RANDOM BSOD even after Factory reset

gsinkaos · 19 Sep 2012

You read it right. Even after the factory reset I continue to get random BSOD. This started happening last year. After going off the edge one day with this thing

, I reset it. It froze the day of the reset when I was rebuilding my desktop again. The improvement after the reset is that it actually writes minidump files now.

I look to the wisdom of this board to help me please. I have attached the minidump files from the last three bsod, the event log and my system specs. If there is anything else needed I will be waiting.

koolkat77 · 20 Sep 2012

Welcome

Please upload your msinfo32.nfo file. To get this:

Click on the Start
Type msinfo32 into the Search programs and files box
When it opens, go to File, Save
Save as msinfo32.nfo and save in a place you will remember
Let it finish the process of gathering and saving the system info
Right click the .nfo file, click send to compressed (zipped) folder
Upload the .zip file here.

koolkat77 · 20 Sep 2012

Assume you have McAfee antivirus installed.
Do upload the msinfo file for confirmation.

Please uninstall McAfee. It alone is a known cause for BSoDs.

How to uninstall or reinstall supported McAfee products using the Consumer Products Removal tool (MCPR)

Download and install MSE. Run a full scan once updated.

Microsoft Security Essentials - Free Antivirus for Windows

Do let us know your feedback.

gsinkaos · 23 Sep 2012

Thanks for the response! I will uninstall mcafee and do the scan- let you know the results. If it is mcafee- it might be a few days before I see if that was the cause of the issue. The BSOD seems to happen almost at random-but we know better, nothing's random with computers.

I have attached the msinfo32 file- give it a look. Thanks again!

koolkat77 · 23 Sep 2012

Sure..take as much time as you want. Let us know if you have any BSoDs after uninstalling McAfee :)

koolkat77 · 30 Sep 2012

Hello,

Did you uninstall McAfee? Any blue screens after that?
You might want to check for an update on your BIOS version as well...

Code:

BIOS Version/Date	DELL INC. A13, 7/28/2009

koolkat77 · 09 Oct 2012

Any new BSoDs? :)

gsinkaos · 17 Oct 2012

There were no BSOD's for a while. The last week- I started up the computer, only opened up chrome, went to cars.com, and out of no where-BSOD. I kept my cool and didn't throw my computer in the tub and run the water. I couldn't find any trace BSOD in the logs so i waited for another. Voila-about 8 minutes ago from this post- another BSOD. It pointed to a tcpip.sys+82139 address as the cause and the address ntoskrnl.exe+7f1c0 as where the crash occurred. I have reattached the dump files and all others. Meanwhile I will go see if there an update for my BIOS! Thanks KoolKat!

koolkat77 · 17 Oct 2012

The BSOD was caused by very old Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC drivers. Update to the latest

Code:

fffff800`00b9c848  fffff880`041df593Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
 Rt64win7+0x18593
fffff800`00b9c848  fffff880`041df593Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
 Rt64win7+0x18593
-----------------
0: kd> lmvm Rt64win7
start             end                 module name
fffff880`041c7000 fffff880`04200000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Fri May 22 20:52:30 2009 (4A16BC2E)
    CheckSum:         00041606
    ImageSize:        00039000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Uninstall older from control panel first

Source 1:

Download Realtek High Definition Audio - FileHippo.com

OR
Source 2:

Driver Reference Table

gsinkaos · 26 Oct 2012

I actually started getting BSOD more often recently and couldn't get a few minutes in when the BSOd would pop up. Anyways, I was finally able to change the realtek driver. I will keep you updated!

Thank you!