BSOD error 0x000005c

[JimmyScott]

Recently bought new hardware because my old motherboard has faulty ram sockets.

So i changed my cpu and the motherboard with the result of a pc that does not freeze up all the time.
So it has worked for around a week now and then this issue started.

i have attached the logs and so on the SF diagnostic that was provided in the guide thread.

I found on some forum that it could have been caused by the driver to my graphics card. Tried uninstalling the old and catalyst control center and install the driver and only driver for catalyst 13.1 instead of 13.4. Still ended up with the same issue.

The issue mainly begins when the GPU has to work. I don't get any BSOD when i start windows normally. Just a black screen. I got that error message when in safe mode and the pc crashed.

So it would be cool if you guys coud look over it and help me find a solution.

 

[Dsprague]

Looks like your issue is being caused by your network driver:

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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa80089ef300, fffffa80089ef420, 4120030}

[COLOR="Red"]*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
Probably caused by : e1c62x64.sys[/COLOR] ( e1c62x64+1fb23 )

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

Driver Reference Table - e1c62x64.sys

Please update the driver from here: https://downloadcenter.intel.com/default.aspx

 

[JimmyScott]

the driver was very outdated. So that has been updated.
However, my problem remains the same.

attached are new logs

 

[Dsprague]

There does not appear that ta crash dump was generated by this latest crash please ensure your computer is configured ot create small memory dumps upon crashing:

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

 

[JimmyScott]

ok, so i'm not getting any BSOD's now. LIke before only a black screen. This time tho, the screen was blue with darker blue lines on it. And nothing else happened. It didnt restart or anything like that. I retarted it with the button on my case, and checked if any dump files was created. There wasn't any.

From the tool i got this, this time

 

[Dsprague]

a couple of things to try:

Run the system file checker

SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
If the program finishes with anything other than "no integrity violations" run the command two more times
If after the third run there are still issues run the command at boot: http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

next from another elevated command prompt run the following command and then reboot:

chkdsk /f /r

 

[JimmyScott]

i have one problem with using those commands.
My windows installation is on an SSD and from what i have researched the fs scan will only check around 75% of my disk.

 

[Dsprague]

So then don't run the command i guess?

 

[JimmyScott]

ok, so i have run the fs scan now, 3timer.

Within windows i could run it, no errors found. I am, however, not able to run it from my windows install disk. As it cannot find my windows installation?

Did the checkdisk aswell. No errors found.

 

[x BlueRobot]

[COLOR="red"]BugCheck C5[/COLOR], {39, 2, 0, fffff80001fb0b05}

Probably caused by : [COLOR="Red"]Pool_Corruption[/COLOR] ( nt!ExDeferredFreePool+249 )

Usual causes:  Device driver, Memory

3: kd> [COLOR="SeaGreen"]!poolval fffff80001fb0000[/COLOR] 
[COLOR="Blue"]Pool page fffff80001fb0000 region is Nonpaged pool[/COLOR]

Validating Pool headers for pool page: fffff80001fb0000

Pool page [ fffff80001fb0000 ] is __inVALID.

Analyzing linked list...
[ fffff80001fb0000 ]:[COLOR="Red"] invalid previous size [ 0x48 ] should be [ 0x0 ][/COLOR]
[ fffff80001fb0000 --> fffff80001fb0400 (size = 0x400 bytes)]: Corrupt region


Scanning for single bit errors...

None found -> Pool Tag

We can clearly see that a device driver has corrupted the pool, however, I can't match the pool tag to to the corresponding driver. A device driver may have overrun this allocation, therefore changing the expected size.

The none pool tag is used to call the ExAllocatePool function.

None - <unknown>    - call to ExAllocatePool

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[JimmyScott]

ok, so im trying to use the driver verifier by using the guide.
I am at the last part where i have to choose the drivers to test.
The guide says:
"Then select all drivers NOT provided by Microsoft and click "Next""
However, only 2 drivers from provided by MS is listed:
"apisetschema.dll"
&
"autochk.exe"

on a side note:
could this error, not with the driver verifier, be in connection with the bsod errors i got while installing windows.
Those where fixed by updating my bios.

 

[x BlueRobot]

They may be the only drivers produced by Microsoft which are able to be tested.

 

[JimmyScott]

should i just test those 2 drivers then?

 

[x BlueRobot]

You don't want to test Microsoft drivers, you want to unselect any drivers related to Microsoft, and leave the third party drivers enabled for testing.

 

[JimmyScott]

ok, so i have found a consistency with my crashes.
I still don't receive a BSOD, but my screen is black and none-responsive.
I tried connecting to my pc with teamviwer. To see if it was some hardware failure and windows still was running in the back. It is'nt. When my screen turned black teamviwer lost the connection.
The consistency i found with the crashes is far as i can tell, whenever i start World Of Warcraft in either the 64bit client or the 23bit.

Tried re-installing the OS, still getting the same issue.
No BSOD's are appearing, just a black screen and a none-responsive pc

 

[JimmyScott]

My pc seems to be stable now.
I restored the pc to before some critical windows update.
In the same restore it also rolled by the driver of my graphics card to something from 2011.
Since this restore my pc seems to be stable.
I have updated the driver to my gfx in the mean time to the latest 13.4 and it's still running stable.
I will report back later tonight, if the issue seems to re-appear.

 

[x BlueRobot]

Okay, that's good to know, thanks for the update

 

[JimmyScott]

Looks like my problem has returned.
attached is 2 pictures of what my screen looks like when i boot it up.
That image or just a black screen is what i'm met with just after the windows logo .disappears

Edit:
Attached a bootlog from a normal boot.

 

[x BlueRobot]

It seems it didn't load your graphics card driver or the chipset driver for some reason, which would explain the display output.

I would suggest following this tutorial to test every possibility for a unbootable Windows - http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html

The hard-drive diagnostics would be the most important one in my opinion, here's the hard-drive diagnostic procedure I always recommend:

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

 

[JimmyScott]

So:

I updated the chipset driver, changed the S-ATA driver from "asmedia" to "intel" and re-installed the graphics driver as well.
My BIOS was already at the latest 4004 and the firmware, of my Corsair Performane Pro, did not need to be updated.

I have now successfully booted my pc into windows. Will report back with stability sometime tomorrow when i wake up