Can't find cause of BSOD

BTW boot time on my mk4 cf-29 on a fresh install of win xp pro is literally 15 seconds on the stock hd, so the stock hd is at least capable of providing that level of performance!

 

Update:

I've been running the crap out this machine since the last update - downloading videos, fast page changes, whatever I want without holding back. Zero crashes. I even let it run all day today after unplugging it, taking it in my truck and letting it hibernate several times. The combination of correcting the drivers, and registry checking seems to have solved the problem. I thank you all for your advice and will stop adding to this thread unless the ugly BSOD head rears itself again.

This site rocks!

 

Bad news...Been almost five days now, started computer and had a cmos clock error right off the bat. Then the machine ran slow and the cpu was bouncing up and down to %100 and back. I eventually went for re-start and had a BSOD with

STOP:0X0000007A (0XC03E5308, 0XC000000E, 0XF94C2302, 0X09C55860)

Atapi.sys address F94C2303 BASE AT F94B1000, DATESTAMP 4802539d

Could I be having a cmos battery problem that is causing this or is the HD likely hooped?

I tried to restart off the XP Pro update disk and it eventually told me that there are no previous Windows versions found on the HD and to put one in the CD ROM then press enter. I put my WIN98 in and it could not continue due to a partition problem.

 

ooo HDD fail sounds like to me!

 

ATAPI.sys is one of the core IDE interface processes; kindof a catch 22 here. If the file is corrupt, it will make anything on an ide(or SATA - it's all on the same PCI Bridge) bus flaky as a buttermilk biscuit.

Of course, then you have to ask WHAT CAUSED IT TO BE CORRUPTED? If you had a system crash caused by a bunk CMOS battery that sure could be it; or it could be a genuine corrupted sector on your HDD.

I'd try replacing the CMOS batt, then rename the atapi.sys file in your Windows build (I think it's in the windows/system32/drivers folder) folder to anything else, then either copy it from the i386 folder of an install disk of the correct version or let Windows reinstall it via the dll cache.

After that, if everything seems to run right, I'd DEF get after that HDD with an aggressive surface scan... or perhaps it might be better to pop it in a desktop as a slave and do that surface scan first, before you disassemble your Toughbook to get at that CMOS batt.

mnem
Bits & Bytes & Bobbles...

 

I think it is the hard drive, read post #48

To check if the bios battery is the issue set bios to factort defaults, then change something in the bios and see if it remains changed
Another hint would be if you had to reset date and time settings in the bios

I have sold dozens of cf-28's and have yet to change a bios battery on this model
I have had issues with the stock factory 30gb hard drive though, and have replaced at least five hard drives due to failure


Alex

 

I would agree with Alex. I have replaced the battery in a couple of IBM Transnotes and even a couple of HP Handhelds, but never a TB. Plus, everything I could find while researching the error code leads to the HD going south. I learned my lesson long ago with HD's, if they start to smell just a bit, big time decay is usually right around the corner. Time for new dilitheum crystals captain!

 

X3 on hard drive...

 

well I did warn you back on post #24 Then again now that I read that post I must have been drinking or something because I pointed my finger at the hard drive then started slamming on the optical... wow

 

x4 on the bad hard drive.

My old laptop had the BSOD on atapi.sys problem and it was due to the hard drive failing. Actually, it had multiple BSODS and they were happening on a whole bunch of files. At first I thought it was due to spyware/badware, but it was the HD that was the culprit.

 

Me thinks it's time fer the surface scan on that HDD, Cap'n...

mnem
HEY! You ain't scanning MY surfaces unless you're an Orion "slave" girl with a boatload of Saurian brandy...

 

Yes... I remember hangin' with Jim T, Spock and Bones on that planet... What a time. The Dilithium crystals were cracked you see... And we were stuck on this planet. THEN we found out about those dancing green girls!


<Note the blurred image of the guy in the background hitting the Turkish water pipe!>

Everything changed then! You've never had a hangover until you've been up all night drinking Saurian brandy while trying to get rid of those pesky Orion Crabs! Look up "Tenacious" in Webster's Intergalactic Dictionary and Crab Guide and you'll see a picture of those little critters... They are murder! Why I... Um... Uh....

So... Have you swapped drives yet? PM me if you want a 60GB drive... I'll work you a deal you can't refuse!

 

Wow you are not kidding, ditched IE8 on my cf27, and Google Chrome rocks, thanks for the tip.

Keven

 

Umm YEAH... THAT's what the Saurian Brandy's for... a little up here *glug* to keep the girls looking good... a little down there *GLUG-GLUG* to keep the local fauna at bay... and with Dragon junk... well, that's why you need a boatload for adequate coverage!

mnem
Scaly-Strength Certs with the Chloroform Center - Knocks out Dragon-Breath - GUARANTEED!

 

LOL

Well... KK has a newish 60GB, 5400 rpm hard drive on the way to him. I pulled it out of a CF-29...

Now... If the USPS can get it there.....

 

I really appreciate the help on this, you guys are great! I realize we are all this together, but TB has really gone over and above the standard!

Krash.

 

Krash

It pays to be Klingon the forum



Alex

 

New hard drive arrived today! Up and running great, just getting all the drivers back in tonight.

Thanks again Toughbook!

Krash.

 

Hey TB, if that was one of the HDs you pulled out of a unit you got from me I'd wouldn't put too much trust in it cuz we've been having alot of those refurbished drives fail for no reason. we are currently fighting with the seller over a return claim. We bought lots of these little buggers too

 

I wish I hadn't read that last post!

But, as it is I've got my XP2 Pro, all drivers from Panasonic starting with the chipset first, and Office 2003 installed and running fine. Also, my Task Manager performance graphs are running a dead straight line at the bottom of the scale whenever I check.

Everything seems to be as good, or better than expected. What circumstances or conditions did these units crash under?

 

Nope... It wasn't one of yours... It was a 60GB, 5400rpm drive out of a batch of 1.3GHz units I just got.

I test them all when they come in... Strangely enough... I've only ever had two of yours fail... Though its not like I use every one all day long....