daily blue screens after swapping in wrong installer disk for garmin gps

I was installing some map software for my Garmin GPS and when it asked me to reinsert the CD, I accidentally reinserted the wrong Garmin CD. Ever since that day I have been getting blue screens that boot up into a bios message that says fixed disk failure.

I ran WinDbg on the crash dump and this is the info. As you can see it says there: A device which does not exist was specified.

How can I resolve this?

Thanks
-Julie


kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 865dfda0, Terminating object
Arg3: 865dff14, Process image file name
Arg4: 805c773e, Explanatory message (ascii)

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

Unable to load image wpsdrvnt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for wpsdrvnt.sys
*** ERROR: Module load completed but symbols could not be loaded for wpsdrvnt.sys

PROCESS_OBJECT: 865dfda0

IMAGE_NAME: hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAULTING_MODULE: 00000000

PROCESS_NAME: csrss.exe

EXCEPTION_RECORD: aa13e9d8 -- (.exr 0xffffffffaa13e9d8)
ExceptionAddress: 75b8ffb9
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000008
Parameter[1]: 75b8ffb9
Parameter[2]: c000000e
Inpage operation failed at 75b8ffb9, due to I/O error c000000e

EXCEPTION_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The required data was
not placed into memory because of an I/O error status of "0x%08lx ".

IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

EXCEPTION_STR: 0xc0000006_c000000e

FAULTING_IP:
+75b8ffb9
75b8ffb9 ?? ???

BUGCHECK_STR: 0xF4_IOERR_C000000E

FOLLOWUP_IP:
+75b8ffb9
75b8ffb9 ?? ???

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware_disk

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0xF4_IOERR_C000000E_IMAGE_hardware_disk

BUCKET_ID: 0xF4_IOERR_C000000E_IMAGE_hardware_disk

 

Hi jllarson.

What is the full blue screen error message ?

 

That is hard to say because it goes blue screen for a second or two and then reboots. It is pretty hard to catch it.

 

That's OK.

Restart and when the BIOS finishes booting, but before Windows says it is loading press F8 until you get into the Boot Menu. You may have to try several times to get the timing right.

When in the Boot Menu select Disable automatic restart on system failure

The next time you get a blue screen it will stay there so you can read it.

 

Okay, I finally did that and caught it. Here is an image of the blue screen:

http://www.flickr.com/photos/13798836@N00/2050213825/

The message is:

STOP: 0x000000F4 (0x0000003,0x86818DA0,0x86818F14,0x805C773E)

Thanks
-Julie

 

Nice photo! You've saved a lot of time and possible transcription errors by taking a picture. Everyone should do this.

AUMHA.org defines this STOP error:

0x000000F4: CRITICAL_OBJECT_TERMINATION
One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function. Specific causes are many, and often best resolved by a careful history of the problem and the circumstances of the error message. One user, who experienced this on return from Standby mode on Win XP SP2, found the cause was that Windows was installed on a slave drive; compare KB 330100.

It seems pretty unlikely that this would be the true cause.

Here's a nitty-gritty way to (hopefully) identify the BSOD cause:

How to Find BSOD (Blue Screen) Error Messages
http://www.bleepingcomputer.com/forums/topic74712.html

Keep in mind that this may not be the cause - the STOP: 0x000000F4 error
could just be a symptom of a hardware failure, a corrupted OS or a corrupted file system. I suggest that you do a series of tests and fixes, each of which is more comprehensive than the previous one.

Hardware and File System Test Procedures

File System Check and Repair:
Run a File System check on the system partition/volume (usually C: )

In Explorer right-click on the drive letter and select:
Properties > Tools tab > Error Checking: Check now button
Check the box Automatically fix file system errors.
Click the Start button. A message may display about having to restart the PC to run the scan - agree to that and then restart.

If you can't boot into your account or any of the Safe Mode accounts from the F8 boot menu, BUT you have an XP Installation CD (not a Restore/Recovery CD) or a Recovery Console CD then you can boot off the CD to start the installation program. Choose to run the Recovery Console repair utility instead of doing an install by pressing R. From the Recovery Console command-line program you can issue the command:
> chkdsk C: /r /f
Which will repair any problems with the file system on C:

Using either method checks and repairs only the file system. Any corrupted files will remain corrupted and unusable.

How to obtain a Recovery Console Boot Disc to Make XP OS Repairs

The Recovery Console is normally available only if the user has an XP Installation CD, not a Repair CD or a Recovery CD. Microsoft does not offer one !! A little know MS article describes how to make one from the 6-diskette XP Boot diskettes that are available from MS. Others have figured out how to make this boot CD from an XP Installation CD.

You can easily get a self-booting Recovery Console CD from this:
Recovery Console Bootable CD .ISO File Image download
http://www.thecomputerparamedic.com/files/rc.iso

The download is a data image of a CD that is to be burned to a blank CD using a burning program such as Nero, Roxio or by any of these free programs:
CDBurnerXP A good general purpose CD & DVD burning program http://cdburnerxp.se/download.php

Active@ ISO Burner Just burns ISO image files http://www.ntfs.com/iso-burning.htm
ISOBurn Just burns ISO image files http://dpaehl.dd6338.kasserver.com/cdr/isoburn.php


Disk Drive Functionality Test (NOT a file system check):
Run a HDD test utility from your drive’s manufacturer to make sure the drive is functionally OK. Use the diagnostic according to what brand drive you have:

Seagate/Maxtor/Quantum http://www.seagate.com/www/en-us/support/downloads/
Western Digital (WDC) http://support.wdc.com/download/
Hitachi/IBM http://www.hitachigst.com/hdd/support/download.htm
Samsung http://www.samsung.com/in/products/harddiskdrives/utilities/hutil.htm
Fujitsu http://www.fujitsu.com/us/services/computing/storage/hdd/support/utilities.html
Excelstor http://www.excelstor.com/en/download.asp

The brand and model of the drive can be found by:
Control Panel > System > Hardware tab > Device Manager button.
Click the plus sign to the left of Disk drives. This will list all the hard disk drives detected by the OS.

If your PC won't boot into XP then to find the make and model of the hard drive you will need to open the case, possibly remove the drive and look at the label on the top of the drive.

Burning CD and DVD Image ISO Files

An ISO image file must be burned using a burning program that knows how to handle ISO image files. The MS built-in XP burning utility does not. You can use Nero, Roxio or the free CDBurnerXP:
CDBurnerXP http://cdburnerxp.se/download.php

You could instead use a program dedicated to burning just ISO files:
Active@ ISO Burner http://www.ntfs.com/iso-burning.htm

ISOBurn http://dpaehl.dd6338.kasserver.com/cdr/isoburn.php

If the system won't boot into XP then you will have to open the case, possibly remove the hard drive and read the make and model number from the label attached to the top of the drive.

If you know you have hooked up data and power cables to a drive but don't see it in the list this usually means that the drive is completely dead (It is "toast" – a door stop, a boat anchor, a paper weight). But, just to be sure, see if it shows up in the Disk Management utility:
Start > Run > diskmgmt {Enter}
This will show all hard drives and optical drives, even ones that sometimes will not show up in Windows Explorer.


RAM Test:
Download the Memtest86 CD ISO image file and burn it to a blank CD-R from:
Memtest86 http://www.memtest86.com

Set your BIOS so that the computer tries to boot from the CD/DVD drive before trying to boot from the hard disk. Memtest86 will thoroughly test the RAM endlessly. Let it run for at least, say, 3 passes. No errors should be listed. If errors do show up and there is more than one RAM module, test each one individually until you can isolate the bad one.

Burning CD and DVD Image ISO Files

An ISO image file must be burned using a burning program that knows how to handle ISO image files. The MS built-in XP burning utility does not. You can use Nero, Roxio or the free CDBurnerXP:
CDBurnerXP http://cdburnerxp.se/download.php

You could instead use a program dedicated to burning just ISO files:
Active@ ISO Burner http://www.ntfs.com/iso-burning.htm

ISOBurn http://dpaehl.dd6338.kasserver.com/cdr/isoburn.php


Power Supply Outputs Test:
Check the power supply's major outputs with either SpeedFan and/or Everest Home (both free and excellent):

SpeedFan http://www.almico.com/sfdownload.php
Everest Home 2.2 http://www.majorgeeks.com/download4181.html

The +3.3V, +5V and +12V should be within +/-5% of their nominal values.

3V 3.135V to 3.465
5V 4.750V to 5.25V
12V 11.400V to 12.60V

In Speed Fan look in the Readings tab. In Everest look in Computer > Sensor.


CPU Temperature Test:
In Everest Home 2.2 and/or SpeedFan look in Computer > Sensor or the Readings tab, respectively. The CPU temp should never be over 50 degrees Celsius. Overheating can happen as the result of a failing CPU fan (aka "cooler" fan) or excessive dust buildup there. It can also be due to an improperly mounted cooler (heatsink+fan) assembly.

SpeedFan http://www.almico.com/sfdownload.php
Everest Home 2.2 http://www.majorgeeks.com/download4181.html

These tests will go a long way to confirm whether or not your PC is in good shape. Remember that any corrupted files will remain corrupted until reinstalled.


Electronic receipts:
I buy all computer components and software on the web. Shortly after the purchase the seller emails a receipt to me. I then "print" the email message using a free print driver called CutePDF that converts anything printable into a PDF file. I then store the electronic receipt in a separate web purchases receipt folder. This way I will always be able to take advantage of "lifetime warranties" in addition to finite-lived warrantees. Besides, I will always have a record of what I bought and when.

When returning a failed component under warranty, I print out the PDF file to a hard copy and send that back to the manufacturer along with the RMA code (Returned Merchandise Authorization) number supplied by the manufacturer along the component, itself. I get a free replacement for the cost of one-way shipping. The manufacturer pays for delivery of the new part to me.

CutePDF Writer http://www.cutepdf.com

 

It's not coming out of standby. I was definitely in the middle of typing away when it does it.

Thank you
-Julie

 

Geez, all this information oughta keep me busy for a while.

Thanks,
I will try to follow up on all this.