XP BSOD (Bluescreen) - atapi.sys?

OK done that (chkntfs /x c:)

I got a different BSOD (UNMOUNTABLE_BOOT_VOLUME) on rebooting but ok this time.


What now?
 
Wrench97 said:
Run chkdsk> http://support.microsoft.com/kb/315265

An error was detected on device \Device\Harddisk0\D
Click to expand...
Run the hard drive diagnostic utility program, Looks like a WD Blue Sata drive D/L Data lifeguard for DOS (CD) burn to a CD, boot from the CD and run the hard drive long test.
> http://support.wdc.com/product/download.asp?groupid=612&sid=3

Type : Error
Date : 6/19/2012
Source : atapi
Description:
The device, \Device\Ide\IdePort0, did not respond within the timeout period.
Click to expand...
This appears to be a IDE Optical drive, it may be failing or all these issues may add up to a failing motherboard.
Click to expand...


Run the hard drive diagnostics.
 
Disclaimer/warning: long post:

Sorry to jump in here, I'm a new sysnative user, but, I hold formal degrees in both computer hardware and software and have been building systems and servers from the ground up for more than 30 years. That being said, I have seen nearly every type of "strange" computer behavior you can shake a stick at. I found your post/thread when searching for something else online.

Is this system under warranty? If not, based on everything in the post/thread thus far, if this were MY system I would be taking it apart (non-literally and literally both) to perform a *thorough* hardware reliability analysis, and would be dividing the system into functional blocks for reliability testing; power supply, motherboard, RAM, storage (drives), the CPU itself, cooling considerations (are all fans working at all times). Sometimes you can do this conveniently if you purchase/find a used *identical* system to logically swap/interchange and test components, then when all is said and done, if you've replaced any defective components, you also have the benefit of two identical working systems, i.e. a redundant computing set-up (if one system goes down, simply move to a different chair and continue working).

Disclaimer: everything I'm eluding to in this post may branch-off to something more complex and detailed which would require *your* time googling/reading/etc. That being said, you can use various offline testing methods and boot the system from a diagnostic CD such as the UBCD4WIN CD/project, which is bootable XP CD, and ISO image that you download, then burn the CD using a friend's *known good* PC and therefore use the CD to boot the suspect system and perform various hardware tests (first) on the suspect computer.

- A noisy power supply can inject electrical noise into the controlling circuitry on a MB.

- A temperature-sensitive chip on a MB can cause intermittent data bus/transfer errors.

- A temperature-sensitive or faulty CPU can "appear" to work but cause data errors.

- A defective chip on a Hard Drive's controller PCB can cause data errors.

- The storage device itself might be intermittent.

- A CPU fan or case fan could be quitting silently or intermittently.

It really does take quite an effort to narrow-down, weed-out, etc. a faulty hardware component, if it IS hardware ... a process-of-elimination in other words, but when you're done, you'll have increased the reliability of a system by a factor of 1000+. Off-the-shelf "entertainment class" PCs are not designed, built, nor tested for the kind of reliability that consumers really need these days, people nowadays are using workstations for serious financial computing or a home business for example. Many people would say they DO have a reliable, working PC, BUT it could work for 10 more years, or crash tomorrow. When you get or have a reliable PC, make sure to perform regular DRIVE IMAGE backups.

My own approach to strange-behavior systems, is firstly prevention, then hardware reliability testing/validation, then operating system validation, then driver checking/research, application compatibility issues, i.e. keeping a system minimal, then building it up slowly and watching for the reliability "crash", if any. If it were me, I would be rebuilding the system's software config. from the ground-up, carefully, after running extended tests on all hardware components.

This may seem like a big "dump" of information but I'm trying to point you in the right direction, for the long-run (fyi - I type fast). It would of course require your time and research. Again, sorry for "jumping in" please try and see the value of my post, all of which is challenging to communicate in just one forum post (or this post might also someday help someone else who is experiencing rare and extremely strange system behavior).
 
@Since1972, Thanks for your advice. I'm not sure I have all the skills required to do everything you suggest but I am happy to learn step by step. We do have 2 sesktops and 2 laptops in the housr but they are all different build. Is this an 'entertainment class PC'? (No it's not under warranty)

@Wrench 97, I have found a CD -R but at the moment I get a message saying that the web page is unavailable and to try again later so will do that. Do I need to download some software to allow me to burn the CD of have I already got something?

Thanks again
 
By the way, when I boot I get the following error:

The file ir directory c:\WINDOWS\prefetch\GOOGLECRASHHANDLER.EXE-2B7A60484.pf is corrupt and unreadable Please run the chkdsk utility
 
If you need a burning utility the free program Imgburn works well.

The Western Digital site works from here give it another try.

Did you post the logs for Corrine to look at?
 
1. Still doesn't work from here. I can try another machine and save to an external drive? Not something to do with being in the UK is it?

2. Ref Correine, see post #19
 
Yes you can do it on any PC since you have to burn to a CD and boot from the CD anyway.

Google Western Digital Diagniostics your looking for the Data Lifeguard for Dos CD on their web site.
 
OK, I've managed to save to my laptop. How do I check the BIOS settings to make sure it will boot to the CD?
 
OK, I now have the diag f504CD.iso file on my portable drive and have installed ImgBurn on my desktop.

Do I literally burn the file to the CD and then reboot with the CD in the drive? (Is ImgBurn pretty intuitive to use?)
 
OK, it's doing that....

When I re-boot will it just show me something like a BIOS menu where I select to run the diagnostics?
 
I/O Error

Device [1:0:0]TSST CorpDVD+-RW TS-H653B D200 (D:) (ATA)
Scsi Status 0x02
Inerpretation: Check Condition


(Do you need the rest?)
 
I 14:17:12 ImgBurn Version 2.5.7.0 started!
I 14:17:12 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3)
I 14:17:12 Total Physical Memory: 2,085,992 KB - Available: 649,336 KB
W 14:17:12 Drive F:\ (FAT32) does not support single files > 4 GB in size.
I 14:17:12 Initialising SPTI...
I 14:17:12 Searching for SCSI / ATAPI devices...
I 14:17:30 -> Drive 1 - Info: TSSTcorp DVD+-RW TS-H653B D200 (D:) (ATA)
I 14:17:30 Found 1 DVD±RW!
I 15:30:42 Operation Started!
I 15:30:42 Source File: F:\Download\WD\Diag504fCD.iso
I 15:30:42 Source File Sectors: 1,078 (MODE1/2048)
I 15:30:42 Source File Size: 2,207,744 bytes
I 15:30:42 Source File Volume Identifier: 081031_0813
I 15:30:42 Source File File System(s): ISO9660 (Bootable), Joliet
I 15:30:42 Destination Device: [1:0:0] TSSTcorp DVD+-RW TS-H653B D200 (D:) (ATA)
I 15:30:42 Destination Media Type: CD-R (Disc ID: 97m31s01f, Ritek Co.)
I 15:30:42 Destination Media Sectors: 336,223
I 15:30:42 Write Mode: CD
I 15:30:42 Write Type: SAO
I 15:30:42 Write Speed: MAX
I 15:30:42 Lock Volume: Yes
I 15:30:42 Test Mode: No
I 15:30:42 OPC: No
I 15:30:42 BURN-Proof: Enabled
I 15:30:43 Write Speed Successfully Set! - Effective: 8,468 KB/s (48x)
I 15:30:44 Filling Buffer... (80 MB)
I 15:30:45 Writing LeadIn...
W 15:37:09 Failed to Write Sectors 384 - 415 - Reason: Write Error
W 15:37:09 Retrying (1 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (2 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (3 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (4 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (5 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (6 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (7 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (8 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (9 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (10 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (11 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (12 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (13 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (14 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (15 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (16 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (17 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (18 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (19 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:37:09 Retrying (20 of 20)...
W 15:37:09 Retry Failed - Reason: Invalid Address For Write
W 15:41:42 Retrying (21)...
W 15:41:42 Retry Failed - Reason: Invalid Address For Write
W 15:41:45 Retrying (22)...
W 15:41:45 Retry Failed - Reason: Invalid Address For Write
E 15:41:49 Failed to Write Sectors 384 - 415 - Reason: Write Error
E 15:41:49 Next Writable Address: 4294967151
I 15:41:49 Synchronising Cache...
W 15:47:43 User opted to skip the 'Close Track/Session/Disc' functions.
E 15:47:43 Failed to Write Image!
E 15:47:43 Operation Failed! - Duration: 00:17:01
I 15:47:43 Average Write Rate: 0 KB/s (0.0x) - Maximum Write Rate: 0 KB/s (0.0x)
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top