6 replies
by kstrongs Accepted solution
by rkuhn040172 Accepted solution
Time to rebuild that box.
It could be a corrupt system file, a bad driver, lord only knows.
While you're at it, save yourself tons and tons of time and create yourself a slipstreamed XP SP2 disk and never have to worry about installing SP2 again.
by older mycroft Accepted solution
by retro77 Accepted solution
by kstrongs Accepted solution
by w2ktechman Accepted solution
except keyboard/monitor/mouse. Also any flash cards, etc.
Then if it works, you can re-attach everything. If not, can you please forward the error code?
3 items are needed from a blue screen error which may dramatically reduce the troubleshooting time to find the problem.
1. The error should have a text code issued. The BSOD should have a code something like this (all caps, with underscores between words)
INACCESSIBLE_BOOT_DEVICE or KERNAL_MODE_INPAGE_ERROR.
There are dozens of these codes, but this can play a key role in determining the problem.
2. All BSOD errors will also have a set of memory (where the error occured) and a hex code with it, such as
0x0000001A (this is hex code) and then followed by 4 sets of similar #'s (this can be either a more in depth code or memory area where the error occured).
3. After these codes there may or may not be this "in file %filename%". This can point to a particular program or driver that caused the failure, but mostly it will point elsewhere. But, please take note of this if it is available. An example of a full error is:
KERNAL_MODE_EXCEPTION_NOT_HANDLED 0x0000001A (0x12345670 0x87654321 0x00000025 0x22211188) in file ntoskrnl.exe
With all of this information (or at least as much as possible), odds are better that a solution can be found to correct the error.
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending