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 during startup, or shortly after logging in, every time.


  • Please log in to reply
11 replies to this topic

#1 Carl Berger

Carl Berger

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Florida
  • Local time:03:50 AM

Posted 12 February 2012 - 03:56 AM

Hi there!

I'm working remotely and on behalf of my friend whose computer it is that is having issues. I apologize in advance for any ambiguity that results.

His laptop specifications are listed here: http://www.asus.com/Notebooks/Gaming_Powerhouse/G73SW/#specifications
He is running the Asus G73SW. Windows 7 - 64 bit.

A few days ago he left his computer alone for a few hours and came back to find it blue-screening and restarting. The stop code for these blue screens was: 0x00000f4

Booting in both normal and safe modes causes a BSOD after a very short period of time, however safe mode with command prompt reliably lets him in without blue-screening. From there we were able to setup a chkdsk /f/r to be run on the next restart. We tried this twice: first letting it run for 10 hours, and again letting it run for 42 hours and counting (ongoing). Chkdsk always gets stuck in Phase 4 on file 134453 (which my friend has named Alex). At this point we pretty much assume that chkdsk is hung up and will not progress.

We've tried to run some basic functions in System Recovery Options, but:
- Startup Repair finds no errors
- System Restore mysteriously finds no restore points (his firewall was supposed to manage the setting of regular restore points but appears to have failed in its job)
- System Image Recovery: he never made a recovery image
- Windows Memory Diagnostic: we haven't bothered with this just yet
- Command Prompt: my friend was unable to switch directories from X:\ to C:\

There is data that my friend does not have backed up and wishes to keep, so using the built-in Asus Recovery Partition seems ill-advised at the moment.

We are considering flashing his BIOS to the latest version (205), but I wanted to throw this information out there to see if anyone has a better idea or advises trying something different.

BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,582 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:50 AM

Posted 12 February 2012 - 08:17 AM

If checkdisk does not complete your hard disk is very possibly on the way out or already gone. You can go to the website of the hd manufacturer, download their diagnostic, burn it to cd and run it (or go here: Run hard drive diagnostics: http://www.tacktech.com/display.cfm?ttid=287 (or http://www.bleepingcomputer.com/forums/index.php?showtopic=28744&hl=hard+drive+diagnostic)
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), to make the CD bootable.
For Toshiba hard drives, see here: http://sdd.toshiba.com/main.aspx?Path=ServicesSupport/FujitsuDrivesUSandCanada/SoftwareUtilities#diagnostic

Note : If you do not know how to set your computer to boot from CD follow the steps HERE)

#3 Plastic Nev

Plastic Nev

  • Members
  • 89 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:in front of a monitor in Lancashire UK.
  • Local time:08:50 AM

Posted 12 February 2012 - 10:24 AM

If I can add a little here, if the diagnostic does show the hard drive is failing, I would advise obtaining an adapter or external hard drive caddy.
Make sure you obtain the correct type, either IDE or SATA, though being W7 I expect it will be SATA.
Remove the hard drive in question and connect to another computer using the adapter or caddy, hopefully the important data can then be rescued on to the other computer before the drive dies altogether.

Nev.
Why all the fuss, I already have Windows 8. Three windows at the front, and five at the back since I bought the house.
Posted Image

#4 Carl Berger

Carl Berger
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Florida
  • Local time:03:50 AM

Posted 14 February 2012 - 07:27 AM

Hey guys, thanks for your help! Sorry for the delayed response, but I wanted to do as much as possible before posting again.

To update you:
-We ran a chkdsk /r (no /f this time) and it finished to completion, and now Safe Mode seems to work without crashing (normal Safe Mode).
-From safe mode my friend was able to backup all of his important data to an external hard drive.

So, as per Allan's suggestion we tried to run a hard drive diagnostic, but we're running into more trouble. His hard drive is a Seagate Model ST9750420AS.
Seatools DOS does not find any hard drives.
We then made an Ultimate Boot CD and tried a number of the diagnostic tools, none of which (including all the Seagate ones) can find a hard drive.

Trying a normal Windows boot still results in BSOD, but Safe Mode seems to work. Any advice for how to proceed?

#5 LucheLibre

LucheLibre

  • Members
  • 608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Tennessee
  • Local time:04:50 AM

Posted 14 February 2012 - 08:22 AM

Enter the BIOS and set the HDD operation mode to IDE and try again with SeaTools.

After the test and before you attempt to boot into windows, change the setting back to its original setting.

Edited by LucheLibre, 14 February 2012 - 08:23 AM.

If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~


#6 Carl Berger

Carl Berger
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Florida
  • Local time:03:50 AM

Posted 14 February 2012 - 09:24 AM

We tried what you suggested, Luche, but to no avail. We used Seatools and other diagnostics after switching the operation mode to IDE and the HDD could still not be detected. The diagnostic utilities seemed to 'think' a bit longer before giving us the error, but alas they came just the same.

#7 Allan

Allan

  • BC Advisor
  • 8,582 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:50 AM

Posted 14 February 2012 - 09:40 AM

Just fyi, the /f switch when running chkdsk /r is redunant (/r assumes /f). Anyway, if you can boot to safe mode I'd like to try two things.

First,
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


Second,
open msconfig and on the General tab choose "selective startup" (uncheck all three items) and reboot. Does the problem still occur? If not, start adding items back to msconfig one or two at a time, rebooting after each change, until the problem reappears and you'll have identified the offending process. This is clearly a time consuming procedure, but it is the best way to determine if some process loading with the system is the cause of your problem.
After you've isolated the cause, do not use msconfig to permanently disable the process. Instead, if it is a service go to START - RUN and type: services.msc (then press enter) and disable the service OR, if it a program, you can download & run a simple app such as Mike Lin's Startup Control Panel (http://www.mlin.net/StartupCPL.shtml) to enable, disable, or otherwise manage startup programs.

#8 Phylar

Phylar

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Wisconsin
  • Local time:03:50 AM

Posted 14 February 2012 - 09:51 AM

First lets ignore the xCodes during BSOD. These can and have been known to change depending on the problem regardless if another problem has occurred.

There are quite a few possible fixes above, yet there is a possibility that your RAM is suspect. Remove one card and restart. Replace and remove another, restart. No idea if you have fixed the issue but attempt this and get back to us if you are still having issues.

(Or I could be crazy...actually I likely am. Don't listen to my crazy self! D=)

#9 hamluis

hamluis

    Moderator


  • Moderator
  • 55,545 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:50 AM

Posted 14 February 2012 - 02:51 PM

Please follow the guidance provided by Allan :).

Louis

#10 Carl Berger

Carl Berger
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Florida
  • Local time:03:50 AM

Posted 15 February 2012 - 12:31 AM

Sorry about the misinformed post about chkdsk /r. We didn't actually schedule it; it was recommended by Windows during one of the times we tried to boot up the computer after our previous failed chkdsks. It was a less thorough scan and took much less time but it did say it was fixing things so I assumed it was chkdsk /r. Perhaps it was chkdsk /f instead? I'm unsure.

Here is what BlueScreenView returns:

==================================================
Dump File : 102711-66019-01.dmp
Crash Time : 2011-10-27 00:24:47
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`07f5a060
Parameter 3 : fffff800`04ab5748
Parameter 4 : fffffa80`08511490
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102711-66019-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 1,367,640
==================================================

==================================================
Dump File : 102511-64038-01.dmp
Crash Time : 2011-10-25 01:43:37
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`07bfb060
Parameter 3 : fffff800`04ab9748
Parameter 4 : fffffa80`0cc55e10
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102511-64038-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 938,984
==================================================

==================================================
Dump File : 102011-63430-01.dmp
Crash Time : 2011-10-20 02:29:46
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`07bf8060
Parameter 3 : fffff800`04ab9748
Parameter 4 : fffffa80`0d9c29d0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102011-63430-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 909,624
==================================================

==================================================
Dump File : 101911-33805-01.dmp
Crash Time : 2011-10-19 17:04:18
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`066ee340
Parameter 3 : fffff800`04abd748
Parameter 4 : fffffa80`0dd7f8d0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101911-33805-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 1,605,304
==================================================

==================================================
Dump File : 100511-65848-01.dmp
Crash Time : 2011-10-05 08:53:54
Bug Check String : DRIVER_VERIFIER_DETECTED_VIOLATION
Bug Check Code : 0x000000c4
Parameter 1 : 00000000`00000062
Parameter 2 : fffffa80`07be70d0
Parameter 3 : fffffa80`0d182010
Parameter 4 : 00000000`00000008
Caused By Driver : IDSvia64.sys
Caused By Address : IDSvia64.sys+0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100511-65848-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 294,400
==================================================

==================================================
Dump File : 091111-31278-01.dmp
Crash Time : 2011-09-11 20:09:00
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`07f61060
Parameter 3 : fffff800`04ab73d8
Parameter 4 : fffffa80`084d9c10
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\091111-31278-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 947,720
==================================================

==================================================
Dump File : 090711-19468-01.dmp
Crash Time : 2011-09-07 14:51:06
Bug Check String : DRIVER_VERIFIER_DETECTED_VIOLATION
Bug Check Code : 0x000000c4
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090711-19468-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 295,176
==================================================

==================================================
Dump File : 090411-39655-01.dmp
Crash Time : 2011-09-04 03:44:19
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`07f61060
Parameter 3 : fffff800`00b9c3d8
Parameter 4 : fffffa80`14f8abd0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090411-39655-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 933,456
==================================================

Also,
When trying to uncheck the three items in selective startup we can only successfully uncheck option 2. My friend says he can uncheck option 1, but it returns with a gray check immediately after.

My friend booted his computer after unchecking what he could and there was no BSOD. He re-enabled all the Microsoft services and there was still no BSOD. He was even able to load up his games. The next services he re-enabled were:

Intel Management and Security Application - Local Management Service
Intel Management and Security Application - User Notification Service

He re-enabled these both at the same time and that was where we were thwarted. All Safe Modes then met with BSODs as did all chkdsks. We tried to power through the blue screens and disable the services quickly, but were unable to accomplish this. Finally we gave in and loaded up the F9 ASUS Recovery Options menu and restored his Windows OS to factory settings. Things seem to be working just fine now. Luckily he downloaded all of his important data when Safe Mode was still working.

Thanks for the help guys. At least we think we know which services were to blame now. Perhaps the computer froze during an automatic update involving them?

Edited by Carl Berger, 15 February 2012 - 08:34 AM.


#11 LucheLibre

LucheLibre

  • Members
  • 608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Tennessee
  • Local time:04:50 AM

Posted 15 February 2012 - 08:13 AM

That log doesn't include any of the recent BSODs. Have you run any sort of cleaning program lately?

One question, though: During the last bout of BSODs last year where Norton was crashing the laptop, did you turn off Driver Verifier afterward?

Bug Check String : DRIVER_VERIFIER_DETECTED_VIOLATION
Bug Check Code : 0x000000c4


If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~


#12 Carl Berger

Carl Berger
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Florida
  • Local time:03:50 AM

Posted 15 February 2012 - 08:38 AM

I doubt he ran any cleaning programs recently, but I just added some more information to my previous post.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users