BSOD Kernal Issues, error 0x0000000a

Ethelwolf · 06 Oct 2013

Hello, all. I just bought a used computer and installed a fresh operating system on it, Windows 7 Ultimate. I had a lot of fun installing all of my programs on it, making sure everything was up to date, and customizing it a little bit, but then I started getting blue screen errors. After it happened a few times, I started trying to analyze them myself, but am in over my head. All I know is that every time there's a crash, the origin comes from the NT Kernal & System, which I've read either points in the direction of bad or outdated drivers or faulty hardware. I've done a complete harddrive scan, as well as memory test to make sure it isn't faulty hardware, leading me to believe (and hope!) that the hardware is fine. Windows Updates says that my drivers are up to date and on my GPU I've turned back my drivers from the most recent beta drivers to the most recent WHQL-certified drivers. Not being able to trace it any further than the Kernal, I'm unsure of what driver to update/change or what program to uninstall. Attached is the SevenForums Diagnostic Tool compressed report. Can someone who understands this a bit better than I do please please point me in the right direction or tell me what you think is going on?

Arc · 06 Oct 2013

Hi Ethelwolf.

The Realtek ethernet driver is failing there and causing the BSODs.

Code:

BugCheck A, {12000017, 2, 0, fffff80002f3920b}

*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+13867 )

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

and the driver is old.

Code:

fffff880`044bd000 fffff880`04542000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Fri Jun 10 12:03:15 2011 (4DF1BAAB)
    CheckSum:         0008B67F
    ImageSize:        00085000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Realtek .... take the Win7 and WinServer 2008 R2 Auto Installation Program dated 2013/9/24.

But there are some other issue, and for that you need to upload your MSINFO32.nfo file.

Click on the start button
Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
Give the time for processing, it will save a .nfo file on your desktop.
Zip it, and upload it following the instruction.

Let us know the results.

D1/Partmgr

Ethelwolf · 06 Oct 2013

Arc, thanks so much for helping me out! Also, awesome avatar. I hadn't even realized that my Realtek ethernet drivers were out of date. I've updated them to the most recent, as you recommended. Attached is a copy of my MSINFO32 file. Again, thanks so much!

Arc · 06 Oct 2013

OK, I asked for the msinfo file to check something, and I am not happy seeing it

Do two more things here ......,

1. Uninstall Virtual Clone Drive.
2. Run SFC /SCANNOW Command - System File Checker

When these two are done, upload the MSINFO file again please?

no sata driver?

Ethelwolf · 06 Oct 2013

Uh, oh, that doesn't sound good... I uninstalled Virtual Clone Drive, put in my Windows 7 Installation disk, but when I attempted to run the System File Checker command, I got the message "Windows Resource Protection could not start the repair service". After looking online, I saw that I needed to set my TrustedInstaller to "Manual" in the Windows Modules Installer part of Services, but upon looking saw that it already was set to "Manual". I tried to run the System File Checker command again, but I got the same message. Is this a problem with the TrustedInstaller or is there something perhaps I've overlooked?

Arc · 07 Oct 2013

So set the things to default and try again?

You also may try SFC /SCANNOW : Run in Command Prompt at Boot

Ethelwolf · 07 Oct 2013

After changing it to "Automatic", it did find and repair corrupted files. Here's the new MSINFO32 file. I really appreciate all the help.

Arc · 08 Oct 2013

A relieving state. VirtualClone Drive is gone, all the SATA drivers are back to their own place.

Now let the computer run .... report us how it is going :)

BIOS=2009

Ethelwolf · 08 Oct 2013

Great to hear that everything is how it should be! Ever since updating the Realtek Ethernet drivers I haven't had any more blue screen issues. Thanks so much for all your help, Arc!

Arc · 08 Oct 2013

You are welcome mate :)

Let us know for any further issue :)