New
#11
Hi Arc,
Just hit another BSOD.
Please have a look and see if you could help me out on this?
Hi Arc,
Just hit another BSOD.
Please have a look and see if you could help me out on this?
I know that you ran MemTest86+ overnight with 18 total passes without errors (from your original post) ... so searching for any possible driver corruption which may be passing any bad info to the memory.
Enable Driver Verifier to monitor the drivers. Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
InformationWhy Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
WarningBefore enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.
If there is no points, make a System Restore Point manually before enabling DV.
Let us know the results, with the subsequent crash dumps, if any.Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.
Hello Arc,
Following your advise I ran DV for a full week with normal use without BSOD. It was slightly laggy during load times but no serious impact on my usage.
But when I disabled DV, the BSOD emerged. It somehow never BSOD in DV mode.
I'm totally at a lost on how to solve my problem. Just minutes ago while running Borderlands 2 for some fun, the BSOD hit me again with "Memory Management".
Crash dump as attached. Please help...
Bit of strange to me, too.
Anyway, the crash dump loosely blames the video memory.
Your motherboard supports Intel HD graphics. Can you remove the graphics card and apply the onboard graphics, at least as a test?Code:BugCheck 1A, {403, fffff680002ca4b0, d08000000ffaf86f, fffff680002b166a} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 ) Followup: MachineOwner ---------
I will need to find a time when I have offloaded all my work and remove the card for the test...
Thank you and will update again soon.