|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
#1 |
|
Member (8 bit)
Join Date: Sep 2002
Location: SW Iowa (moooo)
Posts: 214
|
boot problem
My local volunteer fire department is having a problem with their computer and asked me if I could help them. I went to look at it and it's win 98 machine, generic case. I didn't open it up yet. Upon starting it says the following:
"While initializing device VKD: Windows protection error. Y An internal stack overflow has casued this session to be halted. Change the STACKS setting in your config.sys file, and then try again." That's it. I can't do anything, other than hit the reset button and get the same screen Any ideas, I'd like to help them out if I can....
__________________
| AMD Athlon 64 3000+ | Abit KV8 Pro Mobo | ATI Radeon 9800 Pro 128mb | LiteOn 16X DVD Rom | 24x10x40x LiteOn CD-RW | Zerus Cooling Fan (rear expansion slot mount) | 2GB G Skill DDR PC3200 (2 X 1MB) | Thermaltake Purepwer 420W Power Supply | WD 80GB 7200 RPM | WD 40GB 7200 RPM | Window XP Home | |
|
|
|
|
|
#2 |
|
Shiro Usagi
Premium Member
Join Date: Sep 1999
Location: Kaneohe, Hawaii
Posts: 34,002
|
Try another keyboard and see if the error message goes away.
Cricket
|
|
|
|
|
|
#3 |
|
Member (9 bit)
|
Yep, it's most likely the keyboard... try unplugging the one you have and plugging it back in first (power OFF)... if not, try another as Cricket had suggested...
you can tell the guys at the station you learned that from: http://support.microsoft.com/default...b;en-us;263318 good luck
|
|
|
|
|
|
#4 |
|
Member (12 bit)
Join Date: Nov 2001
Location: Woodland Hills, CA (suburb of Los Angeles)
Posts: 4,014
|
If unplugging/replugging or changing keyboards doesn't help, I seen instances where it's just luck that a hard drive developing bad sectors (or other sources of data corruption) happens to corrupt that file. You can try a "thorough" run of ScanDisk, though to be able to run it you may have to boot from a bootdisk or bootable cd (since the normal boot is going to give you the keyboard error). You can also try looking inside the case to see what hard drive is installed, downloading the diagnostics from the manufacurer's website (the downloads creat a bootable disk that the diagnostics run from), and testing the drive.
Hopefully it's just the keyboard! . . . Gary [ might want to run a thorough antivirus scan too - Norton 2003 will run from a bootable cd. And if you keep seeing the stack errors, this article has some settings for config.sys that can help http://support.microsoft.com/default...b;en-us;145799 ] Last edited by GaryRouth; 07-29-2003 at 12:19 AM. |
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|