BSOD during windows installation

dela · 17 Jan 2014

recently i had multiple bsod after a video driver was updated randomly without my consent. after trying everything i could to fix it (f8, chkdsk, malwarebytes, repair, system restore, safe mode, etc.) i tried using acer erecovery management to restore my laptop. unfortunately during the reinstallation, the bsod still appeared while installing important drivers. i was forced to repeatedly use the erecovery but always encountered bsod before completely installing everything. luckily i was able to enter safe mode somehow and created a user account that i could use normally. from there i used ccleaner to help fix some registry files and disabled all programs running on startup (other than windows applications) using system configuration. so far im still getting bsod's when installing windows updates, or trying to use full scans on any antivirus software. i even got one while typing this. before it happens again, i used the sf diagnostic tool.

btw i have a acer aspire 4743 laptop if it helps at all, also after using bluescreenviewer, most of it seems to involve ntoskrnl.exe

dela · 18 Jan 2014

results from whocrashed.

System Information (local)
--------------------------------------------------------------------------------

computer name: WIN-54QU0T7RE16
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Aspire 4743, Acer,
CPU: GenuineIntel Intel(R) Pentium(R) CPU P6200 @ 2.13GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3947290624 total
VM: 2147352576, free: 1981083648

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 1/18/2014 5:55:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011714-37284-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A0070F5300, 0xFFFFF8A0070F5C10, 0x5910408)
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 Sat 1/18/2014 5:55:29 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A0070F5300, 0xFFFFF8A0070F5C10, 0x5910408)
Error: BAD_POOL_HEADER
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 Sat 1/18/2014 5:25:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011714-35942-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x4E (0x99, 0x7D869, 0x2, 0x7D863)
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.

On Sat 1/18/2014 5:07:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011714-34273-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC50046F00, 0x844000011C982882, 0xFFFFF6800002BCE3)
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.

On Sat 1/18/2014 4:09:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011714-37814-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x19 (0x3, 0xFFFFFA8003AFAB00, 0x7700200066006F, 0xFFFFFA8003AFAB00)
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 Sat 1/18/2014 4:02:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011714-31200-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x5000, 0xFFFFF781C0000000, 0x800011, 0x16E)
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.

On Sat 1/18/2014 12:11:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011714-35178-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xC1 (0xFFFFF980113F4C60, 0xFFFFF980113F4010, 0xC303A0, 0x23)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 driver wrote to an invalid section of the special pool.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Fri 1/17/2014 10:54:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011714-44163-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002CEB7D5)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Fri 1/17/2014 10:40:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011714-49124-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xC1 (0xFFFFF98008450E10, 0xFFFFF98008450010, 0xC901F0, 0x23)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 driver wrote to an invalid section of the special pool.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Fri 1/17/2014 10:03:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011714-38454-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xAC266)
Bugcheck code: 0x19 (0x3, 0xFFFFFA8003AF7300, 0x30003000300030, 0xFFFFFA8003AF7300)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System 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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

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

51 crash dumps have been found and analyzed. Only 10 are included in this report. 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:

athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)

--------------------------------------

ive already updated that driver and had no change whatsoever. i really need help finding this driver thats causes my bsod's. any help is very appreciated

YoYo155 · 18 Jan 2014

Hello and welcome to SF dela :) .

The bugcheck codes are varying greatly which usually means memory issues, please follow
the detailed quote to test the RAM.

Arc said:

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

dela · 26 Jan 2014

i got 274 errors after the first 2 passes. usually found errors when doing the 32 bit test. i cant really open up my laptop since i dont have the tools to do so. is there anyway to do a fix without touching the hardware?

YoYo155 · 27 Jan 2014

dela said:

i got 274 errors after the first 2 passes. usually found errors when doing the 32 bit test. i cant really open up my laptop since i dont have the tools to do so. is there anyway to do a fix without touching the hardware?

Hi again :).

Unfortunately not

, bad memory needs to be addressed else BSOD's will continue.