Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD, driver power state failure, ntoskrnl.exe


  • Please log in to reply
13 replies to this topic

#1 m_cap

m_cap

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:11:50 AM

Posted 13 February 2012 - 03:41 PM

I'm getting (seemingly) random BSOD's, and according to bluescreenview it's caused by ntoskrnl.exe. Not really sure how to fix this, and what it means.

It's a relatively fresh install of windows, built PC

AMD phenom II X4
ECS a750GM-M V7.0 motherboard
G Skill memory (4 GB)
Windows 7 Pro x64
if any of that is relevant.


All windows updates are installed
All drivers are up to date

It says I'm not permitted to upload the .dmp files, so I'll post them on Mediafire, unless there's a way I can view them myself and post them.

Mediafire link to all four dump files: http://www.mediafire.com/?psykx435dqvuabq,8m3hdbhxsquktsg,mth615eme064b6k,m6n5nd3144355os

BC AdBot (Login to Remove)

 


#2 noknojon

noknojon

  • Banned
  • 10,871 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:02:50 AM

Posted 13 February 2012 - 05:03 PM

Hi -
This is a way to see the BSOD records and post them here -

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

Thank You -

#3 Zen Seeker

Zen Seeker

  • Members
  • 695 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:11:50 AM

Posted 13 February 2012 - 05:15 PM

Do you have any more details? I ask because you say it's a relatively fresh install. Does this mean for a short time it was working fine or have you added hardware/software?

As an example I recently installed a Kingston SSD and setup dual boot on it for Win 7 and Linux. Under Linux, which was installed last, it seems fine. Under Windows I was getting BSOD often and under any load. After checking things I found that the manufacturer did have issues with this model of drive but only regarding speed. I later found that MS update KB971033 would fail to install no matter how I tried to apply it, causing BSOD or never finishing and needing a reboot. Further reading showed that boot loaders, good and bad, had issues with this security update. As a quick test I nuked the drive and tried it with just Windows and it was fine.

Have you checked the windows update install list to see if any failed? Have you uninstalled anything you didn't use from the add/remove features list?

Just a few thoughts while you wait for experienced help.

S.

#4 m_cap

m_cap
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:11:50 AM

Posted 13 February 2012 - 06:42 PM

Spoilered for length

Spoiler


I added my TV tuner and scanner, but it was owrking fine immediately afterward.

#5 James Litten

James Litten

    ¿Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:50 AM

Posted 13 February 2012 - 07:23 PM

Hi

Can you tell me which Filenames in the lower pane of BlueScreenView are shaded red when you select

021312-21200-01.dmp

in the upper pane of BlueScreenView?

EDIT: Duh, I didn't see the mediafire link, nevermind :crazy:

Thanks
James

Edited by NeverSayDie, 13 February 2012 - 09:57 PM.


#6 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:50 AM

Posted 13 February 2012 - 09:32 PM

All 4 minidumps had the same bugcheck - 0x9f (0x3,,,) = driver in an inconsistent power state and is blocking an IRP for too long a time (IRP = I/O Request Packet) - and all point at usbhub.sys - a Windows component.

usbhub.sys   Tue Jul 14 10:07:09 2009

System File Protection takes care of this driver, so I suspect either:
  • an attached USB device
  • a driver for an attached USB device
    (or perhaps a bad USB cable, or a broken USB port)
What do you have plugged into USB ports?

I would suggest removing all USB devices and uninstalling all software related to them. If this cures the BSOD's, then reinstall the USB devices one-by-one - waiting to see if they cause BSOD's.

An alternative might be to run Driver Verifier: Driver Verifier will help find a problematic 3rd party driver if one exists.
  • Driver Verifier needs to run 24 hours minimum or until it BSODs your system, whichever is less.
Run Driver Verifier following the instructions DRIVER VERIFIER - Windows 7 & Vista ... by jcgriff2
  • Notes:
  • Do not omit the first step, to create a System Restore point before enabling Driver Verifier.
  • Read the instructions on how to check the Driver Verifier Status.
  • Read the instructions on how To Turn Driver Verifier OFF when you have finished with it.
  • Read the instructions (and record them on paper so you have them if needed) about what to do IF you cannot start the system normally after it crashes under Driver Verifier.
  • Run Driver Verifier for 36 hours unless the system crashes. It doesn't matter whether you are using the computer or not during that time.
If your system BSOD’s under the Driver Verifier:
  • Locate the minidump file:
    • C:\Windows\Minidump <<< folder
  • Zip up the most recent minidump file:
    • Right-click on the most recent minidump file > Send to ... > Compressed (zipped) Folder.
    • The zip file will be located in the same place
  • Attach the zip file to your next post in this thread.
    • When you click on Add Reply, you will see the facility to attach a file just below the box where you type your message
Note: You need to zip up the .dmp file (or files) in order to be able to attach to a post in the BC forums. The forums will allow a .zip file to be attached but not a .dmp file.

The following drivers are outdated and you should attempt to update them:
  • lmimirr.sys Wed Apr 11 2007 ... RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
  • LMIRfsDriver.sys Tue Jul 15 2008 ... RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver

====================
BSOD BUGCHECK SUMMARY
................................................................
Loading Dump File [C:\CactusIsland\m_cap_BC\021312-21200-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Feb 14 07:13:49.475 2012 (UTC + 11:00)
System Uptime: 0 days 3:37:11.269
Probably caused by : usbhub.sys
DRIVER_POWER_STATE_FAILURE (9f)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_usbhub.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`05e00060 fffff800`047ba518 fffffa80`08175010
BiosVersion = 080015
BiosReleaseDate = 08/19/2010
................................................................
Loading Dump File [C:\CactusIsland\m_cap_BC\021112-23649-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Feb 12 04:39:05.982 2012 (UTC + 11:00)
System Uptime: 0 days 20:41:42.402
Probably caused by : usbhub.sys
DRIVER_POWER_STATE_FAILURE (9f)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: cfp.exe
FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_usbhub.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`05c65440 fffff800`047b4748 fffffa80`04bf2c10
................................................................
Loading Dump File [C:\CactusIsland\m_cap_BC\021112-20092-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Feb 12 06:55:47.486 2012 (UTC + 11:00)
System Uptime: 0 days 0:57:54.281
Probably caused by : usbhub.sys
DRIVER_POWER_STATE_FAILURE (9f)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_usbhub.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`03a25440 fffff800`00b9c518 fffffa80`040f6c10
................................................................
Loading Dump File [C:\CactusIsland\m_cap_BC\021112-16676-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Feb 12 05:56:58.858 2012 (UTC + 11:00)
System Uptime: 0 days 1:16:54.653
Probably caused by : usbhub.sys
DRIVER_POWER_STATE_FAILURE (9f)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_usbhub.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`04ff7440 fffff800`047b3518 fffffa80`042adc10
................................................................

Edited by AustrAlien, 13 February 2012 - 09:40 PM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#7 m_cap

m_cap
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:11:50 AM

Posted 13 February 2012 - 10:53 PM

Just the following


ntoskrnl.exe ntoskrnl.exe+df1d3 fffff800`03210000 fffff800`037ec000 0x005dc000 0x4e02aa44 6/22/2011 9:51:48 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16841 (win7_gdr.110622-1503) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe

#8 James Litten

James Litten

    ¿Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:50 AM

Posted 13 February 2012 - 11:22 PM

Hi m_cap

Follow AustrAlien's instructions. He found what I was looking for and has the best solution for troubleshooting :)

James

#9 m_cap

m_cap
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:11:50 AM

Posted 14 February 2012 - 06:22 PM

I have plugged into my USB ports

PCI USB card ports:

Phone, scanner, MP3 player, TV tuner (TV tuner and scanner 24/7, phone and mp3 player on occasion)

Rear integrated ports:

USB cable for camera (rarely used), USB DVD Burner.

Front USB:

Wireless mouse/keyboard combo transceiver.

#10 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:50 AM

Posted 14 February 2012 - 06:29 PM

You have a few USB devices: By a process of elimination, you will need to narrow down the list of possible culprits.

Running Driver Verifier may pinpoint the culprit, but only if it is a 3rd party driver.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#11 m_cap

m_cap
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:11:50 AM

Posted 14 February 2012 - 08:10 PM

I'm running driver verifier as we speak, and I believe it is probably the scanner, or the TV tuner as those are the two most recent. Any idea how to pinpoint which driver is for the scanner, as I manually placed it in the folder?

#12 HolmPC

HolmPC

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:50 PM

Posted 07 May 2012 - 01:56 PM

I came across this thread while searching for solutions to my BSODs which started on both my Windows 7 machines at the same time. I thought it was worth posting my findings, as you mentioned that you have an Asus RT-N56U router, which I have, and have just set up a printer on.

I unplugged the printer, and then removed the printer in Windows, and the problem went away. Having seen this thread I am fairly certain that there is a problem with the Network Printer installation provided with this router.

Does anyone know of any updates that would allow use of a printer connected to this router in Windows 7?

Let us know if following the same steps and removing the printer solves your issue too.

#13 Harold Espera

Harold Espera

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:12:50 AM

Posted 22 July 2012 - 09:03 PM

I had this issue when I re-formated my machine. I've just purchased a ASUS RT-N56U recently. So the the printer driver downloaded from ASUS were also installed to complete my windows installation. Then here comes the BSOD. I never suspected the printer to be the culprit since it is not directly connected to my machine. I've tried updating all drivers, but BSOD won't go away. After removing the printer from the windows device list as suggested by HolmPC, the BSOD goes away.

@HolmPC, thanks for the post, it resolves my BSOD issue. We hope ASUS/Micosoft would be able to fix this soon.

Edited by Harold Espera, 22 July 2012 - 09:05 PM.


#14 HolmPC

HolmPC

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:50 PM

Posted 23 July 2012 - 08:37 AM

Harold, you're very welcome, and it's interesting to have it confirmed that i'm not the only one. I have kept an eye out for updates, but nothing has fixed it for me yet.

I have a Canon MP800 printer, which is not mentioned in the list of supported printers for this router here http://event.asus.com/2009/networks/printersupport/rt-n56u.htm#canon , so I don't expect a solution to be provided by Asus any time soon.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users