Need Help! BSOD appears when computer idles for a period.


New Member
I've been getting BSODs more frequent now, some when the computer idles for a period of time and I've gotten one or two just going through daily business. I've included the minidump. files if anyone could take a look. As always thanks for any help.



Honorable Member
Microsoft MVP
I've been getting BSODs more frequent now, some when the computer idles for a period of time and I've gotten one or two just going through daily business. I've included the minidump. files if anyone could take a look. As always thanks for any help.

At least half of these crashes were caused by vgapnp.sys/videoprt.sys. Both part of the win 7 OS. I would run a system file check to verify and repair system files and update all the driver listed below.

SFC /SCANNOW Command - System File Checker -

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\K\Desktop\SevenForum\012410-21450-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;* ;srv*e:\symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a07000 PsLoadedModuleList = 0xfffff800`02c44e50
Debug session time: Sun Jan 24 01:11:47.616 2010 (GMT-4)
System Uptime: 0 days 1:01:21.613
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for VIDEOPRT.SYS - 
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {fffffa8004fa6b60, fffffa8004f5d9f0, fffffa8004f59850, 1}

*** ERROR: Module load completed but symbols could not be loaded for vgapnp.sys
Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : vgapnp.sys ( vgapnp+530d )

Followup: MachineOwner

1: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arg1: fffffa8004fa6b60, Pointer to a stuck thread object.  Do .thread then kb on it to find
    the hung location.
Arg2: fffffa8004f5d9f0, Pointer to a DEFERRED_WATCHDOG object.
Arg3: fffffa8004f59850, Pointer to offending driver name.
Arg4: 0000000000000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

Debugging Details:

FAULTING_THREAD:  fffffa8004fa6b60




PROCESS_NAME:  csrss.exe


LAST_CONTROL_TRANSFER:  from fffff88001802c54 to fffff80002a78f00

fffff880`036e9c18 fffff880`01802c54 : 00000000`000000ea fffffa80`04fa6b60 fffffa80`04f5d9f0 fffffa80`04f59850 : nt!KeBugCheckEx
fffff880`036e9c20 fffff800`02a5592f : fffffa80`04fa6b60 fffffa80`04fa6bb0 00000000`0023040c fffffa80`03d9dd80 : VIDEOPRT!VideoPortCompleteDma+0xf04
fffff880`036ea150 fffff800`02a55ce7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`036ea1d0 fffff800`02ffb9c3 : 00000000`0023040c fffffa80`04fb0500 00000000`00001ed0 fffff800`02ffde3e : nt!KiApcInterrupt+0xd7
fffff880`036ea360 fffff800`02ffc03f : fffff800`0300bf60 00000000`00000001 00000000`00000000 fffff800`02fe4000 : hal!x86BiosWriteIoSpace+0x14b
fffff880`036ea3b0 fffff800`02ffbe30 : fffff800`0300bf60 fffff880`036ea480 fffffa80`034f28f0 fffff880`036ea480 : hal!XmEmulateStream+0x10f
fffff880`036ea3e0 fffff800`02ff51c5 : 00000000`00000000 00000000`0000411b fffffa80`04fb0500 fffff880`036ea4d0 : hal!x86BiosExecuteInterruptShadowed+0xfc
fffff880`036ea410 fffff880`0180c0a7 : 00000000`00000000 fffff880`00000000 fffffa80`04fb0500 00000000`00000000 : hal!x86BiosCall+0x45
fffff880`036ea450 fffff880`03ba030d : 00000000`00000007 fffffa80`047da9a8 00000000`00000000 fffff800`02a7b8cd : VIDEOPRT!VideoPortInt10+0x9f
fffff880`036ea4b0 fffff880`03ba0d81 : fffffa80`034f2920 00000000`00000000 00000000`00000000 00000000`00000000 : vgapnp+0x530d
fffff880`036ea510 fffff880`01817eb3 : fffffa80`034f2a00 fffff880`00000000 00000000`00000000 00000000`00000000 : vgapnp+0x5d81
fffff880`036ea5b0 fffff960`000e4b02 : 00000000`00000004 fffffa80`034f28f0 fffff900`c0083de8 fffffa80`047da9a8 : VIDEOPRT!VideoPortCreateEvent+0x16ab
fffff880`036ea660 00000000`00000004 : fffffa80`034f28f0 fffff900`c0083de8 fffffa80`047da9a8 fffff880`036ea7d0 : win32k+0x14b02
fffff880`036ea668 fffffa80`034f28f0 : fffff900`c0083de8 fffffa80`047da9a8 fffff880`036ea7d0 fffff800`00000004 : 0x4
fffff880`036ea670 fffff900`c0083de8 : fffffa80`047da9a8 fffff880`036ea7d0 fffff800`00000004 fffff880`036ea700 : 0xfffffa80`034f28f0
fffff880`036ea678 fffffa80`047da9a8 : fffff880`036ea7d0 fffff800`00000004 fffff880`036ea700 fffff880`036ea6c0 : 0xfffff900`c0083de8
fffff880`036ea680 fffff880`036ea7d0 : fffff800`00000004 fffff880`036ea700 fffff880`036ea6c0 fffff880`036ea6b0 : 0xfffffa80`047da9a8
fffff880`036ea688 fffff800`00000004 : fffff880`036ea700 fffff880`036ea6c0 fffff880`036ea6b0 00000000`00000000 : 0xfffff880`036ea7d0
fffff880`036ea690 fffff880`036ea700 : fffff880`036ea6c0 fffff880`036ea6b0 00000000`00000000 fffffa80`04f5ca90 : 0xfffff800`00000004
fffff880`036ea698 fffff880`036ea6c0 : fffff880`036ea6b0 00000000`00000000 fffffa80`04f5ca90 fffff800`02ac4793 : 0xfffff880`036ea700
fffff880`036ea6a0 fffff880`036ea6b0 : 00000000`00000000 fffffa80`04f5ca90 fffff800`02ac4793 00000000`02060001 : 0xfffff880`036ea6c0
fffff880`036ea6a8 00000000`00000000 : fffffa80`04f5ca90 fffff800`02ac4793 00000000`02060001 fffff880`036ea6c8 : 0xfffff880`036ea6b0

STACK_COMMAND:  .thread 0xfffffa8004fa6b60 ; kb

fffff880`03ba030d 85c0            test    eax,eax


SYMBOL_NAME:  vgapnp+530d

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  vgapnp.sys



BUCKET_ID:  X64_0xEA_IMAGE_vgapnp.sys

Followup: MachineOwner
Old drivers needing updating
rimmpx64.sys        fffff880`03d92000    fffff880`03da5000    0x00013000    0x455e66be    11/17/2006 21:49:50                        
rixdpx64.sys        fffff880`03da5000    fffff880`03dfc000    0x00057000    0x455e8712    11/18/2006 00:07:46                        
b44amd64.sys        fffff880`03e06000    fffff880`03e21000    0x0001b000    0x4562efaa    11/21/2006 08:23:06                        
OEM02Vfx.sys        fffff880`05257000    fffff880`05260000    0x00009000    0x45ebf733    3/5/2007 06:55:47                        
stwrt64.sys        fffff880`04375000    fffff880`043d9000    0x00064000    0x46e9578b    9/13/2007 11:30:19                        
OEM02Dev.sys        fffff880`05000000    fffff880`05041180    0x00041180    0x470d8a84    10/10/2007 22:29:24                        
AVerBDA716x_x64.sys        fffff880`03e44000    fffff880`03fb4400    0x00170400    0x47432e86    11/20/2007 14:59:18                        
VSTCNXT6.SYS        fffff880`05105000    fffff880`051d0000    0x000cb000    0x48f69046    10/15/2008 20:52:22                        
VSTAZL6.SYS        fffff880`050b3000    fffff880`05105000    0x00052000    0x48f69096    10/15/2008 20:53:42                        
VSTDPV6.SYS        fffff880`05262000    fffff880`053d6000    0x00174000    0x48f69189    10/15/2008 20:57:45                        
bcmwl664.sys        fffff880`03c03000    fffff880`03d47000    0x00144000    0x49cc26b1    3/26/2009 21:06:57                        
spldr.sys        fffff880`015df000    fffff880`015e7000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
GEARAspiWDM.sys        fffff880`03bd4000    fffff880`03be1000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04

Last edited:


Yep, the Sigmatel audio driver in particular is causing issues:

Unable to load image \SystemRoot\system32\drivers\stwrt64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for stwrt64.sys
*** ERROR: Module load completed but symbols could not be loaded for stwrt64.sys
Probably caused by : stwrt64.sys ( stwrt64+510d8 )
Update that to the newest possible. Update all the others too that Ken has shown, with the exception of spldr.sys, which is part of the OS and well.

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.