Win2k BSOD when scanning HD, KMODE_EXCEPTION_NOT_HANDLED...

AmdEmAll

Diamond Member
Aug 27, 2000
6,699
9
81
Windows 2000 is way to sensitive to improper shut downs. It was in the middle of loading windows 2000 and I restarted it to change some overclock settings. Of course when I go to load windows again a screen comes up saying that it needs to scan the harddrives for errors. It goes through step 1 of scanning and then it gets to step 2 (scanning Indexes) and a BSOD pops up. At the top of it it says STOP... and a bunch of number to the right of it. Below that it says KMODE_EXCEPTION_NOT_HANDLED and it says tbcspud.sys. Below that it gives me a bunch of idea of what I should do. Reinstall drivers or something I dont remember what it said. Now everytime I restart it trys to scan the harddrive. If I cancel the scan it will load windows fine and everything seems to work fine. WTF is up with that? And Norton disk doctor wont scan when I have Automaticaly fix errors checked, it says the hd is in use. But if I uncheck it, it will scan but it says it cant fix the index. Hmm what should I do? It is more of a pain then anything, delaying my bootup.

Posted this is OS's but GH is more active so I posted it here to.
 

Killbat

Diamond Member
Jan 9, 2000
6,641
1
0
If it helps any, that's a Turtle Beach driver file. Reinstall your soundcard drivers and try again. Make sure you clear your temporary file folders.

Win2k wouldn't be scanning drives on startup if there was nothing wrong!
 

AmdEmAll

Diamond Member
Aug 27, 2000
6,699
9
81
Thanks, I didnt know what file that was for. I'm downloading the drivers off of TB's site. Damn 20Mb drivers :Q
 

AmdEmAll

Diamond Member
Aug 27, 2000
6,699
9
81
All fixxed, reinstalled the drivers then windows fixxed everything. Thanks KillBat :)
 

Pabster

Lifer
Apr 15, 2001
16,986
1
0
I assume you are using FAT or FAT32. Bad idea. Reformat and use NTFS. It handles "improper shutdown" situations much better.
 

AmdEmAll

Diamond Member
Aug 27, 2000
6,699
9
81
Nope. My C drive is NTFS and my D drive is Fat32 and the problem was on C drive, go figure.