Random BSOD's

mtrain · 14 Feb 2011

I have been getting random BSOD's on my laptop over the last few months and was hoping someone here could analyze them for me. I have attached my minidump files below. Thanks!

Micah

Dell Studio 1558
Intel i7 q820
Windows Ultimate x64
Radeon Mobility 5470
8gb ram

Jonathan_King · 14 Feb 2011

Hello,

Please run driver verifier: Driver Verifier - Enable and Disable

Some drivers to update:

Code:

NETw5s64.sys  Tue Sep 15 15:40:39 2009 (4AAFEDB7)
http://sysnative.com/0x1/DriverReference.html#NETw5s64.sys 

Rt64win7.sys  Thu Aug 20 12:05:06 2009 (4A8D7432)
http://sysnative.com/0x1/DriverReference.html#Rt64win7.sys 

atikmdag.sys  Tue Jun 01 21:37:54 2010 (4C05B5F2)
http://sysnative.com/0x1/DriverReference.html#atikmdag.sys

If the BSODs persist, upload a full jcgriff2 report: https://www.sevenforums.com/crashes-d...tructions.html

...Summary of the dumps:

Code:


Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 11 13:39:44.523 2011 (UTC - 5:00)
System Uptime: 2 days 0:27:46.727
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260
SystemProductName = Studio 1558
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Jan 27 15:26:39.305 2011 (UTC - 5:00)
System Uptime: 0 days 0:08:02.981
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260
SystemProductName = Studio 1558
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Jan 19 00:55:53.329 2011 (UTC - 5:00)
System Uptime: 4 days 10:42:44.000
*** WARNING: Unable to verify timestamp for usbehci.sys
*** ERROR: Module load completed but symbols could not be loaded for usbehci.sys
Probably caused by : usbehci.sys ( usbehci+5fdf )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci+5fdf
SystemProductName = Studio 1558
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Jan 13 19:54:44.463 2011 (UTC - 5:00)
System Uptime: 1 days 8:49:53.808
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_ANALYSIS_INCONCLUSIVE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Jan 11 16:53:12.218 2011 (UTC - 5:00)
System Uptime: 7 days 2:57:36.438
Probably caused by : ntkrnlmp.exe ( nt!IopDisassociateThreadIrp+ac )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!IopDisassociateThreadIrp+ac
SystemProductName = Studio 1558
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Jan  4 12:33:39.403 2011 (UTC - 5:00)
System Uptime: 2 days 4:17:35.163
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiDispatchException+1b9
SystemProductName = Studio 1558
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Dec  7 15:16:26.083 2010 (UTC - 5:00)
System Uptime: 12 days 23:30:04.322
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260
SystemProductName = Studio 1558
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  2 15:00:26.190 2010 (UTC - 5:00)
System Uptime: 1 days 4:43:19.442
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260
SystemProductName = Studio 1558
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

mtrain · 15 Feb 2011

Thanks for the help Jonathan. I've updated the drivers you recommended and I will see if that fixes things.

mtrain · 15 Feb 2011

Also, I was curious how the Driver Verifier program works. Does it just run in the background?

Jonathan_King · 15 Feb 2011

Yes, it runs in the background testing drivers; if it finds a bad one, it will cause a BSOD.

mtrain · 18 Feb 2011

Well now instead of BSOD's the system just shut down randomly and reboots. I've attached the jcgriff info and perfmon info.

Jonathan_King · 18 Feb 2011

I am seeing an inordinate number of domain-related errors:

Code:

Event[39]:
  Log Name: System
  Source: Microsoft-Windows-GroupPolicy
  Date: 2011-02-18T14:58:32.746
  Event ID: 1129
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: micah-win7.Grindline.local
  Description: 
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has succesfully processed. If you do not see a success message for several hours, then contact your administrator.

Event[42]:
  Log Name: System
  Source: Microsoft-Windows-TerminalServices-RemoteConnectionManager
  Date: 2011-02-18T14:58:32.000
  Event ID: 1067
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: micah-win7.Grindline.local
  Description: 
The terminal server cannot register 'TERMSRV' Service Principal Name to be used for server authentication. The following error occured: Access is denied.

Event[324]:
  Log Name: System
  Source: Microsoft-Windows-Time-Service
  Date: 2011-02-18T09:39:36.152
  Event ID: 130
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: micah-win7.Grindline.local
  Description: 
NtpClient was unable to set a domain peer to use as a time source because of failure in establishing  a trust relationship between this computer and the '' domain in order to securely synchronize time. NtpClient will try again in 3473457 minutes and double the reattempt interval thereafter. The error was: The trust relationship between this workstation and the primary domain failed. (0x800706FD)

Event[325]:
  Log Name: System
  Source: Microsoft-Windows-Time-Service
  Date: 2011-02-18T09:39:34.841
  Event ID: 130
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: micah-win7.Grindline.local
  Description: 
NtpClient was unable to set a domain peer to use as a time source because of failure in establishing  a trust relationship between this computer and the '' domain in order to securely synchronize time. NtpClient will try again in 3473457 minutes and double the reattempt interval thereafter. The error was: The trust relationship between this workstation and the primary domain failed. (0x800706FD)

Code:

Event[88]:
  Log Name: System
  Source: NETLOGON
  Date: 2011-02-18T14:58:24.000
  Event ID: 3210
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: micah-win7.Grindline.local
  Description: 
This computer could not authenticate with \\GL01.Grindline.local, a Windows domain controller for domain GRINDLINE, and therefore this computer might deny logon requests. This inability to authenticate might be caused by another computer on the same network using the same name or the password for this computer account is not recognized. If this message appears again, contact your system administrator.

Do you have any idea what may be going on there?

Also, have you run driver verifier yet?

mtrain · 21 Feb 2011

Jonathan,

The computer is part of a exchange domain. I think sometimes the network connection is spotty and it loses connection to the exchange server. I believe the errors are related to that. I have not had a chance to run the driver verifier yet, I will try sometime this week. Is there a specific amount of time I should let it run? Or just let it run until it crashes?

Jonathan_King · 21 Feb 2011

You can let it run for up to 24 hours or so, or until it crashes. Whichever comes first.

mtrain · 21 Feb 2011

I'll run it over the next couple of days and get back to you with the results.