Windows 7: BSOD, cant collect the data?

DxxS · 24 Jun 2011

Hi, I have followed the steps in the BSOD posting instructions thread, I run perfmon /report, it says collecting data for 60 seconds then says;

Error:
An error occured while attempting to generate the report.
The wait for the report generation tool to finish has timed out.

Any Ideas?

My machine used to BSOD every other week, I reinstalled OS and since then has done it maybe twice in 5-6 months, got home from work to find my pc stuck at an error screen unable to boot OS, after some medling I have it booting fine, just wanted some wise folk to cast their eyes over the report but no such luck.

Thanks,

mgorman87 · 24 Jun 2011

If the report fails on the 3rd step it still should create something. The prefmon report isn't a vital part of bsod analysis. Upload what you have.

DxxS · 25 Jun 2011

When you say upload what I have do you mean the content on Windows_NT6_BSOD_jcgriff2 folder?

If it helps safe mode is ok.

mgorman87 · 25 Jun 2011

Yes. Safe mode is fine.

DxxS · 26 Jun 2011

Please see system spec below and attached BSOD report.Also, over night my PC crashed whilst in safe mode.

OS

Windows 7 Ultimate 64-bit CPU

Intel Core 2 Duo E8400 3GHz Motherboard

ASUS P5Q PRO Turbo Memory

Crucial DDR2 1066MHz/PC2-8500 Ballistix Memory (4x1GB) Graphics Card(s)

BFG GTS250 OC 1GB GDDR3 Sound Card

N/A Monitor(s) Displays

Dual (x2) Samsung SM2033SW 20"TFT Screen Resolution

N/A Hard Drives

350GB - Internal (OS installed)
500GB - Internal (Storage)
1TB - Internal (Storage)
1TB - External (Storage) PSU

OCZ Stealth XStream 700W PSU

mgorman87 · 26 Jun 2011

Remove AVG. It was the cause of one of your crashes. Replace with Microsoft Security Essentials.

AVG - Download tools and utilities

Code:

ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)

A known BSOD maker in Windows 7. The 2005 version of this driver is known to cause BSOD on Windows 7 systems.
Download the ATK0110 utility from here - ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE.
After you install it browse to C:\windows\system32\drivers and check the properties of ASACPI.sys and make sure it now says 2009.

Code:

L1E62x64.sys Sun Aug 23 01:08:09 2009 (4A90CEB9)

Update your Atheros driver - Atheros Communications

Code:

nvlddmkm.sys Fri Jan 07 21:07:22 2011 (4D27C6DA)

Update your video card driver - NVIDIA DRIVERS 275.33 WHQL

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

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jun 24 13:36:18.255 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:17.785
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  Backup & Stora
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 2999
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jun 24 13:26:29.539 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:25.178
Probably caused by : Ntfs.sys ( Ntfs!NtfsOpenAttribute+326 )
PROCESS_NAME:  winlogon.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_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!NtfsOpenAttribute+326
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 2999
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun 21 18:31:58.674 2011 (UTC - 4:00)
System Uptime: 4 days 15:42:26.547
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+156354 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 2999
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jun  9 02:46:13.223 2011 (UTC - 4:00)
System Uptime: 1 days 23:56:20.753
*** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys
Probably caused by : AVGIDSFilter.Sys ( AVGIDSFilter+2656 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_AVGIDSFilter+2656
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 2999
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun  7 02:48:26.472 2011 (UTC - 4:00)
System Uptime: 0 days 21:18:37.002
Probably caused by : NETIO.SYS ( NETIO!NetiopIoWorkItemRoutine+3b )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_NETIO!NetiopIoWorkItemRoutine+3b
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 2999
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jun  6 04:23:07.232 2011 (UTC - 4:00)
System Uptime: 1 days 20:49:13.322
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireFastMutex+1a )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!ExAcquireFastMutex+1a
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 2999
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun  4 07:30:49.884 2011 (UTC - 4:00)
System Uptime: 2 days 1:33:57.000
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 2999
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jun  2 05:55:44.670 2011 (UTC - 4:00)
System Uptime: 1 days 14:43:26.200
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+425 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  avgemca.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+425
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 2999
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue May 31 15:04:30.555 2011 (UTC - 4:00)
System Uptime: 0 days 22:36:40.027
Probably caused by : memory_corruption ( nt!MiEmptyPageAccessLog+e7 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MiEmptyPageAccessLog+e7
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 2999
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun May 15 15:54:29.514 2011 (UTC - 4:00)
System Uptime: 2 days 21:01:09.978
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+156354 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 2999
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

DxxS · 28 Jun 2011

Updated all the drivers specified, seems much better. ran memtest for 9 passes and got no errors. When I stress tested with Prime95, it ran for about 3-5 minutes the CPU temp got up to 70 degrees on all 3 tests, mu CPU is only rated to 72.5 so i stopped the tests, havent had a chance to run seatools yet, will post back once done.

Windows 7: BSOD, cant collect the data?

BSOD, cant collect the data? problems?