Windows 7 64-bit Frequent BSOD

[jbchi]

Hi, I just built a new PC (see specs on my profile) and installed Windows 7 Ultimate 64-bit. I have now had 4 BSOD in the first week since the Windows 7 install and PC build. It looks like the first one was related to the drivers for my Logitech Quickcam Pro 5000 which I learned is not supported for Windows 7. I installed the Logitech lws110_x64.exe anyway to see if that would work and it did to some degree. I was able to use the webcam with Skype successfully but with some color issues.

The first BSOD also occurred before I had installed the ASUS drivers that came with the motherboard as well as the Radeon 4770 drivers. In addition I updated the firmware on the Crucial 64GB SSD drive that I use as the boot partition where Windows is installed.

The next 3 BSOD were all indicating disk.sys so I am a little concerned and don't know what could be wrong.

I have since uninstalled the Logitech drivers, but I'm just not sure what could be the root of the problem. Attached is a zip file with the 4 .dmp files and also corresponding text files containing the debug analysis.

Any and all help is greatly appreciated!

 

[zigzag3143]

Hi, I just built a new PC (see specs on my profile) and installed Windows 7 Ultimate 64-bit. I have now had 4 BSOD in the first week since the Windows 7 install and PC build. It looks like the first one was related to the drivers for my Logitech Quickcam Pro 5000 which I learned is not supported for Windows 7. I installed the Logitech lws110_x64.exe anyway to see if that would work and it did to some degree. I was able to use the webcam with Skype successfully but with some color issues.

The first BSOD also occurred before I had installed the ASUS drivers that came with the motherboard as well as the Radeon 4770 drivers. In addition I updated the firmware on the Crucial 64GB SSD drive that I use as the boot partition where Windows is installed.

The next 3 BSOD were all indicating disk.sys so I am a little concerned and don't know what could be wrong.

I have since uninstalled the Logitech drivers, but I'm just not sure what could be the root of the problem. Attached is a zip file with the 4 .dmp files and also corresponding text files containing the debug analysis.

Any and all help is greatly appreciated!

these were caused by disk.sys.
I would run a system file check
type cmd in search>right click and and run as admin> sfc /scannow
update the old drivers

If you are over clocking STOP


let us know the results as you may need to run it again

good luck

Ken

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


Loading Dump File [C:\Users\K\Desktop\New folder\021110-192770-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*d:\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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a4f000 PsLoadedModuleList = 0xfffff800`02c8ce50
Debug session time: Thu Feb 11 21:21:03.929 2010 (GMT-5)
System Uptime: 0 days 1:30:06.943
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80064c0050, fffff80000b9c518, fffffa800766fe10}

Probably caused by : disk.sys

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

021210-26956-01.dmp    2/12/2010 6:43:38 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`04a57050    fffff800`00b9c518    fffffa80`07061630    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder\021210-26956-01.dmp    8    15    7600    
021110-26208-01.dmp    2/11/2010 6:51:24 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`06577050    fffff800`00b9c518    fffffa80`075c34a0    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder\021110-26208-01.dmp    8    15    7600    
021110-192770-01.dmp    2/11/2010 8:30:30 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`064c0050    fffff800`00b9c518    fffffa80`0766fe10    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder\021110-192770-01.dmp    8    15    7600    
020710-10389-01.dmp    2/7/2010 12:36:36 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`0420fa00    fffff800`00b9c518    fffffa80`054a9550    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder\020710-10389-01.dmp    8    15    7600

secdrv.SYS        fffff880`06381000    fffff880`0638c000    0x0000b000    0x4508052e    9/13/2006 8:18:38 AM                        
wdcsam64.sys        fffff880`06195000    fffff880`06198880    0x00003880    0x4805bb2c    4/16/2008 3:39:08 AM

 

[jbchi]

Thanks for the quick response Ken. I ran the scan and the result was:

"Windows Resource Protection did not find any integrity violations."

I definitely do not overclock and have not tried nor intend to do so. I haven't found anything indicating that the drivers are old.

Any more suggestions?

I should note that I also detached the webcam from the PC in case that could be an issue. One thing that may also be notable is that following the first BSOD after I installed all of the drivers things were running smooth for about 6 days until yesterday when my wife came home and found the PC was off. Turns out that my electrical meter was replaced by ComEd so there was a power outage. Upon rebooting the BSOD info was displayed and then a few hours later another BSOD occurred. After that I did a shutdown and restart and the startup took a long time compared to the usual 10 seconds it takes (it's fast with an SSD). After that all seemed fine again until tonight when it happened again while Pandora was streaming through Firefox.

Thanks,
jb

 

[jbchi]

Just updated the BIOS on my Asus P7P55D motherboard to the latest version. Hoping this helps. I haven't had a BSOD since yesterday evening.

 

[jbchi]

I had another BSOD this morning unfortunately, so it appears BIOS update did not help. One thing I noticed when I assembled the PC was that as I attached the PSU to the motherboard that the ASUS manual says that they recommend that the PSU provides a minimum of 600W. The PSU that I use is 500W. Is it possible that this is my problem? Below is the analysis:

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


Loading Dump File [E:\Crash_Info\021410-26005-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50
Debug session time: Sun Feb 14 11:57:35.976 2010 (GMT-6)
System Uptime: 0 days 13:55:21.991
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006291050, fffff80000b9c518, fffffa8006abee10}

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: fffffa8006291050, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8006abee10, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8006abee10

DEVICE_OBJECT: fffffa8006226060

DRIVER_OBJECT: fffffa8004ce6e70

IMAGE_NAME:  disk.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc11d

MODULE_NAME: disk

FAULTING_MODULE: fffff880018cb000 disk

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002b3fe23 to fffff80002ad0f00

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02b3fe23 : 00000000`0000009f 00000000`00000003 fffffa80`06291050 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02adcfa6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
fffff800`00b9c570 fffff800`02adc326 : fffffa80`080b2b10 fffffa80`080b2b10 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02adce7e : 00000074`b308ecc6 fffff800`00b9cc58 00000000`0031067f fffff800`02c4d268 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02adc697 : 0000001f`e9196ec2 0000001f`0031067f 0000001f`e9196ea1 00000000`0000007f : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02ad96fa : fffff800`02c49e80 fffff800`02c57c40 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
---------

0: kd> lmvm disk
start             end                 module name
fffff880`018cb000 fffff880`018e1000   disk       (pdb symbols)          c:\symbols\disk.pdb\36B97AD42B4D4B96BDB7534FBA7CD76C2\disk.pdb
    Loaded symbol image file: disk.sys
    Mapped memory image file: c:\symbols\disk.sys\4A5BC11D16000\disk.sys
    Image path: \SystemRoot\system32\DRIVERS\disk.sys
    Image name: disk.sys
    Timestamp:        Mon Jul 13 18:19:57 2009 (4A5BC11D)
    CheckSum:         0001FF1D
    ImageSize:        00016000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     disk.sys
    OriginalFilename: disk.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  PnP Disk Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
0: kd> !devobj fffffa8006226060 f
fffff80002c7f790: Unable to get value of ObpRootDirectoryObject
Device object (fffffa8006226060) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa8006226030
 \Driver\Disk DriverObject fffffa8004ce6e70
Current Irp 00000000 RefCount 0 Type 00000007 Flags 01002050
Vpb fffffa8006226b80 DevExt fffffa80062261b0 DevObjExt fffffa8006226858 Dope fffffa8006044820 
ExtensionFlags (0x00000800)  
                             Unknown flags 0x00000800
AttachedDevice (Upper) fffffa8006056910 \Driver\partmgr
AttachedTo (Lower) fffffa8006291050 \Driver\sbp2port
Device queue is not busy.
0: kd> !drvobj fffffa8004ce6e70 f
fffff80002c7f790: Unable to get value of ObpRootDirectoryObject
fffff80002c7f790: Unable to get value of ObpRootDirectoryObject
Driver object (fffffa8004ce6e70) is for:
 \Driver\Disk
Driver Extension List: (id , addr)

Device Object list:
fffffa8006226060  fffffa8004e71060: Could not read device object


DriverEntry:   fffff880018dd06c    disk!GsDriverEntry
DriverStartIo: 00000000    
DriverUnload:  fffff88001903c90    CLASSPNP!ClassUnload
AddDevice:     00000000    

Dispatch routines:
[00] IRP_MJ_CREATE                      fffff880018e2700    CLASSPNP!ClassGlobalDispatch
[01] IRP_MJ_CREATE_NAMED_PIPE           fffff80002ab765c    nt!IopInvalidDeviceRequest
[02] IRP_MJ_CLOSE                       fffff880018e2700    CLASSPNP!ClassGlobalDispatch
[03] IRP_MJ_READ                        fffff880018e2700    CLASSPNP!ClassGlobalDispatch
[04] IRP_MJ_WRITE                       fffff880018e2700    CLASSPNP!ClassGlobalDispatch
[05] IRP_MJ_QUERY_INFORMATION           fffff80002ab765c    nt!IopInvalidDeviceRequest
[06] IRP_MJ_SET_INFORMATION             fffff80002ab765c    nt!IopInvalidDeviceRequest
[07] IRP_MJ_QUERY_EA                    fffff80002ab765c    nt!IopInvalidDeviceRequest
[08] IRP_MJ_SET_EA                      fffff80002ab765c    nt!IopInvalidDeviceRequest
[09] IRP_MJ_FLUSH_BUFFERS               fffff880018e2700    CLASSPNP!ClassGlobalDispatch
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION    fffff80002ab765c    nt!IopInvalidDeviceRequest
[0b] IRP_MJ_SET_VOLUME_INFORMATION      fffff80002ab765c    nt!IopInvalidDeviceRequest
[0c] IRP_MJ_DIRECTORY_CONTROL           fffff80002ab765c    nt!IopInvalidDeviceRequest
[0d] IRP_MJ_FILE_SYSTEM_CONTROL         fffff80002ab765c    nt!IopInvalidDeviceRequest
[0e] IRP_MJ_DEVICE_CONTROL              fffff880018e2700    CLASSPNP!ClassGlobalDispatch
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL     fffff880018e2700    CLASSPNP!ClassGlobalDispatch
[10] IRP_MJ_SHUTDOWN                    fffff880018e2700    CLASSPNP!ClassGlobalDispatch
[11] IRP_MJ_LOCK_CONTROL                fffff80002ab765c    nt!IopInvalidDeviceRequest
[12] IRP_MJ_CLEANUP                     fffff80002ab765c    nt!IopInvalidDeviceRequest
[13] IRP_MJ_CREATE_MAILSLOT             fffff80002ab765c    nt!IopInvalidDeviceRequest
[14] IRP_MJ_QUERY_SECURITY              fffff80002ab765c    nt!IopInvalidDeviceRequest
[15] IRP_MJ_SET_SECURITY                fffff80002ab765c    nt!IopInvalidDeviceRequest
[16] IRP_MJ_POWER                       fffff880018e2700    CLASSPNP!ClassGlobalDispatch
[17] IRP_MJ_SYSTEM_CONTROL              fffff880018e2700    CLASSPNP!ClassGlobalDispatch
[18] IRP_MJ_DEVICE_CHANGE               fffff80002ab765c    nt!IopInvalidDeviceRequest
[19] IRP_MJ_QUERY_QUOTA                 fffff80002ab765c    nt!IopInvalidDeviceRequest
[1a] IRP_MJ_SET_QUOTA                   fffff80002ab765c    nt!IopInvalidDeviceRequest
[1b] IRP_MJ_PNP                         fffff880018e2700    CLASSPNP!ClassGlobalDispatch

 

[XweAponX]

It looks like the first one was related to the drivers for my Logitech Quickcam Pro 5000 which I learned is not supported for Windows 7

-A lot of Programs and Drivers try to tell you that they "Will Not Work" in Win 7 - But, in fact they DO. Case in Point: I'm using an old Visioneer 8100:

http://www.sevenforums.com/drivers/59069-installing-visioneer-onetouch-8100-scanner.html

I stumbled upon a means of actually installing the windows XP driver package for it!

The first BSOD also occurred before I had installed the ASUS drivers that came with the motherboard as well as the Radeon 4770 drivers. In addition I updated the firmware on the Crucial 64GB SSD drive that I use as the boot partition where Windows is installed.

Obviously, you got past the BSOD's? How, in Safe Mode? The Firmware Revision Probably helped?

The next 3 BSOD were all indicating disk.sys so I am a little concerned and don't know what could be wrong.

You know what I think - It may have been your external drives:

Hard Drives Crucial 64GB SSD
WD 1TB Caviar Black
WD 1TB External My Book II

I have since uninstalled the Logitech drivers, but I'm just not sure what could be the root of the problem. Attached is a zip file with the 4 .dmp files and also corresponding text files containing the debug analysis.

Any and all help is greatly appreciated!

I have right here an IO($)MEG(ᵯ)A 1 TB External HD - Which I had bought for a client and was using in a SERVER machine for extra storage... Needless to say, the drive, after about a month, begain to FAIL to be found on the USB Bus as the computer was booting - and in fact was preventing the system to BOOT- And when you unplugged it, the OS would boot right up, and stay up, and when you plugged the USB box back in, it then allowed you to Browse the drive.

But then about a week ago it just stopped working altogether- And while it was in THAT state, it was totally preventing my Server Tower from BOOTING. Eh! It was one of those problems where the solutions is SO obvious I got to kick my self in the buttocks! So when you take the faulty drive offa the USB Buss, the system fires up like drinking a snort of corn likker!

I've had similar problems with my external drives and/or USB ports on my machines.

What happens, is that while the USB drives are new and relatively unused, the system works great! But then, the external drives develope little errors, and that is when they interfere with the normal operation of the computer - They will cause BOOT HANGS, BSODs, UNEXPECTED REBOOTS... And all kindsa stuff.

So, you may want to CHKDSK your Ext Drives - You may even want to GWSCAN the drives- use GWSCAN version 5.12 - But make sure the External Drives are connected to an SATA Bus! Cos the program refuses to see USB paths. GWSCAN will actually REPAIR Hard Drive Errors that CHKDSK cannot touch.

Check out all those things, see if you are being affected by USB devices!

[EDIT] I just need to add that, although the specific problem I was describing here was on Windows Server 2003, I did see the same symptoms on Windows 7 when I brought that 1 TB Iomega drive home and plugged it in here - Win 7 refused to BOOT while I had the drive attached to the USB-bus.

Later, after I was able to run GWSCAN on the drive and then later CHKDSK - The system then booted normally.

Certai disk errors on a USB-Mounted disk will in fact cause the glitches that we are talkign about here- On Windows 2000, XP, Server, Vista OR Windows 7.

 

[ManOwar2]

You should definately get a new PSU ASAP.

The graphic card you are using do require more power. You are using moderns components on your pc and a 500 watt power supply is not enough for what you are using. Nothing less than a 600 watt power supply would be required. A good 600 watt with at least 50 ampere on a single rail would be the best option for your system. Your 500 watt PSU probably does not have enough ampere.


Your graphic card, along with 2 regular HD and 1 SSD, that's a lot of power, count the CPU and your 4 gig of ram in.

You seriously need to remove at least 1 of your 2 HD if you want some stability, and until you change your PSU do not try to push your graphic card.

 

[jbchi]

Thanks for your suggestion ManOwar2. Replacing the PSU is my last resort at this point given the cost and effort. I'm not straining the system by overclocking or doing anything extraordinary. The Radeon 4770 system requirements specify that a 500W PSU is sufficient. So given that I want to exhaust all other possibilities first.

After looking around a bit I found some information that indicated that some of the Asus driver and utility software, PC Probe II in particular, have been reported to cause problems. I uninstalled the versions I had which came with the CD packaged with the motherboard and installed the latest Win 7 64-bit versions.

I also found info saying that shutting off sleeping in the power plan has helped prevent these issues, so I went ahead and did that.

Before making these changes I had 2 BSODs yesterday, but nothing since making the changes. Will wait and see what happens now.

Does anyone else think that my system is under powered? I just hesitate to jump out and drop $100 on a new PSU and then have to almost completely disassemble my PC if I can avoid it. But I'll do what I have to do.

Thanks again for the very useful feedback!

 

[usasma]

PSU installation:
- remove the PSU from the case (leave the wires attached to the devices)
- install the new PSU in the case.
- remove/replace the wires one connection at a time. When you're able to remove the old PSU - you're done!

 

[jbchi]

Thanks for the info usasma!

So far I have not had another BSOD - knock wood - since I updated all of the Asus utilities and disabled sleep and hibernate from the power plan. I'm going on 3 days now with heavy usage on the PC, so I'm hoping that's a good sign. I've also upgraded my printer from the HP 1012 which is not supported in Windows 7. Among all of these things, something maybe was the culprit - maybe PC Probe II given what I've read from other users.