Random BSOD all of a sudden, please assist

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 7 Pro x64
       #1

    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 Computer


  2. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #2

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


    Download

    For x64 OS
      My Computer


  3. Posts : 9
    Windows 7 Pro x64
    Thread Starter
       #3

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


  4. Posts : 9
    Windows 7 Pro x64
    Thread Starter
       #4

    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 Computer


  5. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #5

    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 .
    Last edited by VistaKing; 03 Apr 2013 at 21:01.
      My Computer


  6. Posts : 9
    Windows 7 Pro x64
    Thread Starter
       #6

    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 Computer


  7. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #7

    Send me that log

    If you get any BSOD . Upload the new dmp file
      My Computer


  8. Posts : 9
    Windows 7 Pro x64
    Thread Starter
       #8

    VistaKing said:
    Send me that log

    If you get any BSOD . Upload the new dmp file
    Attached the CBS.log
      My Computer


  9. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #9

    Type this in the command prompt

    Code:
    findstr /C:"[SR] Cannot repair member file" %windir%\logs\cbs\cbs.log >sfcdetails.txt
      My Computer


  10. Posts : 9
    Windows 7 Pro x64
    Thread Starter
       #10

    sfcdetails attached
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About 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 09:21.
Find Us