Random BSOD Memory Management issue...

thadunno · 15 Dec 2015

Hi
I was wondering if someone can help me before I lose my sanity. I built a new system in September and things were going OK until the recent 1511 update to Windows 10. Since then I've been getting a lot of BSOD errors pointing to MEMORY_MANAGEMENT. I ran Memtest for around 12 hours but it didn't show any errors, and after a bit of digging I found out that the memory management BSOD can point to driver conflicts or bad drivers. Since the 1511 upgrade seemed to do the equivalent of an upgrade install, I thought maybe something had got a bit confused driver wise, so yesterday I decided to do a clean install.
I installed Windows from a 1511 ISO downloaded directly from Microsoft and started to reinstall the drivers from the vendors website (this being Gigabyte), did Windows updates, and then proceeded to reinstall all the programs I use. I got about 2 hours into it and was hit with the same BSOD, MEMORY_MANAGEMENT. So I went back to Google, found the advice to try using the Driver Verifier to see if it was indeed a driver issue. Selected the recommended settings, restart and straight away I'm hit with a BSOD on boot, DRIVER_VERIFIER_DETECTED_VIOLATION. Thinking that indeed pointed to a driver issue, I decided to try another fresh install, this time installing only the LAN driver and letting Windows Update grab the rest of the drivers it needed. Try the Driver Verifier again, and yet again, the same BSOD on boot.
Now I'm kind of at a loss. I'm not sure if this is pointing to a driver error, or a hardware error or not. Unfortunately, because of the fresh install I haven't hit a MEMORY_MANAGEMENT BSOD yet, just the Driver Verifier BSOD on boot so I'm not sure my Minidumps will be of any great help. I'm going to carry on using my PC and wait for it to BSOD so I can provide you with more information, but for the time being I was wondering if anyone has any suggestions, or if they can hint if this does look like a driver conflict or something more serious?
Any help is appreciated!
Thanks

axe0 · 17 Dec 2015

Please update the Nvidia virtual audio device driver
Driver Reference Table - nvvad64v.sys

Code:

*** WARNING: Unable to verify timestamp for nvvad64v.sys
*** ERROR: Module load completed but symbols could not be loaded for nvvad64v.sys
4: kd> lmvm nvvad64v
start             end                 module name
fffff800`0c260000 fffff800`0c26d000   nvvad64v T (no symbols)           
    Loaded symbol image file: nvvad64v.sys
    Image path: \SystemRoot\system32\drivers\nvvad64v.sys
    Image name: nvvad64v.sys
    Timestamp:        Mon Aug 10 09:51:42 2015 (55C8580E)
    CheckSum:         0001AC9A
    ImageSize:        0000D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

thadunno · 17 Dec 2015

Hi axe0, thank you for taking the time to reply and look at my problem. I've updated the drivers as far as I can tell, the control panel is telling me I have the latest drivers. Oddly enough, since posting this cry for help, I haven't had one BSOD related to the memory management error (or any BSOD's at all in fact). I can't see me getting off that easy, but I was hoping I would have more minidumps or at least some more information to give by this stage.

axe0 · 17 Dec 2015

There are 3 dumps, according to the event logs there are 3 crashes.
Unless others haven't been logged, it is fine :)

However, after checking the dumps I noticed my analyse isn't completed

A network driver has been flagged, it is the Killer bandwith control driver.
Please check Killer Networking - Driver Downloads for driver updates

Code:

*** WARNING: Unable to verify timestamp for bwcW10x64.sys
*** ERROR: Module load completed but symbols could not be loaded for bwcW10x64.sys
4: kd> lmvm bwcW10x64
start             end                 module name
fffff800`0b4f0000 fffff800`0b855000   bwcW10x64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\bwcW10x64.sys
    Image name: bwcW10x64.sys
    Timestamp:        Fri Dec 11 20:21:05 2015 (566B2221)
    CheckSum:         00027B0D
    ImageSize:        00365000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

thadunno · 17 Dec 2015

Those 3 dumps as far as I'm aware were all from trying to get the driver verifier to work, it would just BSOD on boot. I did that until I could start in safe mode and disable it, so it probably would have created a few dumps in doing so.
I used the same link as above to get the most up to date drivers when I did a reinstall, I've just double checked the installer I used and it's the same version (1.1.57.1665).

axe0 · 17 Dec 2015

Well, let me know how it goes.

thadunno · 17 Dec 2015

Will do! Thanks for your help, it's seriously appreciated!