Page 1 of 1
[solved] Blue Screen of Death
Posted: Fri May 25, 2007 11:49 pm
by codygo
I have never seen a blue screen of death on windows x64 till today while viewing a render from maxwell studio. No other applications were running.
Here is some info I wrote down.
KERNEL_DATA_INPAGE_ERROR
STOP: 0x0000007a (0xFFFFF6FD6FE98, 0xFFFFFFFFD000185, 0xFFFFFADF8FFD3B80, 0X0000000128E7360
ptdisk.sys - address FFFFFAD8AFFD3B80 at FFFFFADF8FFB9000
*edit: rhino was running in the background as well, but the scene was saved and opened in studio
Posted: Sat May 26, 2007 12:24 am
by zoppo
do you have a freecom traveller external disk?
maybe there is a driver update for it?
Posted: Sat May 26, 2007 12:26 am
by JDHill
Hi codygo,
It looks like the beginning of a hardware problem, google 0x0000007a, KERNEL_DATA_INPAGE_ERROR...your #2 status code, STATUS_IO_DEVICE_ERROR (0xFFFFFFFFD000185) is the one to be looking at. Also, I'd back up any valuable data at the first chance.
Stop 0x7A is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware.
SCSI problems. If the I/O status is C0000185 and the paging file is on a SCSI disk, check the disk cabling and SCSI termination for problems.
Viruses. Check your computer for viruses, using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. Any Windows 2000 file system can be infected by viruses.
Bad block. An I/O status code of 0xC000009C or 0xC000016A normally indicates the data cannot be read from the disk due to a bad block (sector). If you can restart the system after the error, Autochk runs automatically and attempts to map out the bad sector. If Autochk does not scan the hard disk for errors, you can manually launch the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the system before the disk scan begins. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r . For more information about the Recovery Console, see Troubleshooting Tools and Strategies in this book.
0xC0000185, or STATUS_IO_DEVICE_ERROR, is caused by improper termination or defective cabling on SCSI devices, or two devices attempting to use the same IRQ.
Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, the disk cabling and SCSI termination should be checked for problems.
Hope it helps,
JD
Posted: Sat May 26, 2007 12:26 am
by dzowada
From the text, it looks like XP64 does not like what ptdisk.sys was doing.
Using a google search, the only thing that came up was that it could be a part of the driver set for Freecom Traveller Disk. And from the mid 90's too!
Could also be a SCSI driver
The following link has more info:
http://members.driverguide.com/driver/d ... rid=129992
Look in the "file list" tab.
Hope it helps.
Dan
Posted: Sat May 26, 2007 12:28 am
by dzowada
Wow!
Two replies in the time it took me to write mine!
My, arent we a helpfull bunch!
Posted: Sat May 26, 2007 1:23 am
by zoppo
yeah - 3 angels for codygo
Posted: Sat May 26, 2007 2:20 am
by codygo
thanks JD, i ran memtest and came up with no errors, chkdisk /r /f on C said it was clean, haven't touched the hardware in a long time so can't imagine the cables being disconnected, no SCSI drive (though sata kinda behaves like scsi i gather?) I have a 10k raptor as my main disk. I'm in linux right now backing up important files. Otherwise, dunno what else to do since no other funny behavior has cropped up.
As far as ptdisk goes, maybe it was a sloppy note taking effort on my part? maybe it was ftdisk.sys, as i don't have any external drives besides an external card reader that wasn't actively used at the time. My second disk is a serial ide drive with sata adapter, which would be the cheapest thing to die except that wasn't explicitly used at the time either.
my antivirus software is always updated, can't see that being an issue either. Oh well, I'll ride it out after the backup and see.
I'm not sure what "worker threads" are, but they also seem to cause this error?
http://support.microsoft.com/kb/174058[/url]
Posted: Sat May 26, 2007 3:30 am
by JDHill
Well it's good to know everything checks out...I guess anomalies will occur, and if they're going to, MWR can sure supply the stress to help them along. Don't know if it's a thread thing, that other KB looks pretty old...
Cheers,
JD
closure!
Posted: Wed May 30, 2007 5:57 pm
by codygo
after a weekend of ambiguity, I downloaded the western digital diagnostic utility and my 10k raptor failed inspection . I'm sending it back under warranty with RMA. Good news is that it won't cost me anything except for patience reinstalling all my programs and a few bucks for shipping.
Posted: Wed May 30, 2007 10:38 pm
by b-kandor
Just a note: I've had wd drives fail inspection, the I changes my SATA cable and it was fine. In fact, new systems are shipping with 28ga. sata cables and my old ones are all 26ga. I had a bunch of drives dropping out of my arrayusing the thin cables - superstition maybe, but it definately fixed one drive.
Posted: Thu May 31, 2007 4:09 am
by codygo
I replaced the cable but no dice, still showed an error.