Random Blue Screens

[walterono]

I contacted this forum some time ago with repeated BSODs, which always cite ntsokrnl.exe+7040. I recently changed my motherboard, and the BSODs are still with me, exactly as before. I enclose the latest minidump. I would be eternally grateful if you guys could help me sort this out.
In my research I came across www.newdriversupdate.com. They say they are an official Microsoft partner and will find the correct and up to date drivers for one's machine. Has anyone any experience with them and is it worthwhile paying for their services?

 

[yowanvista]

Never use driver updaters, they usually cause a lot of system issues
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[walterono]

Random BSODs

I now attach the files as per your Posting instructions. (The perfmon file is inside the zip file).

I am running Windows 7 Home Premium x64. I have a retail copy. The motherboard is brand new (ASUS P5P41T/USB3). Original internal harddrive about 3 yrs old, second internal drive this year.

 

[yowanvista]

I now attach the files as per your Posting instructions. (The perfmon file is inside the zip file).

I am running Windows 7 Home Premium x64. I have a retail copy. The motherboard is brand new (ASUS P5P41T/USB3). Original internal harddrive about 3 yrs old, second internal drive this year.

No file is attached, try again

 

[walterono]

File attached

Hope I got it this time!

 

[yowanvista]

Hope I got it this time!

You uploaded the tool itself not the zip file

 

[walterono]

Finally?

I seem to be having a bad weekend. Hope this is it.

 

[yowanvista]

Latest dump in your attachment (dated 13/12/2010) blames a core system file
You should enable driver verifier to locate the faulting driver
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Run a scan of Malwarebytes in safe mode with networking

BugCheck 7F, {8, 80050031, 406f8, fffff80002df1886}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

 

[walterono]

Assuming Driver Verifier identifies the faulting driver, do I then replace it, and if so, how?

 

[yowanvista]

Assuming Driver Verifier identifies the faulting driver, do I then replace it, and if so, how?

You will have to uninstall the driver and install a newer version

 

[walterono]

Where do I get the newer version from?

 

[yowanvista]

From the device manufacturer's website

 

[walterono]

Driver Verifier

I now attach the dumpfile created by running Driver Verifier. I will be very interested in what you find ...

 

[walterono]

Can I add something while I'm waiting for you to analyse the crash dump? I have made a number of disk images of my boot partition enabling me to revert my system to an earlier known good condition. At the present time I've reverted to a state where I'm getting no BSODs. However, if I make any change to my machine--I repeat, ANY change--the BSODs start up again. If I

• install a new program
• upgrade an existing program
• make minor changes to the registry

the BSODs start up again and I have to revert my machine back again to be free of them. I find this decidedly weird, but hopefully it will suggest something to the expert mind ...

 

[yowanvista]

All your drivers are up to date but the new dump still blames ntkrnlmp.exe, the core OS file
I suggest running SFC http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

The last solution is a http://www.sevenforums.com/tutorials/3413-repair-install.html

BugCheck 7F, {8, 80050031, 406f8, fffff80002ec6613}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )