Radomly Frustrating BSOD needs to vanish :-)

[Apttap]

Hey Guys, I have been experiencing BSOD. I have had it a random times, but I do notice it when I attempt to plug in/operate my Logitech Webcam Pro 9000 (though this has the latest driver).

The pc runs Windows 7 Ultimate and the hardware in this computer is:
iCore 7 860, 4gb 1333mhz ram,
1 Tb+750Gb+250Gb harddrives,
logitech mx5500 revolution keyboard+mouse,
GA Nvidia GTS250 graphics card,
GA p55a ud3r motherboard,
and a new 550W antec powersupply.

I have attached the BSOD minidumps, as while I can see that "ntoskrnl.exe, USBSTOR.sys, cpudrv64.sys" pop up in the BlueScreenView... I am not sure how to further interpret what is displayed to be able to help me.

 

[Jonathan_King]

Looks pretty straightforward. Your USB drivers are causing the problem. Try uninstalling them and install a fresh, up-to-date version.

BugCheck A, {fffff98048edcfe0, 2, 0, fffff80002cbe6a0}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iMapTransfer+24a )

BugCheck C9, {300, fffff88001e7d214, fffff9800df3ccf0, df3ccf0}

Probably caused by : USBSTOR.SYS ( USBSTOR!USBSTOR_Scsi+0 )

The file cpudrv64.sys may be a virus. Download Malwarebytes and run a full scan.

 

[Apttap]

unfortunately all drivers have been updated. Funnily enough I found the problem and it was something the a MS 'techie' did. He had enabled verifier and left it on.

 

[Tews]

Glad its all sorted! ;

 

[jcgriff2]

unfortunately all drivers have been updated. Funnily enough I found the problem and it was something the a MS 'techie' did. He had enabled verifier and left it on.

Driver Verifier should be able to run without flagging a driver and forcing a BSOD. If Driver Verifier was indeed running and BSOD'ing your system, your system troubles are far from over. The next BSOD is just a matter of time.

Regards. . .

jcgriff2

.

 

[Apttap]

unfortunately all drivers have been updated. Funnily enough I found the problem and it was something the a MS 'techie' did. He had enabled verifier and left it on.

Driver Verifier should be able to run without flagging a driver and forcing a BSOD. If Driver Verifier was indeed running and BSOD'ing your system, your system troubles are far from over. The next BSOD is just a matter of time.

Regards. . .

jcgriff2

.

Right you were..... :-( Sadly yet another blue screen and this time saying Driver_Power_State Failure. I have updated every usb device driver this machine runs (at least I think I have).

The latest blue screen mini dump is attached... any ideas where to go from here?

I should note previously I have run memtest, seagate tools, prime and everest but none of these program show any errors or consistent failures (ie the system bsod when it attempts to something, or at regular time periods). My last guess is the cpu or my windows install cd (but nothing shows up when i run the repair function in cmd)?? I have had troubles with the system since day one and reinstall a few times.

 

[zigzag3143]

unfortunately all drivers have been updated. Funnily enough I found the problem and it was something the a MS 'techie' did. He had enabled verifier and left it on.

Driver Verifier should be able to run without flagging a driver and forcing a BSOD. If Driver Verifier was indeed running and BSOD'ing your system, your system troubles are far from over. The next BSOD is just a matter of time.

Regards. . .

jcgriff2

.

Right you were..... :-( Sadly yet another blue screen and this time saying Driver_Power_State Failure. I have updated every usb device driver this machine runs (at least I think I have).

The latest blue screen mini dump is attached... any ideas where to go from here?

I should note previously I have run memtest, seagate tools, prime and everest but none of these program show any errors or consistent failures (ie the system bsod when it attempts to something, or at regular time periods). My last guess is the cpu or my windows install cd (but nothing shows up when i run the repair function in cmd)?? I have had troubles with the system since day one and reinstall a few times.

This one was Probably caused by : disk.sys. I would do the following

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

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


Loading Dump File [C:\Users\K\Desktop\050910-18080-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*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`0303de50
Debug session time: Sun May  9 02:43:02.136 2010 (GMT-4)
System Uptime: 0 days 17:53:55.912
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80069d4060, fffff80000b9c518, fffffa80044df1a0}

Probably caused by : disk.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: fffffa80069d4060, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa80044df1a0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa80044df1a0

DEVICE_OBJECT: fffffa80069e7790

DRIVER_OBJECT: fffffa80042a8e10

IMAGE_NAME:  disk.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc11d

MODULE_NAME: disk

FAULTING_MODULE: fffff88001400000 disk

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002edf4c3 to fffff80002e6d900

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02edf4c3 : 00000000`0000009f 00000000`00000003 fffffa80`069d4060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02e79a66 : fffff800`00b9c630 fffff800`00b9c630 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x26990
fffff800`00b9c570 fffff800`02e78d26 : fffff800`03020700 00000000`003f06b0 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02e7993e : 00000096`06cc08b5 fffff800`00b9cc58 00000000`003f06b0 fffff800`02fee888 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02e79097 : 0000001d`47515ec3 0000001d`003f06b0 0000001d`47515ebd 00000000`000000b0 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02e760fa : fffff800`02feae80 fffff800`02ff8c40 00000000`00000002 fffff880`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_IMAGE_disk.sys

BUCKET_ID:  X64_0x9F_IMAGE_disk.sys

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

 

[Apttap]

Thanks, will get onto doing that in next few hours! Thanks a lot!

MAIN DRIVE/WINDOWS PARTITION C:
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
136960 file records processed. File verification completed.
97 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
179606 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
136960 file SDs/SIDs processed. Cleaning up 493 unused index entries from index $SII of file 0x9.
Cleaning up 493 unused index entries from index $SDH of file 0x9.
Cleaning up 493 unused security descriptors.
Security descriptor verification completed.
21324 data files processed. CHKDSK is verifying Usn Journal...
34126024 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
136944 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
213556692 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

976757759 KB total disk space.
122194284 KB in 112244 files.
69860 KB in 21325 indexes.
0 KB in bad sectors.
266843 KB in use by the system.
65536 KB occupied by the log file.
854226772 KB available on disk.

4096 bytes in each allocation unit.
244189439 total allocation units on disk.
213556693 allocation units available on disk.

Internal Info:
00 17 02 00 cc 09 02 00 9d af 03 00 00 00 00 00 ................
38 3c 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 8<..,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.



DRIVE D:
Chkdsk was executed in read/write mode.

Checking file system on D:
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) Volume dismounted. All opened handles to this volume are now invalid.
Volume label is PHD.

CHKDSK is verifying files (stage 1 of 5)...
4096 file records processed. File verification completed.
0 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
4178 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
4096 file SDs/SIDs processed. Cleaning up 4 unused index entries from index $SII of file 0x9.
Cleaning up 4 unused index entries from index $SDH of file 0x9.
Cleaning up 4 unused security descriptors.
Security descriptor verification completed.
42 data files processed. CHKDSK is verifying Usn Journal...
2080656 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
4080 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
3834438 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

25599999 KB total disk space.
10187880 KB in 3351 files.
1488 KB in 43 indexes.
0 KB in bad sectors.
72875 KB in use by the system.
65536 KB occupied by the log file.
15337756 KB available on disk.

4096 bytes in each allocation unit.
6399999 total allocation units on disk.
3834439 allocation units available on disk.



DRIVE F:
Chkdsk was executed in read/write mode.

Checking file system on F:
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) Volume dismounted. All opened handles to this volume are now invalid.

CHKDSK is verifying files (stage 1 of 5)...
8960 file records processed. File verification completed.
1 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
10652 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
8960 file SDs/SIDs processed. Cleaning up 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.
Cleaning up 3 unused security descriptors.
Security descriptor verification completed.
847 data files processed. CHKDSK is verifying Usn Journal...
4420464 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
8944 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
30698091 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

218594303 KB total disk space.
95712320 KB in 8071 files.
3428 KB in 848 indexes.
0 KB in bad sectors.
86187 KB in use by the system.
65536 KB occupied by the log file.
122792368 KB available on disk.

4096 bytes in each allocation unit.
54648575 total allocation units on disk.
30698092 allocation units available on disk.



DRIVE E:
Chkdsk was executed in read/write mode.

Checking file system on E:
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) Volume dismounted. All opened handles to this volume are now invalid.

CHKDSK is verifying files (stage 1 of 5)...
12288 file records processed. File verification completed.
0 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
12422 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
12288 file SDs/SIDs processed. Cleaning up 6 unused index entries from index $SII of file 0x9.
Cleaning up 6 unused index entries from index $SDH of file 0x9.
Cleaning up 6 unused security descriptors.
Security descriptor verification completed.
68 data files processed. CHKDSK is verifying Usn Journal...
9719776 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
12272 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
174488987 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

732572000 KB total disk space.
34505332 KB in 917 files.
396 KB in 69 indexes.
0 KB in bad sectors.
110320 KB in use by the system.
65536 KB occupied by the log file.
697955952 KB available on disk.

4096 bytes in each allocation unit.
183143000 total allocation units on disk.
174488988 allocation units available on disk.

 

[Apttap]

I also ran sfc /scannow... but that found nothing worth noting...

 

[jcgriff2]

I see chkdsk found no errors on the 4 drives/ partitions.

Are they partitions of a single drive or seperate HDDs? Are any external USB drives? If so, unplug it and see if BSODs persist.

Any Internet Security apps, e.g., NIS, N360, KIS, McAfee, etc... installed?

Any encryption of any kind? Any other partitions/ drives other than the 4 NTFS listed?

 

[Apttap]

I see chkdsk found no errors on the 4 drives/ partitions.

Are they partitions of a single drive or seperate HDDs? Are any external USB drives? If so, unplug it and see if BSODs persist.

Any Internet Security apps, e.g., NIS, N360, KIS, McAfee, etc... installed?

Any encryption of any kind? Any other partitions/ drives other than the 4 NTFS listed?

Hi!

There are no external usb drives attached at present. (there was a maxtor one touch 4 mini 160 gb attached but that has been retired, and recently an iomega 1tb drive but that is run through a qnap ts 219p now)
There are three internal sata drives. two drives are single partitions, and the third and smallest one has two partitions (one of which is encrypted with bitlocker).
The security installed is Avast Free Antivirus and Malwarebytes.
The only drive not listed is an iSCSI target drive on a QNAP TS219P (I doubt this is causing the problem as it was recently added to the mix [after bsod first occured] and it is only written to when backing up with windows backup/restore).
Not sure how this might factor, but I also run 'Dropbox' and Teamviewer.

Thanks!

 

[Jonathan_King]

Please upload any new dmps as they come. Be sure to delete the old ones from the minidump folder now to avoid confusion.

Check to see if you can find updated chipset drivers.

 

[Apttap]

Please upload any new dmps as they come. Be sure to delete the old ones from the minidump folder now to avoid confusion.

Check to see if you can find updated chipset drivers.

Thanks, I will keep you posted. Though it may be a while... Oh and I have the latest chipset already Intel P55 1.1.2.1007, though apparently it is beta according to intel's site but recommend by Gigabyte....

 

[CarlTR6]

Sometimes, the beta and even the latest drivers do not work the best. You may have to experiment with different drivers to see which is best for your system.