Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: BSOD - info attached.

28 May 2011   #1

Windows 7 x64
 
 
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.


My System SpecsSystem Spec
.

28 May 2011   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit
 
 

Can you upload a jcgriff2 report?

http://www.sevenforums.com/crashes-d...tructions.html
My System SpecsSystem Spec
28 May 2011   #3

Windows 7 x64
 
 

OK health report and bsod jcgriff2 attached in zip file

thanks!
My System SpecsSystem Spec
.


28 May 2011   #4

Windows 7 x64
 
 

updated health report, just installed the USB driver, but I don't think it makes difference.

sorry and thanks again.
My System SpecsSystem Spec
28 May 2011   #5

Windows 7 x64
 
 

The age of the hardware is 2 weeks.
original installed OS : none.
OEM - I am using my serial, but the CD I got from my friend he recommended me his version that works very good for him, I have my original win cd anyway, but it's not the problem thought.
Windows 7 64-bit as mentioned above.

sorry for too much posts.
My System SpecsSystem Spec
28 May 2011   #6

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit
 
 

Disable driver verifier and run the tests

Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - RAM - Test with Memtest86+
2. Prime95 - Run all three tests (Small FFTs, Large FFTs, Blend) for 3-4 hours each or until fail - http://www.sevenforums.com/tutorials...t-prime95.html
3. Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests

Forgot that you ran Memtest already for 30+ hours

BSOD BUGCHECK SUMMARY
Code:

Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 13:54:50.054 2011 (UTC - 4:00)
System Uptime: 0 days 0:09:40.881
Probably caused by : ntkrnlmp.exe ( nt!PfpRpFileKeyUpdate+35e )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  where.exe
FAILURE_BUCKET_ID:  X64_0x3B_VRF_nt!PfpRpFileKeyUpdate+35e
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 13:44:22.913 2011 (UTC - 4:00)
System Uptime: 0 days 1:08:31.740
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_VRF_nt!MiBadShareCount+4c
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 12:35:08.805 2011 (UTC - 4:00)
System Uptime: 0 days 0:21:57.632
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  mscorsvw.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_VRF_nt!MiBadShareCount+4c
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 08:30:52.193 2011 (UTC - 4:00)
System Uptime: 0 days 0:08:57.021
Probably caused by : ntkrnlmp.exe ( nt!CmpDelayCloseWorker+15e )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.
FAILURE_BUCKET_ID:  X64_0x7E_VRF_nt!CmpDelayCloseWorker+15e
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 07:21:34.962 2011 (UTC - 4:00)
System Uptime: 0 days 0:04:00.790
Probably caused by : fileinfo.sys ( fileinfo!FIStreamGet+52 )
BUGCHECK_STR:  0x1a_411
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x1a_411_VRF_fileinfo!FIStreamGet+52
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 07:16:48.789 2011 (UTC - 4:00)
System Uptime: 0 days 0:03:27.617
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a8fd )
BUGCHECK_STR:  0x1a_5001
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_5001_VRF_nt!_??_::FNODOBFM::_string_+2a8fd
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 07:12:34.648 2011 (UTC - 4:00)
System Uptime: 0 days 0:06:47.476
Probably caused by : memory_corruption ( nt!MiPerformFixups+80 )
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_VRF_nt!MiPerformFixups+80
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 06:45:14.513 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:39.215
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  RPMMgr.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_gdrv+1809
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 06:42:09.515 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:51.343
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  RPMMgr.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_gdrv+1809
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 06:40:35.253 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:46.080
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  RPMMgr.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_gdrv+1809
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 06:20:13.542 2011 (UTC - 4:00)
System Uptime: 0 days 0:03:10.354
Probably caused by : ntkrnlmp.exe ( nt!CmpDelayDerefKCBWorker+12a )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.
FAILURE_BUCKET_ID:  X64_0x7E_nt!CmpDelayDerefKCBWorker+12a
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 05:43:27.868 2011 (UTC - 4:00)
System Uptime: 0 days 0:20:39.680
Probably caused by : Ntfs.sys ( Ntfs!NtfsCreateInternalAttributeStream+2c1 )
PROCESS_NAME:  explorer.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCreateInternalAttributeStream+2c1
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 05:18:53.766 2011 (UTC - 4:00)
System Uptime: 0 days 0:09:42.578
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  mscorsvw.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri May 27 20:54:44.264 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:44.091
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  RPMMgr.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_gdrv+1809
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri May 27 20:53:23.122 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:37.949
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  RPMMgr.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_gdrv+1809
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri May 27 18:06:41.190 2011 (UTC - 4:00)
System Uptime: 0 days 0:21:34.002
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri May 27 14:09:19.437 2011 (UTC - 4:00)
System Uptime: 0 days 1:55:04.138
Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2b49 )
PROCESS_NAME:  TrustedInstall
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!_??_::FNODOBFM::_string_+2b49
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri May 27 08:26:15.254 2011 (UTC - 4:00)
System Uptime: 0 days 0:27:45.066
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+34f )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  SmartViewAgent
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!ExDeferredFreePool+34f
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri May 27 07:57:42.367 2011 (UTC - 4:00)
System Uptime: 0 days 2:49:32.179
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+14382 )
BUGCHECK_STR:  0x1a_41201
PROCESS_NAME:  SearchProtocol
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+14382
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu May 26 19:05:36.842 2011 (UTC - 4:00)
System Uptime: 0 days 0:11:01.654
Probably caused by : ntkrnlmp.exe ( nt!CmpAllocateKeyControlBlock+72 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  TrustedInstall
FAILURE_BUCKET_ID:  X64_0x3B_nt!CmpAllocateKeyControlBlock+72
BiosReleaseDate = 03/31/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = P67A-UD3-B3
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
  
My System SpecsSystem Spec
29 May 2011   #7

Windows 7 x64
 
 

Hi, I tried Blend tests and got errors :

[Sun May 29 10:32:05 2011]
Self-test 640K passed!
Self-test 640K passed!
Self-test 640K passed!
Self-test 640K passed!
Self-test 640K passed!
Self-test 640K passed!
Self-test 640K passed!
Self-test 640K passed!
[Sun May 29 10:47:08 2011]
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
[Sun May 29 11:02:42 2011]
Self-test 720K passed!
Self-test 720K passed!
Self-test 720K passed!
Self-test 720K passed!
Self-test 720K passed!
Self-test 720K passed!
Self-test 720K passed!
Self-test 720K passed!
[Sun May 29 11:18:54 2011]
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
[Sun May 29 22:05:24 2011]
FATAL ERROR: Rounding was 0.4995117188, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Self-test 800K passed!
Self-test 800K passed!
Self-test 800K passed!
Self-test 800K passed!
FATAL ERROR: Final result was 6844DB94, expected: EB7C125D.
Hardware failure detected, consult stress.txt file.
Self-test 800K passed!
Self-test 800K passed!

what might the problem be?
My System SpecsSystem Spec
29 May 2011   #8

Windows 7 x64
 
 
BSOD - info attached.

my 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‎

health report + Windows_NT6_BSOD_jcgriff2 attached.

Note:
tested memtest86+ for 22 hours.
Prime95 blend test. (Large and Small FFT interrupted by BSOD).


Please close my last thread there are too much info and outdated, sorry for that.
Thank you!
My System SpecsSystem Spec
29 May 2011   #9

Windows 7 x64
 
 

Attached here, sorry
My System SpecsSystem Spec
30 May 2011   #10

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit
 
 

What type of power supply do you have?
My System SpecsSystem Spec
Reply

 BSOD - info attached.





Thread Tools



Similar help and support threads for2: BSOD - info attached.
Thread Forum
Multiple and random BSOD's. Summary dmp info attached BSOD Help and Support
BSOD - SF Diagnostic Tool Info is attached. BSOD Help and Support
Please help with BSOD crash. Requested info attached. Thank you! BSOD Help and Support
CONSTANT BSOD Stop 0x00000124 all info attached BSOD Help and Support
recent & frequent BSOD's. info attached BSOD Help and Support
BSOD error info attached BSOD Help and Support
Bsod 3 dumps and info attached BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 07:27 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33