Random BSOD all of a sudden, please assist

[EKwag]

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.

 

[VistaKing]

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


Download

For x64 OS

 

[EKwag]

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

 

[EKwag]

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.

 

[VistaKing]

Try running

SFC /scannow

Oops forgot to mention how . Open an elevated command prompt . Click on the rb: 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 .

 

[EKwag]

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

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

 

[VistaKing]

Send me that log

If you get any BSOD . Upload the new dmp file

 

[EKwag]

Send me that log

If you get any BSOD . Upload the new dmp file

Attached the CBS.log

 

[VistaKing]

Type this in the command prompt

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

 

[EKwag]

sfcdetails attached

 

[VistaKing]

Looks like the SFC scannow fixed .

 

[EKwag]

Went to load up a video on YouTube and instant crash. I have a feeling it could be my RAM so I will run Memtest all night to test. I also have extra sticks I can throw in there.

On Thu 4/4/2013 4:25:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040413-21309-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x1A (0x403, 0xFFFFF680000357D0, 0x992000052C9DE867, 0xFFFFF6800002B2A2)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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.

 

[VistaKing]

If the memtest fails test every ram stick in every slot

Reread the SFC /scannow CBS.log . It shows it can't repair this file webservices.dll

Lets run the command below . Click on the rb: button type CMD right click CMD under Programs (1) choose Run as administrator . Command Prompts opens up to this path C:\Windows\System32>_

SFC /SCANFILE=C:\Windows\System32\webservices.dll

   Note

If SFC can't fix the file you will need to get the file from other Windows 7 SP1 machine . Copy the file to a flash drive and input the commands below .

:ar: STEP 1 : You would have to take ownership of the webservices.dll file

:ar: STEP 2 : In the command prompt type in the command below

 [B]takeown /f C:\windows\system32\webservices.dll[/B]

:ar: STEP 3 : Type the command below to grant Full Access to the file

 [b]icacls C:\windows\system32\webservices.dll /grant administrators:F[/b]

:ar: STEP 4 : Copy the file from the USB Flash Drive to the Hard Drive

 [B]xcopy E:\webservices.dll C:\windows\system32\webservices.dll [/B]

   Note

E:\ is your Drive letter of the Flash Drive . Change drive letter if needed

 

[EKwag]

The process cannot access the file because it is being used by another process.

 

[VistaKing]

Try copying it over inside the system recovery. Make sure the file that you grabbed from another computer is unblocked . Right click on the file choose Properties and click on the unblock button .

Restart your computer . Tap on F8 when you get to the Advanced Boot Options press ENTER on Repair Your Computer . Choose Windows 7 and click Next . On the System Recovery window click on Command Prompt . Command prompt will open to this path X:\Sources .

Type in the command below to see which is your OS drive

bcdedit | find "osdevice"

   Note

the | pipe symbol is the key above Enter . Hold shift down and press the key with \ on it

Press the enter key after you inputted the command . It will tell you the drive letter of Windows . It might say its os device partition=D:

To find out the drive letter of your USB flash drive do these commands and press ENTER after each command

 Diskpart

list volume

ADDED :

While talking to a few members here . Before we go and try to replace the files . Lets run another

 SFC /scannow