Reboot and select proper boot device...

N_J · Aug 8, 2012

Computer info:

ASUS CM5570
Intel Core 2 Quad CPU Q8200 @ 2.33 GHz
RAM: 6GB
64-bit Vista Home Premium

Upon booting up my friends pc it gives the error in the title. I am booting in safe mode with networking on the pc now as I type. I checked the cables and hardware for any loose connections and also reseated to be sure. I haven't checked the boot sequence yet in the BIOS, will do that after I'm done posting. I have attached the Windows7_Vista_jcgriff2.zip file, but it won't let me attach the html file it is too big.

Thanks for helping I'll let you know about the BIOS later after an expert responds.

N_J

Wrench97 · Aug 8, 2012

Usually they will not boot into safe mode when you see that message it means the hard was not found or is corrupt.
Try doing a start up repair.

N_J · Aug 8, 2012

That was my first thought too....when I shutdown Microsoft installed a bunch of updates. Upon restarting the computer booted fine. I then shutdown and left for a bit. When I restarted the same error occurred so I restarted again to find the OS fired right up. It does sound like the hard drive is going bad.

I would like to pursue this further before buying a new hard drive....what steps should I take next?

Patrick · Aug 8, 2012

Try and run some diagnostics: http://www.carrona.org/hddiag.html

It may tell you if the hard drive is on its way out or not.

Regards,

Patrick

N_J · Aug 8, 2012

Running SeaTools now.

N_J · Aug 9, 2012

Well, all scans with SeaTools came up fine.

Has anyone had a chance to look at the attachment log?

writhziden · Aug 9, 2012

Analysis:

The following is for information purposes only.

Code:

[FONT=lucida console]**************************Sat Jul 23 21:02:43.383 2011 (GMT-6)**************************
Loading Dump File [C:\Users\Mike\Downloads\N_J\Mini072411-01.dmp]
Built by: [B]6002[/B].18327.amd64fre.vistasp2_gdr.101014-0432
System Uptime:[B]1 days 12:56:51.309[/B]
BugCheck Code: [B]BugCheck 50, {ffffe46017c44620, 0, fffffa60007ed001, 7}[/B]
*** WARNING: Unable to verify timestamp for ataport.SYS
*** ERROR: Module load completed but symbols could not be loaded for ataport.SYS
Probably caused by :[B]ataport.SYS ( ataport+1a001 )[/B]
BugCheck Info: [B]PAGE_FAULT_IN_NONPAGED_AREA (50)[/B]
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x50_ataport+1a001[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jul 21 22:06:15.327 2011 (GMT-6)**************************
Loading Dump File [C:\Users\Mike\Downloads\N_J\Mini072211-01.dmp]
Built by: [B]6002[/B].18327.amd64fre.vistasp2_gdr.101014-0432
System Uptime:[B]0 days 0:01:19.388[/B]
BugCheck Code: [B]BugCheck F4, {3, fffffa80084b6c10, fffffa80084b6e48, fffff800022e1640}[/B]
Probably caused by :[B]wininit.exe[/B]
BugCheck Info: [B]CRITICAL_OBJECT_TERMINATION (f4)[/B]
PROCESS_NAME: [B]wininit.exe[/B]
BUGCHECK_STR:  0xF4_84B6780
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID: [B]X64_0xF4_84B6780_IMAGE_wininit.exe[/B]
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q8200  @ 2.33GHz"
MaxSpeed:     2330
CurrentSpeed:[B]2331[/B]
  BIOS Version                  0207   
  BIOS Release Date             05/13/2009
  Manufacturer                  ASUSTeK Computer INC.
  Product Name                  CM5570
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Aug  1 05:10:34.837 2009 (GMT-6)**************************
Loading Dump File [C:\Users\Mike\Downloads\N_J\Mini080109-01.dmp]
Built by: [B]6001[/B].18226.amd64fre.vistasp1_gdr.090302-1506
System Uptime:[B]1 days 8:49:43.648[/B]
BugCheck Code: [B]BugCheck 9F, {3, fffffa8005e26060, fffffa800730e050, fffffa8009dfc010}[/B]
*** WARNING: Unable to verify timestamp for netr28x.sys
*** ERROR: Module load completed but symbols could not be loaded for netr28x.sys
Probably caused by :[B]netr28x.sys[/B]
BugCheck Info: [B]DRIVER_POWER_STATE_FAILURE (9f)[/B]
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x9F_IMAGE_netr28x.sys[/B]
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q8200  @ 2.33GHz"
MaxSpeed:     2330
CurrentSpeed:[B]2331[/B]
  BIOS Version                  0207   
  BIOS Release Date             05/13/2009
  Manufacturer                  ASUSTeK Computer INC.
  Product Name                  CM5570
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:

The following is for information purposes only. Any drivers in red should be updated.

Code:

[FONT=lucida console]**************************Sat Jul 23 21:02:43.383 2011 (GMT-6)**************************
_                             2010  2010 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jul 21 22:06:15.327 2011 (GMT-6)**************************
ASACPI.sys                  Mon Oct 30 20:09:12 2006 (4546B048)
AsIO.sys                    Mon Dec 17 02:11:49 2007 (47663D55)
intelppm.sys                Fri Jan 18 22:52:45 2008 (4791902D)
NWADIenum.sys               Mon Jun  2 17:25:53 2008 (48448181)
nvlddmkm.sys                Tue Oct  7 15:57:15 2008 (48EBDB3B)
netr28x.sys                 Mon Jan 19 07:41:47 2009 (4974912B)
Rtlh64.sys                  Mon Jan 19 23:49:47 2009 (4975740B)
RTKVHD64.sys                Tue Feb  3 02:23:13 2009 (49880D01)
tmtdi.sys                   Tue Jul 20 02:58:07 2010 (4C45651F)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Aug  1 05:10:34.837 2009 (GMT-6)**************************
AsInsHelp64.sys             Thu Jan  3 22:36:10 2008 (477DC5CA)
tmwfp.sys                   Mon Nov 24 04:32:44 2008 (492A90DC)
tmlwf.sys                   Mon Nov 24 04:33:41 2008 (492A9115)
tmtdi.sys                   Mon Nov 24 04:34:20 2008 (492A913C)
vsapint.sys                 Thu May 21 10:55:35 2009 (4A158787)
tmpreflt.sys                Thu May 21 11:04:02 2009 (4A158982)
tmxpflt.sys                 Thu May 21 11:04:05 2009 (4A158985)
[/FONT]

Recommendations:

Two of the three crashes point to a hard disk related issue as the most likely suspect. You said you checked cables, but I am not sure if that means you replaced them with spares to test. Have you tried replacing the cable for the drive?

These hard disk related crashes can also sometimes mean faulty RAM or mismatched RAM. Is the original RAM installed, or have upgrades been made?

You will need to access a command prompt outside Windows to check the hard disk for file system errors and/or bad sectors. There are a few methods that may be used to access a command prompt outside Windows:

Access a Command Prompt using the Windows 7 or Windows Vista Install Disc:
Press Shift + F10 when the installer loads.

Access a Command Prompt from the Windows 7 or Windows Vista System Recovery Options:
You can access a command prompt through the Windows Vista System Recovery Options. To do so,
1. Press F8 every second or every half second when your system first turns on or restarts. Some BIOS systems may not recognize the F8 being pressed unless it is pressed very rapidly. Others require the F8 key to be pressed with a longer interval in between. You may have to try different methods of pressing F8 after the Power On Self Test (POST) screen in order to reach the Advanced Boot Options screen. For reference: the POST screen generally has the name of your motherboard (ASUS, Gigabyte, MSI, etc.) or the name of your system's manufacturer (HP, DELL, Toshiba, etc.) as an image/logo or in text as it proceeds through the test, and it appears just prior to seeing the Windows logo for the Windows loading process.
  
  NOTE: If you are unable to reach the Advanced Boot Options screen, proceed to the Windows Vista System Repair Disc section.
2. Once you have the Advanced Boot Options available, choose Repair Your Computer.
3. Select your language and login to your administrative user.
4. Choose the Command Prompt.
Access a Command Prompt from a Windows 7 or Windows Vista System Repair Disc:
You may also create a Windows Vista Repair Disc by running recdisc.exe to reach the Windows Vista System Recovery Options. If you are unable to create a System Repair Disc on your own system, you may use another system to do so. Make sure you find someone with 32-bit Windows Vista if you have 32-bit Windows Vista or 64-bit Windows Vista if you have 64-bit Windows Vista.

In the Windows Vista System Recovery Options, there is an option to start the command prompt.

Once you have a command prompt available, do the following:
chkdsk /r c:
chkdsk /r d:
chkdsk /r e:
chkdsk /r f:
.etc until you get the message that the volume could not be opened for direct access. For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.

I realize you may only have one disk show up in Windows explorer, but you may have more than one disk through recovery options. This is because the system creates a hidden boot partition (which will be C: in recovery), you may have a recovery partition for your PC that is hidden (which will be D: in recovery), and you will have your primary Windows partition (which may be E: in recovery). A custom PC will likely have at least C: and D: to scan.

Also, if asked whether you would like to force a dismoount on any volumes, choose Y for yes. That message just means the volume is currently being accessed, but dismounting it will not cause any harm.
Run the boot version of Memtest86+. Let it run for at least 7-10 passes (preferably more) or until errors show up.

If you see even one error, stop the test and do the following:
Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!

Click to expand...
1. Shut down and turn off your computer.
2. Unplug all power sources to the system: unplug the power from the outlet/surge protector or PSU (then remove the battery if it is a laptop).
3. Hold down the power button for 30 seconds (for your safety and the safety of the components) to close the circuit and drain all power from components.
4. Remove the casing (or remove the RAM panel if it is a laptop).
5. Remove all but one memory module making sure you are grounded while doing so.
  Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
6. Replace the casing (or replace the RAM panel if it is a laptop) and put the remaining memory module(s) in a safe, static free environment.
7. If the problem persists, repeat steps 1-4 and move the memory module to another slot (while staying grounded, of course).
Do this until all slots have been tested. If all slots fail, the memory module may be bad. Test with one of the remaining modules. Continue one module at a time in one slot at a time until you find a good module and good slot. Test remaining modules in the good slot, test good modules in other slots to find bad slots, etc.
Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. You may want to run both Memtest86+ and the Windows Memory Diagnostics Tool overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

What to do if Windows won't start correctly may also be helpful.

N_J · Aug 11, 2012

It appears that the drive is failing so we will try a new drive and see how that goes.

Thanks for the help everyone.

F5ing · Aug 11, 2012

N_J said:
It appears that the drive is failing so we will try a new drive and see how that goes.

Thanks for the help everyone.

It passed the SeaTools scan, but SMART was tripped?

Reboot and select proper boot device...

N_J

Emeritus, Contributor

Attachments

Wrench97

Administrator, Hardware Expert

N_J

Emeritus, Contributor

Patrick

Sysnative Staff

N_J

Emeritus, Contributor

N_J

Emeritus, Contributor

writhziden

Administrator, .NET/UWP Developer

N_J

Emeritus, Contributor

F5ing

Member