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

Computer won't shutdown, bluescreen on shutdown


  • Please log in to reply
17 replies to this topic

#1 ADLMC

ADLMC

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:09:26 PM

Posted 12 March 2013 - 06:22 PM

Trying to figure out this nagging problem with my HP laptop Pavilion DV7 running Vista 64 bit.

The laptop won't shutdown.  It logs off user, then stalls at shutting down message then finally blue screen error and memory dump files created.

It then reboots to the logon screen.

 

Once logged back in get windows messsage:

 

Windows has recovered from an unexpected shutdown.

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.0.6002.2.2.0.768.3
  Locale ID:    4105

Additional information about the problem:
  BCCode:    1000009f
  BCP1:    0000000000000004
  BCP2:    0000000000000258
  BCP3:    FFFFFA8003CBD040
  BCP4:    0000000000000000
  OS Version:    6_0_6002
  Service Pack:    2_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\Mini031213-02.dmp
  C:\Users\Alex\AppData\Local\Temp\WER-1868689-0.sysdata.xml
  C:\Users\Alex\AppData\Local\Temp\WER4BDE.tmp.version.txt
 

 

 

 

I also have issues trying to use Windows backup utility as it times out when creating a shadow copy.  I belive this is related to above issue.

I can shut down from safemood without any apparent issues.  So I think some driver is corrupt somewhere.

 

Thanks in advance for your help !

 

 



BC AdBot (Login to Remove)

 


m

#2 Allan

Allan

  • BC Advisor
  • 8,395 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:26 PM

Posted 13 March 2013 - 07:05 AM

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

 

 

Also, What is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?



#3 ADLMC

ADLMC
  • Topic Starter

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:09:26 PM

Posted 13 March 2013 - 07:43 AM

Hi Allan, thanks for your support !

Here is requested info:

 

I'm not sure when this problem started, might be result of recent windows update?  or imminent hardware failure??

Computer is very slow at times.  Often get messages "not responding" when launching programs and trying to open files.

Think that's a Vista issue in general though.

 

I scanned for malware (spybot) and viruses(AVG) everything seems clean.

 

 

==================================================
Dump File         : Mini031213-02.dmp
Crash Time        : 12/03/2013 6:42:46 PM
Bug Check String  : DRIVER_POWER_STATE_FAILURE
Bug Check Code    : 0x1000009f
Parameter 1       : 00000000`00000004
Parameter 2       : 00000000`00000258
Parameter 3       : fffffa80`03cbd040
Parameter 4       : 00000000`00000000
Caused By Driver  : msdsm.sys
Caused By Address : msdsm.sys+1e94620
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+5997f
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\Mini031213-02.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 6002
Dump File Size    : 274,368
==================================================

==================================================
Dump File         : Mini031213-01.dmp
Crash Time        : 12/03/2013 9:18:33 AM
Bug Check String  : DRIVER_POWER_STATE_FAILURE
Bug Check Code    : 0x1000009f
Parameter 1       : 00000000`00000004
Parameter 2       : 00000000`00000258
Parameter 3       : fffffa80`03cbd720
Parameter 4       : 00000000`00000000
Caused By Driver  : WMILIB.SYS
Caused By Address : WMILIB.SYS+14510620
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+5997f
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\Mini031213-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 6002
Dump File Size    : 274,368
==================================================

==================================================
Dump File         : Mini031113-02.dmp
Crash Time        : 11/03/2013 4:05:07 PM
Bug Check String  : DRIVER_POWER_STATE_FAILURE
Bug Check Code    : 0x1000009f
Parameter 1       : 00000000`00000004
Parameter 2       : 00000000`00000258
Parameter 3       : fffffa80`03cbd720
Parameter 4       : 00000000`00000000
Caused By Driver  : msdsm.sys
Caused By Address : msdsm.sys+14fa4620
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+5997f
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\Mini031113-02.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 6002
Dump File Size    : 274,368
==================================================

==================================================
Dump File         : Mini031113-01.dmp
Crash Time        : 11/03/2013 2:42:47 PM
Bug Check String  : DRIVER_POWER_STATE_FAILURE
Bug Check Code    : 0x1000009f
Parameter 1       : 00000000`00000004
Parameter 2       : 00000000`00000258
Parameter 3       : fffffa80`03cbdbb0
Parameter 4       : 00000000`00000000
Caused By Driver  : wd.sys
Caused By Address : wd.sys+13e31620
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+5997f
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\Mini031113-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 6002
Dump File Size    : 274,368
==================================================

==================================================
Dump File         : Mini031013-01.dmp
Crash Time        : 10/03/2013 10:15:01 PM
Bug Check String  : DRIVER_POWER_STATE_FAILURE
Bug Check Code    : 0x1000009f
Parameter 1       : 00000000`00000004
Parameter 2       : 00000000`00000258
Parameter 3       : fffffa80`03cbdbb0
Parameter 4       : 00000000`00000000
Caused By Driver  : WMILIB.SYS
Caused By Address : WMILIB.SYS+14ab6620
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+5997f
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\Mini031013-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 6002
Dump File Size    : 274,368
==================================================

==================================================
Dump File         : Mini112212-02.dmp
Crash Time        : 22/11/2012 10:13:42 AM
Bug Check String  : DRIVER_POWER_STATE_FAILURE
Bug Check Code    : 0x1000009f
Parameter 1       : 00000000`00000004
Parameter 2       : 00000000`00000258
Parameter 3       : fffffa80`03cbf720
Parameter 4       : 00000000`00000000
Caused By Driver  : msdsm.sys
Caused By Address : msdsm.sys+14b8c620
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+5a27f
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\Mini112212-02.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 6002
Dump File Size    : 274,368
==================================================

==================================================
Dump File         : Mini112212-01.dmp
Crash Time        : 22/11/2012 9:14:21 AM
Bug Check String  : DRIVER_POWER_STATE_FAILURE
Bug Check Code    : 0x1000009f
Parameter 1       : 00000000`00000004
Parameter 2       : 00000000`00000258
Parameter 3       : fffffa80`03cbd040
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a27f
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+5a27f
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\Mini112212-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 6002
Dump File Size    : 274,424
==================================================
 



#4 Allan

Allan

  • BC Advisor
  • 8,395 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:26 PM

Posted 13 March 2013 - 08:08 AM

No, it is NOT a "Vista issue". Vista should run no differently from any other Windows version.

 

Have you recently updated or installed any drivers? Do you allow Windows Update to install drivers? If you do, you need to disable that feature immediately. Drivers should only be installed by the user and only if and when he chooses to. Additionally, laptop drivers should be obtained ONLY from the website of the laptop manufacturer.

 

1) If new drivers have been installed, please roll them back. You can look in Windows Update's log to see if any new drivers were installed by Windows Update

 

2) If no new drivers have been installed, please go to the HP website and download and install the latest available drivers for your system

 

3) In my opinion Spybot is a useless, old school utility. Please download MalwareBytes and run a full system scan

 

4) If problems still occur at shutdown please post back and we'll try some other measures.



#5 ADLMC

ADLMC
  • Topic Starter

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:09:26 PM

Posted 13 March 2013 - 08:26 AM

Yes I allow automatic updates.  Funny you mention this since I already cross checked some driver files against the hp site and noticed that my laptop has newer versions over the oem drivers.

 

Do you know which drivers in particular?

I'll work on restoring original drivers and get back to you.

I used to run Malwarebytes but I think it was conflicting with AVG at the time.



#6 ADLMC

ADLMC
  • Topic Starter

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:09:26 PM

Posted 13 March 2013 - 08:33 AM

Also want to add that I use a Western Digital My Book Live drive on my network which I haven't accessed for some time (was disconnected).

I was overdue for a backup and that's when I started noticing these issues.

The drive used to be connected to a cascaded router but now connected to primary router - not sure if related to this issue.

I did read online about some issues with this network drive.



#7 Allan

Allan

  • BC Advisor
  • 8,395 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:26 PM

Posted 13 March 2013 - 09:14 AM

The problem you are having is almost always related to drivers.



#8 ADLMC

ADLMC
  • Topic Starter

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:09:26 PM

Posted 13 March 2013 - 10:08 AM

Updated my bios, both my video and audio drivers are more recent than those shown on HP support page.

Trying to roll them back...very slow process since computer takes some time to shutdown before blue screen hits and restarts...

The blue screen ihas striped black lines and can hardly make out the text - is this indicative of a video driver issue?

MY first attempt rolling back the video card driver was not successful.  Probably need to uninstall newer version first...



#9 Allan

Allan

  • BC Advisor
  • 8,395 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:26 PM

Posted 13 March 2013 - 11:11 AM

Yes, sounds like the display adapter. I'd suggest doing just that - boot to safe mode, uninstall the existing driver, install the new one.



#10 ADLMC

ADLMC
  • Topic Starter

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:09:26 PM

Posted 13 March 2013 - 01:37 PM

removed old driver from safe mode and tried to reinstall oem driver however the installation fails.

I rebooted normally and tried again and the device is not loading the driver.

The display card is running in VGA mode right now.

I may consider trying to restore system to an earlier point but I fear things are corrupt...any other ideas?



#11 Allan

Allan

  • BC Advisor
  • 8,395 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:26 PM

Posted 13 March 2013 - 03:09 PM

Can you install the driver in regular mode?



#12 ADLMC

ADLMC
  • Topic Starter

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:09:26 PM

Posted 13 March 2013 - 03:19 PM

Still trying in regular mode.  I downloaded another driver from ATI/AMD but installation wizard is hanging on "Currently Installing: AMD Catalyst Install Manager" 

Been over an hour and I'm afraid to interrupt the install for fear of further corrupting the system !



#13 Allan

Allan

  • BC Advisor
  • 8,395 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:26 PM

Posted 13 March 2013 - 03:22 PM

Okay. If you can use system restore to before the last update that would be great.



#14 ADLMC

ADLMC
  • Topic Starter

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:09:26 PM

Posted 13 March 2013 - 04:21 PM

OK some 2 hours later, I let the regular driver installation complete its task however the installation was unsuccessful.

So next step is system restore...wish me luck !



#15 Allan

Allan

  • BC Advisor
  • 8,395 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:26 PM

Posted 13 March 2013 - 04:56 PM

In the future you might want to consider using disc imaging software on a regular basis. I'm a big advocate of EVERYONE using it. You'll always have a safe haven to which you can return in the event of any problems.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users