LLXX Posted February 10, 2006 Share Posted February 10, 2006 If the external drive is working properly, no errors should occur...Especially with external devices I recommend checking the cabling. They are more prone to interference than internal ones as the cables are longer and exposed. Link to comment Share on other sites More sharing options...
cluberti Posted February 10, 2006 Share Posted February 10, 2006 (edited) I hate to say this, but this dump still shows a hardware error with a different stop code from before (it's now a stop 77, 0x77_c000009d:2: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KERNEL_STACK_INPAGE_ERROR (77)The requested page of kernel data could not be read in. Caused bybad block in paging file or disk controller error.In the case when the first arguments is 0 or 1, the stack signaturein the kernel stack was not found. Again, bad hardware.An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) orC000016AL (STATUS_DISK_OPERATION_FAILED) normally indicatesthe data could not be read from the disk due to a badblock. Upon reboot autocheck will run and attempt to map out the badsector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the pagingfile is on a SCSI disk device, then the cabling and termination should bechecked. See the knowledge base article on SCSI termination.Arguments:Arg1: c000009d, status codeArg2: c000009d, i/o status codeArg3: 00000000, page file numberArg4: 01529000, offset into page fileDebugging Details:------------------ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTEDDISK_HARDWARE_ERROR: There was error with disk hardwareBUGCHECK_STR: 0x77_c000009dDEFAULT_BUCKET_ID: DRIVER_FAULTFOLLOWUP_NAME: ntmsdMODULE_NAME: hardware_diskIMAGE_NAME: hardware_diskDEBUG_FLR_IMAGE_TIMESTAMP: 0STACK_COMMAND: kbFAILURE_BUCKET_ID: 0x77_c000009dBUCKET_ID: 0x77_c000009dINTERNAL_BUCKET_URL: http://deviceweb/Bucket/Bucket.aspx?BucketID=1543OCA_CRASHES: 3096 (in last 90 days)Followup: ntmsdI'm sorry, and I can't tell you why quicktime is doing it (other than it's owned by csrss.exe, and appears to be bringing csrss.exe down when it crashes, which is also VERY odd), but the system says there's a hardware error here, and I'm inclined to agree. It may be as simple as running chkdsk /f against all drives on the box, or it could be a bad cable connected to a CD or hard disk - but it's just not something I see going on in any stack in the entire dump. The only stacks I can see with issues are ones with a kernel trap or kernel lock, and these are all csrss.exe processes, which would make sense because if csrss.exe crashes, the whole box will come down.This error can only be caused by a bad block in the page file, or it is indeed a disk controller/subsystem error. My guess is that it's a bad block in your paging file (perhaps move it to a different drive and reboot?), but it could still be the actual controller on your motherboard (or PCI IDE controller) has a problem (drivers or bad hardware). If it's a bad block in the paging file, you should consider your filesystem suspect and should chkdsk /f the drive right away. If it's a controller error, you should consider replacing the drive, the controller, or both.Wish I had a better explanation, but I don't - the issue is the filesystem (specifically in the page file location) or the actual controller/cables/hard disk subsystem. Sorry to be the bearer of bad news, but dumps don't lie . Edited February 10, 2006 by cluberti Link to comment Share on other sites More sharing options...
tb582 Posted February 11, 2006 Author Share Posted February 11, 2006 I hate to say this, but this dump still shows a hardware error with a different stop code from before (it's now a stop 77, 0x77_c000009d:I'm sorry, and I can't tell you why quicktime is doing it (other than it's owned by csrss.exe, and appears to be bringing csrss.exe down when it crashes, which is also VERY odd), but the system says there's a hardware error here, and I'm inclined to agree. It may be as simple as running chkdsk /f against all drives on the box, or it could be a bad cable connected to a CD or hard disk - but it's just not something I see going on in any stack in the entire dump. The only stacks I can see with issues are ones with a kernel trap or kernel lock, and these are all csrss.exe processes, which would make sense because if csrss.exe crashes, the whole box will come down.This error can only be caused by a bad block in the page file, or it is indeed a disk controller/subsystem error. My guess is that it's a bad block in your paging file (perhaps move it to a different drive and reboot?), but it could still be the actual controller on your motherboard (or PCI IDE controller) has a problem (drivers or bad hardware). If it's a bad block in the paging file, you should consider your filesystem suspect and should chkdsk /f the drive right away. If it's a controller error, you should consider replacing the drive, the controller, or both.Wish I had a better explanation, but I don't - the issue is the filesystem (specifically in the page file location) or the actual controller/cables/hard disk subsystem. Sorry to be the bearer of bad news, but dumps don't lie .Hmm ok thanks.I usually try to run chkdsk on all my hdd's about once every 2 weeks... I normally right click the hdd - properties- scan disk, but I'm assuming that if I restart my computer using a 98boot disk I can also run it that way on all drives? What is the proper syntax? to run chkdsk/f on all drives? Link to comment Share on other sites More sharing options...
cluberti Posted February 11, 2006 Share Posted February 11, 2006 but I'm assuming that if I restart my computer using a 98boot disk I can also run it that way on all drives? What is the proper syntax? to run chkdsk/f on all drives?If the drives are NTFS, a 98boot disk will do you no good (it can't read NTFS without 3rd party software). You would run the following command to run chkdsk in "fix" mode (the /f):chkdsk C: /F /RYou should only do one drive at a time (and you should do it after a reboot, do not forcibly dismount any drives if prompted to do so!), and you should run this command for each hard disk volume on your system (obviously substituting the proper drive letter for C:, when appropriate). Link to comment Share on other sites More sharing options...
tb582 Posted February 11, 2006 Author Share Posted February 11, 2006 Where is the log created of each drive scanned? Link to comment Share on other sites More sharing options...
nmX.Memnoch Posted February 11, 2006 Share Posted February 11, 2006 IIRC, the Event Viewer. Link to comment Share on other sites More sharing options...
tb582 Posted February 11, 2006 Author Share Posted February 11, 2006 I'm sorry, and I can't tell you why quicktime is doing it (other than it's owned by csrss.exe, and appears to be bringing csrss.exe down when it crashes, which is also VERY odd), but the system says there's a hardware error here, and I'm inclined to agree. It may be as simple as running chkdsk /f against all drives on the box, or it could be a bad cable connected to a CD or hard disk - but it's just not something I see going on in any stack in the entire dump. The only stacks I can see with issues are ones with a kernel trap or kernel lock, and these are all csrss.exe processes, which would make sense because if csrss.exe crashes, the whole box will come down.Wish I had a better explanation, but I don't - the issue is the filesystem (specifically in the page file location) or the actual controller/cables/hard disk subsystem. Sorry to be the bearer of bad news, but dumps don't lie .I'm going to run chkdsk on all of my drives this weekend, I will report back probably sometime on Sunday Link to comment Share on other sites More sharing options...
tb582 Posted February 15, 2006 Author Share Posted February 15, 2006 I'm going to run chkdsk on all of my drives this weekend, I will report back probably sometime on SundayWell I ran scandisk and it found no errors, but last night I left my computer on and when I got up it had restarted. The event viewer shows this messageEvent Type: InformationEvent Source: USER32Event Category: NoneEvent ID: 1074Date: 2/15/2006Time: 3:05:10 AMUser: NT AUTHORITY\SYSTEMComputer: XEON800FSBDescription:The process winlogon.exe has initiated the restart of XEON800FSB for the following reason: No title for this reason could be found Minor Reason: 0x2 Shutdown Type: reboot Comment: Data:0000: 02 00 02 80 ... Link to comment Share on other sites More sharing options...
cluberti Posted February 15, 2006 Share Posted February 15, 2006 That's odd - you sure that box is clean from viruses, spyware, rootkits, etc? Winlogon initiating a machine restart, without any reason, is pretty fishy. Link to comment Share on other sites More sharing options...
tb582 Posted February 17, 2006 Author Share Posted February 17, 2006 I ran chkdsk on all the drives and didn't find any problems, I'm going to assume that the system restarting was some sort of fluke thing... BUT its the whole quicktime thing that still aggravates me... Link to comment Share on other sites More sharing options...
LLXX Posted February 17, 2006 Share Posted February 17, 2006 (edited) Have you run MemTest86 and Prime95 to test the reliability of your memory and processor?I've seen many strange reboots and errors being caused by corrupted memory or overheating CPUs. Edited February 17, 2006 by LLXX Link to comment Share on other sites More sharing options...
tb582 Posted February 17, 2006 Author Share Posted February 17, 2006 Have you run MemTest86 and Prime95 to test the reliability of your memory and processor?I've seen many strange reboots and errors being caused by corrupted memory or overheating CPUs.No but I plan on running Memtest tonight and Prime's torture test after that... any recommended settings for either? or just the standard tests? Link to comment Share on other sites More sharing options...
LLXX Posted February 17, 2006 Share Posted February 17, 2006 Memtest86 loops repeatedly, so let it run overnight.Prime95 you can just do the standard test. Link to comment Share on other sites More sharing options...
tb582 Posted February 18, 2006 Author Share Posted February 18, 2006 Memtest86 loops repeatedly, so let it run overnight.OK I let Memtest run overnight and it didn't find any errors:Run Time: 11h:03mPasses: 33Errors: 0I'll run the prime stress test tonight Link to comment Share on other sites More sharing options...
tb582 Posted February 19, 2006 Author Share Posted February 19, 2006 Memtest86 loops repeatedly, so let it run overnight.I'll run the prime stress test tonightPrime ran for 13 Hours with no errors and no warnings.Perhaps there is a way to scan for corrupted quicktime files? I think its just one folder on my desktop that's coming up with the quicktime error Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now