Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD's

25 Feb 2010   #1
telboy1812

windows 7 home premium
 
 
BSOD's

Hello,
My name is Terry, and I am hoping that somebody can give me some help with BSOD’s I have been getting.
System – Mobo – ASUS P5K Ws - Intel Core2 Quad Q6600 @ 2.40Ghz – NVIDIA GeForce 8800 GTS 512 RAM 8,00 GB (4 x 2GB) - Win7 Home Premium 64bit (installed on 22/02/2010 – one day before my first BSOD with this installation.
Getting a lot of BSOD's. I have been getting them for a little while now, and I have tried various installs but with similar results. All installations have been clean (with a drive format first).
History – I ran the RC1 immediately on release, on this machine (in 32 bit) as it stands until I took delivery of preordered Win7. I had no problems with it. I installed it in 32 bit for a while with no problems. Then decided to go 64 bit after checking that my machine and peripherals were OK with updated dvrs etc. Again it was OK. I ran it for some time installing a lot of different apps – mostly on trial – to see if they worked ok with 64bit and which I wanted to buy. I then did a clean install (to get rid of some of the stuff left behind with the trials) and the BSOD’s started a week or so later. I was running 64bit and getting various module errors. I reinstalled with 32bit – same results, but all the errors were ntdskrnl.exe. I read a thread here that suggested RAM and another that was overheating due to dust so I took my machine apart and cleaned it. There was very little dust. I removed the RAM, cleaned it. I had previously run Memtestx86 v4 for over four hours and had no errors and it reported that my RAM was four modules – 3 x 2048mb DDR2-400 and 1 x 2048mb DDR2-333. When the RAM was fitted I was assured that it was all matched and that it was DDR2-800 dimm’s. My mobo manual states that I can mix and match my RAM. I changed the order of the RAM in the slots but it made no difference. I have now reinstalled several times, both 32 and 64 bit and I am now getting a different error – ntoskrnl,exe – each time. I am currently running it as 64bit, and I have only a few apps on the machine.
I apologize if I have gone on too long here but I thought the info may be of help. I have not used a help forum before so it is all new. I have attached the relevant dump files.
Thanks in anticipation.


My System SpecsSystem Spec
.
25 Feb 2010   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by telboy1812 View Post
Hello,
My name is Terry, and I am hoping that somebody can give me some help with BSOD’s I have been getting.
System – Mobo – ASUS P5K Ws - Intel Core2 Quad Q6600 @ 2.40Ghz – NVIDIA GeForce 8800 GTS 512 RAM 8,00 GB (4 x 2GB) - Win7 Home Premium 64bit (installed on 22/02/2010 – one day before my first BSOD with this installation.
Getting a lot of BSOD's. I have been getting them for a little while now, and I have tried various installs but with similar results. All installations have been clean (with a drive format first).
History – I ran the RC1 immediately on release, on this machine (in 32 bit) as it stands until I took delivery of preordered Win7. I had no problems with it. I installed it in 32 bit for a while with no problems. Then decided to go 64 bit after checking that my machine and peripherals were OK with updated dvrs etc. Again it was OK. I ran it for some time installing a lot of different apps – mostly on trial – to see if they worked ok with 64bit and which I wanted to buy. I then did a clean install (to get rid of some of the stuff left behind with the trials) and the BSOD’s started a week or so later. I was running 64bit and getting various module errors. I reinstalled with 32bit – same results, but all the errors were ntdskrnl.exe. I read a thread here that suggested RAM and another that was overheating due to dust so I took my machine apart and cleaned it. There was very little dust. I removed the RAM, cleaned it. I had previously run Memtestx86 v4 for over four hours and had no errors and it reported that my RAM was four modules – 3 x 2048mb DDR2-400 and 1 x 2048mb DDR2-333. When the RAM was fitted I was assured that it was all matched and that it was DDR2-800 dimm’s. My mobo manual states that I can mix and match my RAM. I changed the order of the RAM in the slots but it made no difference. I have now reinstalled several times, both 32 and 64 bit and I am now getting a different error – ntoskrnl,exe – each time. I am currently running it as 64bit, and I have only a few apps on the machine.
I apologize if I have gone on too long here but I thought the info may be of help. I have not used a help forum before so it is all new. I have attached the relevant dump files.
Thanks in anticipation.

Hi Terry and welcome to sevenforums.

These are ar DRIVER_POWER_STATE_FAILURE crashes. Since most of them mention disk.sys I would suspect a HD problem.

I would run a chkdsk /f
sun a system file check
(type cmd in search>right click and run as admin>SFC /SCANNOW

If you are over clocking stop

Let us know the results

Ken


Code:
022310-17035-01.dmp    2/23/2010 6:49:46 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`0783d050    fffff800`00b9c518    fffffa80`0773a700    ntoskrnl.exe    ntoskrnl.exe+71f00        x64    
022410-17550-01.dmp    2/24/2010 8:39:14 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`0783e050    fffff800`00b9c518    fffffa80`06fc29d0    ntoskrnl.exe    ntoskrnl.exe+71f00        x64    
022410-20545-01.dmp    2/24/2010 7:50:12 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`0783e050    fffff800`00b9c518    fffffa80`08ec58f0    ntoskrnl.exe    ntoskrnl.exe+71f00        x64    
022410-27549-01.dmp    2/24/2010 5:54:24 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`0783d050    fffff800`04304518    fffffa80`0840c9d0    ntoskrnl.exe    ntoskrnl.exe+71f00        x64    
022510-20217-01.dmp    2/25/2010 6:40:58 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`0783e050    fffff800`04304518    fffffa80`07d41010    ntoskrnl.exe    ntoskrnl.exe+71f00        x64
Code:
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\022410-20545-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c5ae50
Debug session time: Wed Feb 24 14:47:50.407 2010 (GMT-5)
System Uptime: 0 days 1:22:13.545
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800783e050, fffff80000b9c518, fffffa8008ec58f0}

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

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8008ec58f0

DEVICE_OBJECT: fffffa8007d87060

DRIVER_OBJECT: fffffa8007bcbc50

IMAGE_NAME:  disk.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc11d

MODULE_NAME: disk

FAULTING_MODULE: fffff88001de7000 disk

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002afde23 to fffff80002a8ef00

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02afde23 : 00000000`0000009f 00000000`00000003 fffffa80`0783e050 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02a9afa6 : fffff800`00b9c618 fffff800`00b9c618 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
fffff800`00b9c570 fffff800`02a9a326 : fffffa80`09a7ecd0 fffffa80`09a7ecd0 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02a9ae7e : 0000000b`7c9f4480 fffff800`00b9cc58 00000000`0004d35a fffff800`02c0adc8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02a9a697 : 00000002`b2cad8c6 00000002`0004d35a 00000002`b2cad832 00000000`0000005a : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02a976fa : fffff800`02c07e80 fffff800`02c15c40 00000000`00000000 fffff880`04e55db0 : 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
---------
My System SpecsSystem Spec
25 Feb 2010   #3
telboy1812

windows 7 home premium
 
 

Hi Ken, thanks for your reply.
The test was ok - got this
Verification 100 complete
Windows Resource Protection did not find any integrity violations
I am not overclocking.
had a thought - re the drives - I do run external HDDs, both SATA and PATA in enclosures (both USB and eSATA). Would the bug report refer to one of those. I assume that the report would be on the internal drive (500gb split into C: and D: partitions)
What now?
My System SpecsSystem Spec
.

25 Feb 2010   #4
telboy1812

windows 7 home premium
 
 

Hi Ken - Thanks for the reply.
No, I am not overclocking.
The test found no errors - Verification 100% Windows Resource Protection did not find any integrity violations.
Not sure how to reply here - I sent one but did not see it come up in the forum - i used 'quick reply' - Reckon I should have used Post Reply. Duh?!!
Thanks
My System SpecsSystem Spec
Reply

 BSOD's




Thread Tools



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 08:28.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App