Spontaneous Reboot On Defrag Attempt

[surefire]

Three days ago, I was doing my normal thing... left the room and came back to find that the computer had shut down all open programs while I was gone. I shutdown, reboot, and when the computer came back on Norton AV was telling me there was an error accessing the system database. Symantec's website gave no valuable info on this error... as usual. Each time I reboot I'd get the same error.

 

So, I decided to backup everything valuable and do a full system scan. During the scan for viruses, about 15 minutes in, the system reboots. When it comes back on, I get the typical windows popup that says 'Your computer has recovered from a serious error'. Here's the specifics

 

C:\WINDOWS\Minidump\Mini030406-04.dmp

C:\DOCUME~1\Owner\LOCALS~1\Temp\WER1.tmp.dir00\sysdata.xml

BCCode : d1 BCP1 : 00000034 BCP2 : 00000002 BCP3 : 00000000

BCP4 : F75418F0 OSVer : 5_1_2600 SP : 0_0 Product : 768_1

 

Several attempts at a full system scan fail in the same way. So I decide to try a defrag of the hard drive. As soon as it starts moving files, bam, reboot.

 

I've really tried to research this kind of problem but haven't found anything definitive. I tried creating a boot image of 'memtest' to run some diagnostics but for some reason the computer won't boot from the CD I created.

 

Using the computer normally hasn't yet resulted in a spontaneous reboot.... It seems to occur only when doing system scans and defrags.

 

As smart as I am with software, I'm out of my element with hardware. This computer is several years old, but I get the feeling there's more life in her if I can figure out what's going on with this.

 

Anyone got any ideas?

 

Thanks in advance.

[curtis]

This may help you out

http://www.computing.net/windowsxp/wwwboard/forum/8407.html

[surefire]

I've tried most of the suggestions from that link, curtis (thanks for the help) but so far nothing has worked. The problems reported on that page you linked to seemed to indicate they were getting the error message every time - even when there was no crash. My computer is indeed crashing. It crashes when I attempt a virus scan or defrag.

 

I still have one or two things to try.

[cajunman4life]

Is this an XP insallation or earlier? Also, if XP, Pro or Home?

[surefire]

That info would be useful, wouldn't it?

 

XP Home. No major changes. The only thing I can think that I updated recently was Adobe Reader 7.

 

For some reason, I can't use a CD on reboot. I put in the XP cd and my computer just boots up normally.

 

I think my next attempt is to reboot to safe mode and try to restore to a previous point.

[surefire]

I think I may be on to something. Possible culprit... Norton Anti Virus. I'll update after I know more.

[cajunman4life]

What version of NAV? 2006/5/4/3/etc...

[Deverill]

My opinon: NAV is evil. Most AV's are evil for an experienced user though. (Disclaimer, I like AVG and use it. The big-names usually have posts in various forums about the problems they cause.)

 

If virii are a possibility (for you or anyone else) I have had great success with stinger (google Stinger.exe). It looks for a lot of viruses but is small, fast, and often works when nothing else will for me anyway.

 

Hope the lead you are onto pans out!

[cajunman4life]

I'll agree with Jim 100% on AVG. Converted to it from NAV, and would never consider going back.

[Samrc]

ME TOO...I'll agree with Jim 100% on AVG. Converted to it from NAV on one computer and PC-cillin (Trend) on another machine, and would never consider going back.

[surefire]

Maybe I'll switch to AVG, but uninstalling Norton didn't do any good. When I do the defrag, it analyzes the disk (C:) and then starts in on the defrag. It compresses the files, then starts moving a file or two around. It seems like every single time it chokes and reboots when the status message says 'moving Inbox'.

 

I also went into the control panel and turned off the setting to reboot on a fatal error (aka stop) so I could see the Blue Screen of Death in all its glory. The message I'm getting starts with

 

'Driver_IRQL_NOT_LESS_OR_EQUAL'

 

@cajumanforlife - 2006

[cajunman4life]

I get that error a lot on my laptop when using Skype and Google Talk for extended (read: 15+ minutes) periods of time. Still haven't quite figured out what it was... my thoughts were something was overheating (my laptop does get pretty warm). You may want to check that out in your computer, as virus scanning will heat your PC up a bit.

[TCH-Rob]

Jack,

 

What is the rest of the BSOD?

[surefire]

Rob,

You're smart to ask... because that's where I found the clue that got things moving in the right direction.

 

STOP: 0x000000D1 (0x00000034, 0x00000002, 0x00000000, 0xF75418f0)

 

IdeChnDr.sys

 

A search for IdeChnDr.sys turned up some info for Intel Ultra ATA Controller (whatever that is) and a search of Intel's feeble support site indicated that they don't really support this driver any more and the last update was in October of 2002.

 

So, in desperation, I went into the control panel, System, Hardware, etc. and clicked on properties for the driver. There was an option to 'rollback' to an earlier version. I closed my eyes and clicked. Rebooted and crossed my fingers.

 

When Frankenstein awoke he was ready to do a defrag. The next thing I did was a ChkDsc. I had done this prior, but with no results. I must have checked a different option (such as to attempt repair automatically) because the chkdsk took much longer and actually found 5 or 6 bad sectors, including one where the virus scan and the defrag had been choking previously. When all 5 steps of chkdsk were done, I reloaded Norton AV and I'm now in the middle of completing a scan of the computer (nothing so far... not surprised).

 

I am trying to decide whether I should put the 2002 driver for the intel ATA controller back. My theory is that there were bad sectors on the hard disk and that they may be fixed now. But obviously there's a part of me that thinks I should let it ride and not f- with it.

 

What took the longest to debug this was the fact that the OS was set to reboot automatically on a major failure. This bypassed the BSOD and so there was no error information for me to see. I had to come across some tips during my research that indicated how to turn off this setting so I could see the error message. Then it was a matter of figuring out what to make of the gobbley gook on the blue screen.

 

Looks like I may not have to buy a new computer just yet.

[TCH-Bruce]

Glad you are back to working condition at least.

[TCH-Rob]

Good, nice to see things are moving along. The reason I asked is because the initial portion you posted from the BSOD could have been any number of problems and the IdeChnDr.sys was the key I was looking for. Ultra ATA is really just the hard drive controller.

[curtis]

Goes to show Patience is a Virtue.

Glad you have it working Jack

[surefire]

Thank you all for your kind words, support, and help!