BSOD WinDbg info

mgorman87 · 17 May 2011

I had asked you to run some tests (https://www.sevenforums.com/crashes-d...ml#post1393993) and it appears you haven't run them or you haven't posted the results.

Run the tests and report back the results here

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Tue May 17 09:33:04.723 2011 (UTC - 4:00)
System Uptime: 0 days 19:35:08.705
Probably caused by : memory_corruption
BUGCHECK_STR:  0x50
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 09/08/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu May 12 12:33:23.650 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:14.632
*** ERROR: Module load completed but symbols could not be loaded for ATKDispLowFilter.sys
Probably caused by : ATKDispLowFilter.sys ( ATKDispLowFilter+d8e )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD5
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD5_VRF_ATKDispLowFilter+d8e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon May  9 16:11:12.970 2011 (UTC - 4:00)
System Uptime: 3 days 5:39:00.297
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x50
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 09/08/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue May  3 11:18:51.368 2011 (UTC - 4:00)
System Uptime: 0 days 4:34:54.695
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 09/08/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue May  3 06:42:26.271 2011 (UTC - 4:00)
System Uptime: 0 days 12:27:56.237
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 09/08/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Apr 26 00:19:44.004 2011 (UTC - 4:00)
System Uptime: 0 days 0:29:23.970
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 09/08/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Apr 25 23:48:55.331 2011 (UTC - 4:00)
System Uptime: 0 days 2:04:56.297
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 09/08/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Apr 24 07:41:15.540 2011 (UTC - 4:00)
System Uptime: 0 days 8:03:35.867
Probably caused by : usbhub.sys ( usbhub!UsbhWaitEventWithTimeoutEx+3aa )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhWaitEventWithTimeoutEx+3aa
BiosReleaseDate = 09/08/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Apr 17 17:12:40.911 2011 (UTC - 4:00)
System Uptime: 2 days 12:49:14.258
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 09/08/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Apr  6 10:34:59.195 2011 (UTC - 4:00)
System Uptime: 1 days 2:33:40.161
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 09/08/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Apr  4 11:15:18.008 2011 (UTC - 4:00)
System Uptime: 0 days 5:01:32.335
Probably caused by : usbhub.sys ( usbhub!UsbhWaitEventWithTimeoutEx+3aa )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhWaitEventWithTimeoutEx+3aa
BiosReleaseDate = 09/08/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Mar 25 12:59:15.593 2011 (UTC - 4:00)
System Uptime: 0 days 5:00:09.920
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
BiosReleaseDate = 09/08/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Mar 12 22:35:35.868 2011 (UTC - 4:00)
System Uptime: 0 days 10:28:02.195
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 09/08/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Mar 12 12:06:00.450 2011 (UTC - 4:00)
System Uptime: 1 days 6:46:18.777
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
BiosReleaseDate = 09/08/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar 10 08:23:55.439 2011 (UTC - 4:00)
System Uptime: 0 days 0:04:12.766
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 09/08/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar 10 08:12:07.033 2011 (UTC - 4:00)
System Uptime: 0 days 12:58:00.000
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 09/08/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Mar  5 09:46:41.695 2011 (UTC - 4:00)
System Uptime: 0 days 15:08:25.022
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 09/08/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

NTXHeat · 17 May 2011

I didnt run them as things went well. Either way- posted are the results of the SFC scan. I am rebooting to run the memory test now. Will post back with all test results in some time. Thank you for your continued help.

NTXHeat · 17 May 2011

I am currently running the Prime95 as the tutorial has stated and the long SeaTools test (short test came up with no errors). Just curious- if Prime95 finds any problems how will I be notified? Also- is there some sort of text file that MEMTEST86+ records errors on? I did receive an error and I will follow the tutorial on how to find which stick it is and all but I will need to complete that when I have more time (probably starting with the first stick tonight- overnight). Just curious if it records errors or not. Prime95 has been running for over an hour at an average core temp of around 55 degrees C.

mgorman87 · 19 May 2011

NTXHeat said:

I am currently running the Prime95 as the tutorial has stated and the long SeaTools test (short test came up with no errors). Just curious- if Prime95 finds any problems how will I be notified? Also- is there some sort of text file that MEMTEST86+ records errors on? I did receive an error and I will follow the tutorial on how to find which stick it is and all but I will need to complete that when I have more time (probably starting with the first stick tonight- overnight). Just curious if it records errors or not. Prime95 has been running for over an hour at an average core temp of around 55 degrees C.

Memtest does not record errors. You will be notified in the popup window that errors were found in Prime95. It also creates a report text file.