Tech Support banner

Status
Not open for further replies.
1 - 20 of 34 Posts

·
Registered
Joined
·
19 Posts
Discussion Starter #1 (Edited by Moderator)
Hi everyone.

I'm getting crashes frequently on my new computer (Windows 7). Sometimes I'm not even actively using it when it happens. I can be on the internet or word processing and suddenly the monitor fills up with thousands of tiny color spots and the computer shuts down. I'm pretty sure it's a driver issue. Below are a few reports that might help. Any and all help is appreciated. Thanks!

Code:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8009C08050
BCP3: FFFFF80000B9C518
BCP4: FFFFFA8006F9E5A0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\WINDOWS\Minidump\050410-37861-01.dmp
C:\Users\JimDT\AppData\Local\Temp\WER-54194-0.sysdata.xml

Read our privacy statement online:
[url]http://go.microsoft.com/fwlink/?l...cid=0x0409[/url]

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
This is a file from BlueScreenView:
Code:
==================================================
Dump File : 050410-37861-01.dmp
Crash Time : 5/4/2010 3:41:11 PM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`09c08050
Parameter 3 : fffff800`00b9c518
Parameter 4 : fffffa80`06f9e5a0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\050410-37861-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 050410-37939-01.dmp
Crash Time : 5/4/2010 9:21:07 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`09fc8050
Parameter 3 : fffff800`00b9c518
Parameter 4 : fffffa80`08fbe4b0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\050410-37939-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 050310-34632-01.dmp
Crash Time : 5/3/2010 9:39:48 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`09d21050
Parameter 3 : fffff800`00b9c518
Parameter 4 : fffffa80`09facd80
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\050310-34632-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 042710-39078-01.dmp
Crash Time : 4/27/2010 10:35:54 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`09cb2050
Parameter 3 : fffff800`00b9c518
Parameter 4 : fffffa80`0ab75880
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\042710-39078-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
==================================================


Here is the dmp file:
Code:
Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\050510-40014-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*C:\Symbols*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c63000 PsLoadedModuleList = 0xfffff800`02ea0e50
Debug session time: Wed May 5 03:10:20.021 2010 (UTC - 7:00)
System Uptime: 0 days 11:29:53.208
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
............................
Loading User Symbols
Loading unloaded module list
.......
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8009c1b050, fffff80000b9c518, fffffa80072f9010}

Probably caused by : sbp2port.sys

Followup: MachineOwner
---------

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8009c1b050, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa80072f9010, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: sbp2port.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc119

MODULE_NAME: sbp2port

FAULTING_MODULE: fffff88001693000 sbp2port

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff800`00b9c4c8 fffff800`02d421b3 : 00000000`0000009f 00000000`00000003 fffffa80`09c1b050 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02cdf6a6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`00b9c570 fffff800`02cdea26 : fffff800`02e83700 00000000`00287cd1 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02cdf57e : 00000060`60465392 fffff800`00b9cc58 00000000`00287cd1 fffff800`02e51ca8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02cded97 : 00000019`0914fec1 00000019`00287cd1 00000019`0914fe7d 00000000`000000d1 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02cdbdfa : fffff800`02e4de80 fffff800`02e5bc40 00000000`00000001 fffff800`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_disk_IMAGE_sbp2port.sys

BUCKET_ID: X64_0x9F_3_disk_IMAGE_sbp2port.sys

Followup: MachineOwner
 

·
Registered
Joined
·
19 Posts
Discussion Starter #3
Thanks so much for your reply. I have an external hard drive connected to the firewire port. I have Avast a/v software running. I don't think I have a firewall.
 

·
Registered
Joined
·
19 Posts
Discussion Starter #5 (Edited)
So the sbp2port.sys is (or is linked to) the firewire port?

I can unplug the external drive, but it might be hours or days before I'd know if I'd get the BSOD, I guess. (But just to be perfectly clear, I don't actually get the BSOD, I just get random reboots after the screen fills with colored spots). Is there a way to test whether that's the problem if I simply unplug it from the CPU? Maybe unplug and then rerun some form of diagnostic? Should I just unplug it and then plug it back in, letting the computer search for the driver to reinstall?
 

·
Administrator, Manager, Microsoft Support, MVP
Joined
·
34,388 Posts
sbp2port.sys is a Microsoft OS driver related to Firewire and although listed as the probable cause, it is not the actual cause.

The Driver Verifier should help isolate the 3rd party driver causing the trouble, assuming one exists -

Run --> DRIVER VERIFIER - Windows 7 & Vista

I don't know why the video is acting up as you describe and don't see any apparent connection with firewire. You are getting BSODs -

Bugcheck 0x9f (0x3,,,) = driver in an inconsistent power state and blocking an IRP (I/O Request Packet) for too long a time.

Are video drivers updated?

See what D/V can do for you. If D/V flags a driver, it will BSOD your system. Get the VERIFIER_ENABLED minidump and attach it to post.

Regards. . .

jcgriff2

.
 

·
Registered
Joined
·
19 Posts
Discussion Starter #7 (Edited)
Okay, I ran the driver verifier, but it did not BSOD. A message prompted me to srestart, which i did (and it rebooted normally).

How do I get the VERIFIER_ENABLED minidump? I tried going to cmd then I typed "cd c:\" then when I got the "c:\" prompt, I added "verifier /query" Something ran, but it disappeared almost immediately.

As far as the video drivers being updated, I went to device manager and checked and it says the latest driver is installed for the video card. I assume that's the way to check, correct? Thanks again for your help and patience!
 

·
TSF Team Emeritus
Joined
·
6,147 Posts
How do I get the VERIFIER_ENABLED minidump?
Wait until you have a BSOD (it might take a while, but you can still use your PC normally while DV is running) then get it from the same location as the normal dump files (C:\Windows\Minidump)

I went to device manager and checked and it says the latest driver is installed for the video card. I assume that's the way to check, correct?
That way works sometimes, it is far better to just download and install the latest one direct from the chip manufacturers site though.

For NVIDIA chips -> http://www.nvidia.com/Download/index.aspx?lang=en-us

For ATI chips -> http://support.amd.com/us/gpudownload/Pages/index.aspx

Regards,
Reventon
 

·
Registered
Joined
·
19 Posts
Discussion Starter #9
Thanks, reventon. I installed the driver again from ATI. So is the thought that based on the monitor freak out and the sys file error from the dump files, the problem is likely the video card driver AND the firewire connection? With the firewire connection, is it the driver for the firewire port itself or is it the driver for my external hard drive?
 

·
Registered
Joined
·
19 Posts
Discussion Starter #10
I also just checked out the external hard drive site and found that there is a firmware upgrade which "Fixed failure to re-enumerate 1394 (FireWire) when resuming from Windows® Vista™ operating system’s sleep state." I'm running Win 7, but this sounds like it could be part of the problem!
 

·
Registered
Joined
·
19 Posts
Discussion Starter #12
Yes, it can take firewire or USB. I guess I have to switch to to USB to do the firmware update anyway. I was planning to do the firmware update. That doesn't erase the drive, though, right?
 

·
Administrator, Manager, Microsoft Support, MVP
Joined
·
34,388 Posts
I don't see why a firmware update would erase the drive, but there are no guarantees in life. If the files are something you can not do without - back them up elsewhere. Does firewire give you that much of an edge over USB? I have tested both and personally don't find much of a difference, but your use and my use of external may differ greatly.

`
 

·
Registered
Joined
·
19 Posts
Discussion Starter #14
Interesting. I always thought firewire was supposed to be much faster than USB. I've never tested it. I can switch it to USB. Do you think I should still do the firmware upgrade or see how it works in USB first?
 

·
Registered
Joined
·
19 Posts
Discussion Starter #15
So the computer crashed again - same thing with the monitor spots, but this time I got an actual BSOD (as opposed to just shutting down). I went to C:\windows\minidump, but don't see a file there for today. Is that because of the VERIFIER_ENABLED setup?
 

·
TSF Team Emeritus
Joined
·
6,147 Posts
See how it works over USB first. No point risking losing access to your data unless you have to.

EDIT: didn't see your last post, the DV shouldn't affect the creation of dump files but there is a possibility that the system went down so fast it couldn't create one.
 

·
Registered
Joined
·
19 Posts
Discussion Starter #18
Thanks again for the help. I'm way over my head here, but this is the output:


1 Instances of Win32_OSRecoveryConfiguration
Node AutoReboot Caption DebugFilePath DebugInfoType Description ExpandedDebugFilePath ExpandedMiniDumpDirectory KernelDumpOnly MiniDumpDirectory Name OverwriteExistingDebugFile SendAdminAlert SettingID WriteDebugInfo WriteToSystemLog

JIMDT-PC TRUE. . %SystemRoot%\MEMORY.DMP. 2
. . C:\Windows\MEMORY.DMP. C:\Windows\Minidump. FALSE. %SystemRoot%\Minidump. Microsoft Windows 7 Home Premium |C:\Windows|\Device\Harddisk0\Partition3. TRUE. FALSE. . TRUE. TRUE.

1 Instances of Win32_PageFileUsage
Node AllocatedBaseSize Caption CurrentUsage Description InstallDate Name PeakUsage Status TempPageFile

JIMDT-PC 8182
. C:\pagefile.sys. 493
. C:\pagefile.sys. 20100426153046.522061-420. C:\pagefile.sys. 685
. . FALSE.

0 Instances of
Node
 

·
Administrator, Manager, Microsoft Support, MVP
Joined
·
34,388 Posts

·
Registered
Joined
·
19 Posts
Discussion Starter #20
Thanks, jcgriff. Where do I right click and hit run as admin? (I re-ran WMI, but can't find any file called 1.html, so I know I'm doing something wrong.)
 
1 - 20 of 34 Posts
Status
Not open for further replies.
Top