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

17 May 2011   #11
mgorman87

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit
 
 

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



My System SpecsSystem Spec
.
17 May 2011   #12
NTXHeat

Windows 7 64bit
 
 

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.
My System SpecsSystem Spec
17 May 2011   #13
NTXHeat

Windows 7 64bit
 
 

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.
My System SpecsSystem Spec
.

19 May 2011   #14
mgorman87

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by NTXHeat View Post
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.
My System SpecsSystem Spec
Reply

 BSOD WinDbg info




Thread Tools




Similar help and support threads
Thread Forum
Random BSOD in Windows 7. Windbg: Probably cause NETIO.SYS
Hello everyone, I have had several BSOD during last 3-4 weeks. They are seemengly random :huh::huh:. Sometimes I have 3 BOSD a day, sometimes I have no BSOD in several days. I have run windbg and it says "BugCheck D1, {50, 2, 0, fffff8800142a232} Probably caused by : NETIO.SYS (...
BSOD Help and Support
BSOD, Windows 7 New Install - WinDbg says ntoskrnl.exe
Hi, I have had a BSOD twice now over the last 2 days. Both times analysis of minidump file says that probable cause is ntoskrnl.exe. I have run your diagnostic tool and have attached the output. Any help here would be much appreciated. I am sure the attached files give you the...
BSOD Help and Support
BSOD Commands - WinDbg
Commands and Extensions for WinDbg !analyze Performs analysis of the dump file, and displays information about the current exception or bugcheck. Parameters for !analyse extension: -v Displays verbose output of the analysis.
Tutorials
BSOD. Windbg indicates Csrss.exe. F4 Code. Can't Figure it out.
Hi all. This is my first post here, so I'll try and make it a good one. I've built my first Enthusiast PC (detailed specs are in my profile) and have had only 1 issue. I've been getting a random BSOD since day 1 of uptime. I've used Windbg, Whocrashed, Memtest, Intelburn Test, Chkdsk /f...
BSOD Help and Support
WinDBG vs BSOD exe
I'm slightly familiar with the BSOD_Windows7_....exe provided on this forum, but I also see reference to the Microsoft-provided WinDBG and would like to understand their purposes. The BSOD thing seems to be mostly a data collection tool, but doesn't have much built in debugging. Is that correct,...
BSOD Help and Support
windbg help for BSOD
Good evening, I have recently been having BSOD issues while playing a game of mine that has been frustrating. Because of this I am trying to learn more about the dmp files and how to read them. From what I see in windbg it keeps saying that the probable cause is ntkrnlmp.exe ( nt! ??...
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 23:13.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App