New
#1
Multiple kinds of BSOD on startup
Edit: Everything I was supposed to post for BSOD reports is down on post 4
Hey everyone, this has been driving me crazy and I'm running out of ideas on how to hunt down the source of the problem. My computer is a few years old now, custom built, and has had a strange string of problems in which it likes to crash and restart during startup. Here is my basic information and a log of the recent crashes and types from WhoCrashed:
More Notes: Windows 7 64-bit Ultimate (Japanese Originally, but I installed and switched it all to English)System Information (local)
computer name: WEBBSTRE64PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4294107136 total
VM: 2147352576, free: 1994977280
4GB DDR2 RAM
As you can see, it happens pretty often, and every one of those BSOD have been during startup. I did a DSKCHK and it found nothing wrong. I did several full passes with the Memory Diagnostics tool and it too found nothing wrong. I tried to run the Windows Repair Tool, but it gave me some weird error about media devices being connected or something (my OS is originally in Japanese, so taking a photo or something wouldn't help you too much) and refused to run the repair tool. If I let the computer load into the Windows tool that switches it to a previous version it just freezes and hangs forever.Code:Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Thu 2011/01/27 7:25:43 GMT your computer crashed crash dump file: C:\Windows\Minidump\012711-19765-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x4E (0x7, 0x148F18, 0xC000, 0x0) Error: PFN_LIST_CORRUPT file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR 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 which cannot be identified at this time. On Thu 2011/01/27 7:25:43 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: 0x4E (0x7, 0x148F18, 0xC000, 0x0) Error: PFN_LIST_CORRUPT 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 which cannot be identified at this time. On Mon 2011/01/24 7:59:39 GMT your computer crashed crash dump file: C:\Windows\Minidump\012411-30092-01.dmp This was probably caused by the following module: ataport.sys (ataport+0xF60C) Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF88000DB660C, 0xA, 0x5C0031002E0000) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\drivers\ataport.sys product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: ATAPI Driver Extension Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sun 2011/01/23 3:01:24 GMT your computer crashed crash dump file: C:\Windows\Minidump\012311-23462-01.dmp This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x156354) Bugcheck code: 0x116 (0xFFFFFA80067A54E0, 0xFFFFF88010980354, 0x0, 0x2) Error: VIDEO_TDR_ERROR file path: C:\Windows\system32\drivers\nvlddmkm.sys product: NVIDIA Windows Kernel Mode Driver, Version 266.58 company: NVIDIA Corporation description: NVIDIA Windows Kernel Mode Driver, Version 266.58 Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed. 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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 266.58 , NVIDIA Corporation). Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_ERROR On Sat 2011/01/22 23:35:47 GMT your computer crashed crash dump file: C:\Windows\Minidump\012311-30513-01.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8) Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880050AA738, 0xFFFFF880050A9FA0, 0xFFFFF8000AB89A20) Error: NTFS_FILE_SYSTEM file path: C:\Windows\system32\drivers\ntfs.sys product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT File System Driver Bug check description: This indicates a problem occurred in the NTFS file system. 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 which cannot be identified at this time. On Fri 2011/01/21 23:52:56 GMT your computer crashed crash dump file: C:\Windows\Minidump\012211-21075-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x19 (0x3, 0xFFFFFA8004864720, 0xFFFFFA8004864720, 0xFFFFF8A0018371D0) Error: BAD_POOL_HEADER file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR 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 which cannot be identified at this time. On Wed 2011/01/19 7:42:55 GMT your computer crashed crash dump file: C:\Windows\Minidump\011911-18829-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x4E (0x7, 0x14B188, 0x3400, 0x0) Error: PFN_LIST_CORRUPT file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR 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 which cannot be identified at this time. On Sun 2011/01/16 21:24:25 GMT your computer crashed crash dump file: C:\Windows\Minidump\011711-26005-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF8000ABA8232) Error: UNEXPECTED_KERNEL_MODE_TRAP file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 2011/01/16 0:17:45 GMT your computer crashed crash dump file: C:\Windows\Minidump\011611-20732-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x19 (0x3, 0xFFFFFA8004864320, 0xFFFFFA8004866720, 0xFFFFFA8004866720) Error: BAD_POOL_HEADER file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR 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 which cannot be identified at this time. On Sun 2011/01/09 0:35:09 GMT your computer crashed crash dump file: C:\Windows\Minidump\010911-20904-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000A9B936B, 0x0, 0x108) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. 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 which cannot be identified at this time. On Fri 2011/01/07 5:08:38 GMT your computer crashed crash dump file: C:\Windows\Minidump\010711-24538-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x4E (0x7, 0x175B30, 0x4200, 0x0) Error: PFN_LIST_CORRUPT file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR 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 which cannot be identified at this time. On Mon 2011/01/03 22:51:03 GMT your computer crashed crash dump file: C:\Windows\Minidump\010411-26613-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x4E (0x9A, 0x17D9C3, 0x6, 0x8001) Error: PFN_LIST_CORRUPT file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR 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 which cannot be identified at this time.
Small note: I am aware one of the errors was from my Geforce drivers, and have already installed the newer driver release for that since then.
Here is the strangest part: The computer never BSODs on the second load, ever. It always is able to load normally after the first crash, and it never crashes while Windows is running.
Anyone know what I am experiencing? I have tried everything I can find.
Last edited by Webbstre; 01 Feb 2011 at 18:22.
Quote