Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD all of a sudden, please assist

03 Apr 2013   #1
EKwag

Windows 7 Pro x64
 
 
Random BSOD all of a sudden, please assist

Few days ago I got a random BSOD playing ARMA3 and could barely get my computer to restart. At first I thought it was my Crucial M4 SSD running Windows 8. I decided to disconnect my SSD and install Windows 7 Pro x64 on a WD Black drive but I'm still getting errors. Hoping someone out there can read these dump files and assist me. Thanks in advance.

On Wed 4/3/2013 8:08:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040313-22526-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x19 (0x20, 0xFFFFFA801D1C0080, 0xFFFFFA801D1C01A0, 0x4120004)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 4/3/2013 8:08:01 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: e1c62x64.sys (e1c62x64+0x1FB23)
Bugcheck code: 0x19 (0x20, 0xFFFFFA801D1C0080, 0xFFFFFA801D1C01A0, 0x4120004)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\e1c62x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e1c62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation BAD_POOL_HEADER



On Wed 4/3/2013 1:58:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040313-25334-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xC5 (0xFFFFF81002E106B0, 0x2, 0x0, 0xFFFFF80002DB5A4E)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

e1c62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


My System SpecsSystem Spec
.
03 Apr 2013   #2
VistaKing

Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
 
 

Have you updated the NIC driver if not here is the download for the driver

download For x64 OS
My System SpecsSystem Spec
03 Apr 2013   #3
EKwag

Windows 7 Pro x64
 
 

Yes, sorry I should have updated my post. I just installed that when I saw it in my WhoCrashed report
My System SpecsSystem Spec
.

03 Apr 2013   #4
EKwag

Windows 7 Pro x64
 
 

Updating the NIC did not fix anything. Here is the latest dump report

On Thu 4/4/2013 1:12:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040413-23556-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x4E (0x99, 0x5B0257, 0x2, 0x5B0257)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
My System SpecsSystem Spec
03 Apr 2013   #5
VistaKing

Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
 
 

Try running

Code:
SFC /scannow
Oops forgot to mention how . Open an elevated command prompt . Click on the button type CMD and right click on CMD under Programs (1) choose Run as administrator . Command prompt should open to path C:\Windows\System32>_

type the command above inside the command prompt . Restart the PC when asked .
My System SpecsSystem Spec
03 Apr 2013   #6
EKwag

Windows 7 Pro x64
 
 

No problem, ran it in a elevated window and restarted. We shall see how it holds up, thanks for all your help

Code:
Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log
My System SpecsSystem Spec
03 Apr 2013   #7
VistaKing

Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
 
 

Send me that log

If you get any BSOD . Upload the new dmp file
My System SpecsSystem Spec
03 Apr 2013   #8
EKwag

Windows 7 Pro x64
 
 

Quote   Quote: Originally Posted by VistaKing View Post
Send me that log

If you get any BSOD . Upload the new dmp file
Attached the CBS.log
My System SpecsSystem Spec
03 Apr 2013   #9
VistaKing

Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
 
 

Type this in the command prompt

Code:
findstr /C:"[SR] Cannot repair member file" %windir%\logs\cbs\cbs.log >sfcdetails.txt
My System SpecsSystem Spec
03 Apr 2013   #10
EKwag

Windows 7 Pro x64
 
 

sfcdetails attached
My System SpecsSystem Spec
Reply

 Random BSOD all of a sudden, please assist




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Sudden and random BSOD's/Restarts/Lockups during gaming
Hello, My name is John and I'm a rather new guy around here. I was really hoping someone here can shed some much needed light upon the curse I have been suffering from for some time now that has me stumped. I've grown prone to random system complete lock-up's that cause my screen to go...
BSOD Help and Support
BSOD/sudden lag when working/gaming(random times)(Oc Asus P8P67 pro)
hello all , I have been reading in this fourm about the problem but i didnt reach to any lead so far i have a system which i got 1 month ago and it was stable and good till recently i started getting BSOD at random times , i tried to update my bios as most were saying but i couldnt because...
BSOD Help and Support
Very random BSOD, sudden restarts
Hi guys, I have a relatively new laptop that has been having very random BSODs and sudden restarts. They are very random. They happen during the day, sometimes back to back, sometimes as soon as I boot the laptop. There is no particular pattern, as far as I can see. Basic specs: - I...
BSOD Help and Support
Win7Ultimate - XPS 1645 random sudden BSOD
I have been after this problem for about 2 months. Changing everything from USB vs. BT keyboard to hibernate vs. shutdown. The problem seems from USB driver and two system components left "disabled" per dell suggestion since it complains with a yellow exclam point when activated. Any...
BSOD Help and Support
Random BSOD's - Please Assist
Is Windows 7 . . . - x86 (32-bit) or x64 ? 64-Bit Installation - the original installed OS on the system? Upgrade from Vista 64bit - an OEM or full retail version? Full Retail - OEM = came pre-installed on system ? - Full Retail = MSDN - What is the age of system (hardware)? 1.5 years -...
BSOD Help and Support
Random BSOD all of the sudden.
I've been getting Random BSOD for a couple days now. Not sure whats causing it as it will BSOD while at the desktop. I checked my temps and updated my Video drivers and thats all I could see that was out of date. Anyway this is my first time posting, I think I have Attached everything you guys...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 15:31.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App