Unsolved
This post is more than 5 years old
11 Posts
0
7173
December 17th, 2005 10:00
Blue Screen Stop Message on reboot.
I have a Dimension 8200 with Windows XP Professional and I am having a problem with start up. When booting up it goes into a disk check procedure which then brings up the following blue screen stop message:
A problem has been detected and windows has been shut down to prevent damage to your computer.
If this is the first time you've seen this stop error creen, restart your computer. If this screen appears again, follow these steps:
Check to be sure you have adequate disc space. If a driver is identified in the stop message disable the driver or check with the manufacturer for driver updates. Try changing video adaptors.
Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press 8 to select advanced startup options, and then select safe mode.
Technical information:
***STOP: 0X0000007E (0X0000005, 0XF99D1570, 0XF9FC95A8, 0XF9FC92A4)
*** NIDS.sys - ADDRESS F99D1570 BASE AT F99B3000, DATE STAMP 41107ec3
I have udated my BIOS from A03 to A09 but does not solve the problem.
A problem has been detected and windows has been shut down to prevent damage to your computer.
If this is the first time you've seen this stop error creen, restart your computer. If this screen appears again, follow these steps:
Check to be sure you have adequate disc space. If a driver is identified in the stop message disable the driver or check with the manufacturer for driver updates. Try changing video adaptors.
Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press 8 to select advanced startup options, and then select safe mode.
Technical information:
***STOP: 0X0000007E (0X0000005, 0XF99D1570, 0XF9FC95A8, 0XF9FC92A4)
*** NIDS.sys - ADDRESS F99D1570 BASE AT F99B3000, DATE STAMP 41107ec3
I have udated my BIOS from A03 to A09 but does not solve the problem.
I have tried opening in safe mode but after pressing F8 to get to the black options screen, the 'white highlight' is frozen on the 'safe mode' option and when I press enter nothing happens - also if I try to move to another option with the arrow keys - nothing happens!
A little history here might help. I have had real problems with slow running and this was resolved by increasing the RAM from 2x128=256mb to 2x128 + 2x256 = 768mb. At the same time I also installed a secondary 160Gb hard disk (primary HD 80Gb). Both the installation of the RAM and HD went without a hitch and the computer is now running well - but I am still left with this blue screen stop message on start up (To run windows I have been bypassing the stop message each time I need to reboot)
I do not know how long the problem has been there because I leave the computer switched on and only reboot when necessary for windows upgrades etc. I have installed a lot of software over the last 6 months so it is impossible for me to attribute the problem to any particular installation. I was hoping that the increase in RAM would resolve the problem and mabe there could still be a problem with the original 2x128mb being corrupted? Should I have replaced these with the 2x256 rather than adding them?
A little history here might help. I have had real problems with slow running and this was resolved by increasing the RAM from 2x128=256mb to 2x128 + 2x256 = 768mb. At the same time I also installed a secondary 160Gb hard disk (primary HD 80Gb). Both the installation of the RAM and HD went without a hitch and the computer is now running well - but I am still left with this blue screen stop message on start up (To run windows I have been bypassing the stop message each time I need to reboot)
I do not know how long the problem has been there because I leave the computer switched on and only reboot when necessary for windows upgrades etc. I have installed a lot of software over the last 6 months so it is impossible for me to attribute the problem to any particular installation. I was hoping that the increase in RAM would resolve the problem and mabe there could still be a problem with the original 2x128mb being corrupted? Should I have replaced these with the 2x256 rather than adding them?
Can anyone help please.
Richard
No Events found!
The Virus
1 Message
0
December 17th, 2005 11:00
DarkStrike
31 Posts
0
December 17th, 2005 17:00
rgmt22
11 Posts
0
December 20th, 2005 10:00
Hi Virus/ DarkStrike,
Thanks for your comments. I have Norton Internet Security installed (incl antivirus) and 3 lots of antispyware (Microsoft, Ad - Adware and Spybot) so I don't think there is a problem there - I know you can never be sure!
I do not suffer from crashes and once windows is loaded the computer seems to run ok and much faster since I increased the RAM. The blue screen only appears on startup because Windows is detecting a problem and initiates a disk check which runs to about 60% and then the blue screen comes up. I bypass this by aborting the disk check. My concern is - am I causing potential further more catastrophic problems by doing this?
I agree that a re-install of windows should solve the problem but I see that as a last resort because of all the programmes I would need to reinstall. Can I install windows on the secondary HD and then copy files accross from the primary HD? I have Acronis True Image which can 'clone' the entire contents of my HD but I guess if I do that then I will also clone the problem?
Can I also have your comments please on the following suggestion which came from BIOS forum:
From your description of the blue screen stop error, I'm guessing that you tried to run CHKDSK /F from Start\Run or the Dos Box and replied yes when asked if you want to run CHKDSK on the next restart. There seems to be some kind of incompatibility between CHKDSK, the Dell bios, certain hard drives, and 1.5Ghz or faster processors that causes CHKDSK to fail when run at startup or in safe mode. I suspect that chkdsk is issuing commands to the disk bios, or the disk bios is issuing commands to the controller so quickly that a buffer overrun occurs in the bios memory block or the disk controller which, when detected, causes an unrecoverable failure. You can avoid the blue screen by entering setup to switch the processor from normal to compatible mode before CKHDSK runs. It will take an outrageous time to run at compatible speed but it will run all the way through and fix any errors on your disk. After displaying ordinary status messages, CHKDSK will again reboot your machine, giving you the chance to enter setup again to set the processor speed back to normal. The system should boot to windows normally after exiting setup. At least that's how it worked on my 8200 when I had this problem.
I scheduled chkdsk to run at startup to fix file system corruption caused by power failures and, when chkdsk started, I got pretty much the same blue screen you did. This happened every time chkdsk ran after boot. I discovered that putting the processor in compatibility mode allowed chkdsk to run to completion by accident; I was trying to slow the scrolling of informational messages during bootup at the time.
My P4 1.7GHZ system runs chkdsk to completion in compatibility mode in about 45 minutes on an 80GB drive with about 23GB in use. It takes 5 to 10 minutes just to get past the black Windows XP system ID screen so it can begin checking the disk.
If chkdsk is failing on your system because of a hard drive, bios, processor speed mismatch then running it in compatibility mode will just allow it to finish without incident after correcting any volume bitmap, file allocation, or indexing errors on your hard drive. This should also reset your "run chkdsk at startup flag." I have XP Home Edition so I don't know exactly how XP Professional works but it may be that your OS scheduled a disk check at startup because, in the normal course of operation, it detected a significant problem with your file system. In this case, not allowing chkdsk to finish may be risky. On the other hand, if a non-processor-speed-related problem is causing your blue screen message, running chkdsk in compatibility mode will just bring up the blue screen again (albeit a bit more slowly.) This may mean that the chkdsk program itself is corrupt and you may then need to lookup how to use Windows Repair Console.