Windows 10: BSOD - I'm very frustrated

Good evening to you all,


One week ago I "upgraded" my RAM to enable processing with Agisoft PhotoScan

Crucial Ballistix Sport 32GB (4 x 8GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model BLS4KIT8G3D1609DS1S00 - http://www.newegg.com/global/au/Prod...82E16820148666


Ever since I've had numerous BSOD issues and I'm struggling to identify and fix the problem. My old RAM setup (1 x Kingston 8GB module) worked flawlessly and if I didn't need to update the system I would've left it alone. All my inquiries have indicated that my new RAM modules are compatible with my other components, but obviously there are other issues that I simply don't understand.


My wife has made passing remarks that I need to spend more time with her instead of "swearing at that "#$@&... computer". As you can see, I need your help!

Memtest shows zero errors on each module (tested individually and collectively)

I've just done a clean install of Windows so you'll see there's only one dump file. I'm not going to wait for the next BSOD just to provide you with another one!

UPDATE: Make that two now *Mad

Attachment 80430

:)

 

Video TDR Failure (NVLDDMKM.SYS) on windows 10

I'm getting the BSOD with the exact same error code while transferring files from one internal hard drive to another. Very frustrating.

 

Crash Log Help

I've had a few BSOD crashes recently and it's become very frustrating.. Can anyone take a look at the help logs and help me out?

Dropbox - Crash Logs.zip

 

Hi Heartbroken,

Welcome to the 10forums *Smile

What memory test did you run & for how long/many passes?

 

Thanks for your reply. This forum is excellent! *Smile

MemTest86
8 passes each stick - zero errors
6 passes collectively - zero errors

The RAM was purchased as a 4-kit.

 

Both dumpfiles mention memory corruption.
But in one in the procesname is mentioned Nsbu.exe.
This is part of symentec .

And in your eventviewer i found this

Bhdrv64.sys is also from symentec.

In your unloaded modules this:

Both drivers are also from symentec.

In your driverlist:
ccSetx64 Mon Aug 18 21:33:11 2014
SRTSPX64 Tue Aug 26 08:36:42 2014
SYMEVENT64x86 Mon Jan 19 23:43:56 2015
These are all older drivers from symentec, but there are also drivers from 2016.
Are you running 2 different symentec programs at the same time.
Or there could be some corruption.
I would uninstall all symentec programs with symentec/Norton removal tool and reinstall your programs.

 

Thank you for your help!

The dual Symantec driver issue makes perfect sense. Just prior to my latest BSOD I upgraded "Norton Internet Security to "Norton Security". I also run "Norton Family". I suspect that I've simply installed Norton Security "over the top" of Norton Internet Security" without actually uninstalling it from my second hard drive (which was not wiped when I did the clean install of Windows). I will uninstall all Symantec programs as suggested.

In regard to the memory corruption... I guess that just means I have either a bad stick or a bad slot on the motherboard? I'll do some more MemTest86 scans and see what comes up.

Again.... Thank you!!!

 

Memory corruption doesn't necessarily mean hardware, it is more often caused by drivers passing data to the wrong memory address but a memory test is still suggested to ensure it is not the cause.

With memory corruption the most occuring causes are:

• Drivers,
• Memory,
• SSD (firmware more often than the SSD itself bad),
• HDD,
• GPU, in this case we should see some DirectX stuff back in the stacks or similar drivers.

Then there is also the possibility that the

• CPU,
• SATA/IDE controller,
• mainboard &
• PSU,

can cause memory corruption, though most of these are pretty rare occuring when we see memory corruption.
I've seen only once the PSU causing memory corruption because of a loose cable, a few times the CPU and a few times the mainboard.

 

My rig is currently 6 passes in to an 8 pass Memtest86 check with all four RAM modules installed. It has displayed the following error. All previous tests have come back with zero errors.

Should I continue with the test (with the four modules installed or is it time to test one/two modules at a time to try to an identify an individual module?

Attachment 80686

 

This is the correct next step *Smile