New
#1
Bsod: Memory management & pfn_list_corrupt
Hi,
I bought a new desktop with the following spec:
AMD Radeon 6950 2GB
2 * [2x2GB G.Skill Ripjaws Edition Dual Channel CL7-8-7-24] - 8GB of RAM
GIGABYTE P67A-UD3-B3 Motherboard
i7-2600K sandy bridge processor
Caviar Black 640GB 7200RPM, 32MB, SATA II WD6401AALS
I'm getting MEMORY MANAGEMENT & PFN LIST CORRUPT BSODS.
I ran every kind of test (memtest86+ for 30 hours , memtest, bootsect, chkdsc.. of windows and lots of tests passed), even the verifier.exe , it was reporting gdrv.sys error but I got over it and now it doesn't recognize any driver error on startup.
I am running on Windows 7 64bit.
* I deleted GIGABYTE tools (enegy saver + et6) and I don't get gdrv.sys related BSODs anymore.
* I deleted AVG anti virus as a realized there was a bsod related to it and installed Microsoft Security Essentials instead.
* I updated all files for WINDOWS UPDATE.
****** ALL OF THE REMAINED BSODS ARE RELATED TO "ntoskrnl.exe" as you can see at the bottom of the comment.
p.s: I was told to delete catalyst 11.5 (that seemed to be corrupted, it was always crashing.. like other programs) and I did, but still I am getting the same errors.
# I used Driver Genius 10 in order to update my drivers also!
I paid lots of money and not enjoying my computer.. got any solution? maybe BIOS settings? or whatever? I am not that good in determining BIOS settings, although am not sure its the problem.
Please help me am dying , hope I didn't miss any info :)
--------------------------------------------------------------------------------
WhoCrashed LOG:
Code:On Sat 5/28/2011 4:35:08 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\052811-15818-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00) Bugcheck code: 0x4E (0x99, 0x1B959A, 0x1, 0x1B969A) 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 which cannot be identified at this time. On Sat 5/28/2011 4:35:08 PM 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 (0x99, 0x1B959A, 0x1, 0x1B969A) 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 Sat 5/28/2011 12:30:52 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\052811-19671-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x2D1FD2) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000094, 0xFFFFF800032DFFD2, 0xFFFFF88003362888, 0xFFFFF880033620E0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 system thread 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 Sat 5/28/2011 11:21:34 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\052811-15038-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00) Bugcheck code: 0x1A (0x411, 0xFFFFF6FCC018A3D0, 0x500001A04228C2, 0xFFFFF8A0030204E3) 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 which cannot be identified at this time. On Sat 5/28/2011 11:16:48 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\052811-19032-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00) Bugcheck code: 0x1A (0x5001, 0xFFFFF70001080000, 0x6DD9, 0x4A9FFFFEFFE) 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 which cannot be identified at this time. On Sat 5/28/2011 11:12:34 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\052811-17347-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800033AD1C0, 0x0, 0x197DB88C0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 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 Sat 5/28/2011 10:45:14 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\052811-20623-01.dmp This was probably caused by the following module: gdrv.sys (gdrv+0x1809) Bugcheck code: 0xC4 (0xF6, 0x15C, 0xFFFFFA8009C4B260, 0xFFFFF88007EB9809) Error: DRIVER_VERIFIER_DETECTED_VIOLATION Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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: gdrv.sys . Google query: gdrv.sys DRIVER_VERIFIER_DETECTED_VIOLATION On Sat 5/28/2011 10:42:09 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\052811-19936-01.dmp This was probably caused by the following module: gdrv.sys (gdrv+0x1809) Bugcheck code: 0xC4 (0xF6, 0x15C, 0xFFFFFA8009D4F3B0, 0xFFFFF88008090809) Error: DRIVER_VERIFIER_DETECTED_VIOLATION Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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: gdrv.sys . Google query: gdrv.sys DRIVER_VERIFIER_DETECTED_VIOLATION On Sat 5/28/2011 10:40:35 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\052811-17409-01.dmp This was probably caused by the following module: gdrv.sys (gdrv+0x1809) Bugcheck code: 0xC4 (0xF6, 0x15C, 0xFFFFFA80085B7B30, 0xFFFFF88008B5E809) Error: DRIVER_VERIFIER_DETECTED_VIOLATION Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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: gdrv.sys . Google query: gdrv.sys DRIVER_VERIFIER_DETECTED_VIOLATION On Sat 5/28/2011 10:20:13 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\052811-23041-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x3633BA) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000094, 0xFFFFF800033BC3BA, 0xFFFFF880033698D8, 0xFFFFF88003369130) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 system thread 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 Sat 5/28/2011 9:43:27 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\052811-19546-01.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88) Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800ADBC748, 0xFFFFF8800ADBBFA0, 0xFFFFF800031FB617) Error: NTFS_FILE_SYSTEM 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 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 Sat 5/28/2011 9:18:53 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\052811-21465-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00) Bugcheck code: 0x4E (0x99, 0xB9258, 0x0, 0xB90D8) 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 which cannot be identified at this time. On Sat 5/28/2011 12:54:44 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\052811-26301-01.dmp This was probably caused by the following module: gdrv.sys (gdrv+0x1809) Bugcheck code: 0xC4 (0xF6, 0xE0, 0xFFFFFA8008B9DB30, 0xFFFFF880083D2809) Error: DRIVER_VERIFIER_DETECTED_VIOLATION Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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: gdrv.sys . Google query: gdrv.sys DRIVER_VERIFIER_DETECTED_VIOLATION On Sat 5/28/2011 12:53:23 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\052811-24180-01.dmp This was probably caused by the following module: gdrv.sys (gdrv+0x1809) Bugcheck code: 0xC4 (0xF6, 0xE0, 0xFFFFFA800902C060, 0xFFFFF88008194809) Error: DRIVER_VERIFIER_DETECTED_VIOLATION Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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: gdrv.sys . Google query: gdrv.sys DRIVER_VERIFIER_DETECTED_VIOLATION On Fri 5/27/2011 10:06:41 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\052811-18283-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00) Bugcheck code: 0x1A (0x41284, 0x69B47001, 0x0, 0xFFFFF70001080000) 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 which cannot be identified at this time.
Last edited by Brink; 28 May 2011 at 12:45. Reason: added code box
Quote