BSOD while using more memory-intensive programs

Tiphareth · 14 Mar 2015

Hello, I have been experience multiple BSODs, especially when using more memory-intensive programs, and have yet to determine the cause. I have run Windows Memory Diagnostic Tool after the last one, and it reported no errors. I have downloaded the Windbg Toolkit, and have followed the instructions, but need assistance in translating the information. Attached is my current Minidump files.

Thank you in advance.

Boozad · 14 Mar 2015

Download and run MemTest86+ to test your RAM. RAM - Test with Memtest86+

Note

Attachment 352665

Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

Run the test and report back with the results.

Tiphareth · 15 Mar 2015

Thank you for your reply. I ran the Memtest for 11 passes, and no errors were detected. I have attached an image of the Memtest for verification of this. While I guess that it not showing any memory errors is good, it's still leaves me to wonder what the cause of the BSOD's is. What would you recommend as the next step?

Boozad · 15 Mar 2015

That's good news, I wanted to ensure your RAM was good before we moved forwards. There are a few instances showing up in your dumps which I'll outline below, please follow the steps listed then check system stability.

1: Norton is causing multiple issues.

Code:

*** WARNING: Unable to verify timestamp for IDSvia64.sys
*** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys
 IDSvia64+0xc310
fffff800`045ce6b8  fffffa80`04eaa7f8
fffff800`045ce6c0  fffff880`04516ff0Unable to load image \SystemRoot\System32\Drivers\N360x64\1506000.020\SYMNETS.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMNETS.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMNETS.SYS
 SYMNETS+0x7bff0

Uninstall Norton and install MS Security Essentials and MalwareBytes.

Note

Make sure you uncheck the 'Enable Free Trial' box when installing MalwareBytes.

2: Your nVidia driver has been flagged. Download this earlier version from here and follow NVIDIA Drivers - Avoid Problems for the cleanest possible install.

Code:

fffff800`045ce608  fffff880`0f39a1a0Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xde1a0

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f2bc000 fffff880`0ff90000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Sep 13 20:59:50 2014 (5414A236)
    CheckSum:         00C8E3A6
    ImageSize:        00CD4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

3: Your nVidia nForce Network driver is causing problems. It's old and needs updating.

Code:

ffff800`045ce4c8  fffff880`050e7b1cUnable to load image \SystemRoot\system32\DRIVERS\nvmf6264.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
 nvmf6264+0x28b1c

0: kd> lmvm nvmf6264
start             end                 module name
fffff880`050bf000 fffff880`05113080   nvmf6264 T (no symbols)           
    Loaded symbol image file: nvmf6264.sys
    Image path: \SystemRoot\system32\DRIVERS\nvmf6264.sys
    Image name: nvmf6264.sys
    Timestamp:        Thu Aug 12 12:46:06 2010 (4C63DEFE)
    CheckSum:         00064419
    ImageSize:        00054080
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Tiphareth · 23 Mar 2015

Well, back again. After following your advice, I am still getting BSOD's. Note that I couldn't find a newer driver for #3 (Nvidia nforce Network)anywhere, but I don't have an external ethernet device on any PCI devices, it is internal. Could this be the driver for the Motherboard? I have attached a new log to provide the most recent BSOD's. Let me know if there is more information you require.

Boozad · 23 Mar 2015

Is your CPU overclocked at all?

Tiphareth · 23 Mar 2015

Boozad,

Thank you for replying. It should be at factory BIOS settings. Would you like me to post some screenshots of the configuration in BIOS?

Boozad · 23 Mar 2015

No that's fine. I have to hit the sack now, I'm beat after a long late shift but will look further into your dumps tomorrow. I'm pretty sure there's a hardware problem somewhere so we'll have to run some tests. Please bear with me and I'll get back to you tomorrow night.

Tiphareth · 24 Mar 2015

Boozad,

So, being frustrated, I decided to run Verifier to stress the drivers, and it looks like the older Nvidia driver(s) you suggested a rollback to are causing issues. I let it BSOD 3 times, and it all pointed to nvlddmkm.sys. I am not sure if this has any relevance, but figured it was worth testing. Note I followed the instructions on using Verifier here: Using Driver Verifier to identify issues with Drivers

I was going to run Furmark, but I do have reservations about knowing the temperature threshold for the GeForce GTX 560 and when to stop testing. I didn't want to burn it up.

Thanks for checking these, hope you got some rest.

Boozad · 24 Mar 2015

It certainly looks like your GPU is causing problems. Do you know what your card's temperatures are both idle and under load?