BSOD when PC is idle

[debdutta]

After I uninstalled BitDefender and installed MSE I am getting constant BSODS, I have only one minidump file to show cause others are not logged (dont know why). Please experts look into it, hope this predicts the problem.

Thanks

 

[yowanvista]

Test your RAM http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

BugCheck A, {684fffec, 2, 1, 82caebaf}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+2e1 )

 

[debdutta]

Here's another one

Here's another Minidump I could get, please check this one

 

[Tews]

Update your video driver ....

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {83dfffe4, 2, 1, 82cd1bee}

Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+8a )

Followup: MachineOwner
---------

 

[debdutta]

Thanks for quick reply, I think I have latest video drivers I downloaded few days ago, by the way here's another BSOD file, came while I was listening to music in WMP12. Hope this solves the problem.

 

[yowanvista]

Run System File Checker http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys

 

[WDAexodus]

Sometimes the lastest and greatest video drivers are broke. Perfect example is the lastest ATI drivers with the game Bad Company 2. They cause all kinds of issues so many had to go back a couple revisions to get it to be stable. Try reloading the newest version or go back to a previous version that you knew worked properly. You may want to check direct x also to make sure it isn't screwed up.