Our forums are currently in maintenance mode and the ability to post is disabled. We will be back up and running as soon as possible. Thanks for your patience!

General discussion


Looping boot

By darrenm ·
Yesterday an NT4 computer was shut down improperly and only would boot to the blue screen. NO REPAIR DISK!!!! so I ran the repair from the NT disk and followed the recommended repairs. Now it will boot all the way until you see the login screen and then and soon as you see the ctrl-alt-del box it just breifly flashes a KMODE_EXCEPTION_NOT_HANDLED bluescreen and reboots, continuosly.

I figure this is a driver thats loading and causing the error and the continuos reboot but I dont know which one. I tried booting in VGA mode and it does the same exact thing.

Is there a utility out there that offers a interactive bootup that could help me?

Thanks in advance

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by SFHSGrad00 In reply to Looping boot

try rebooting the system, and press F8 to get the start menu to display. You can either boot into safe mode, and try to revert back to the last good safe state the systme was in, before the invalid shut down, or try the option to boot from last good configuration, without going into windows.

Collapse -

by darrenm In reply to Looping boot

I don't think that works with NT However there is a VGA mode that only loads minimal driver kind of like the safe mode and that still didn't work.

Collapse -

by w2ktechman In reply to Looping boot

You can limit the search for the problem by looking at 3 parts of the blue screen. First part KMODE_EXCEPTION etc. Second part to look at it the actual dump (example: 0xC0000005 (0x00000etc.) And usually it is followed by a file name (example: ntoskrnl)
The file name may list any number of files, you can usually trace this to a device or program on the system.The first 2 parts can be used together for a MS Query.
Once you have an idea of what failed, then it seems to get easier to fix.

Collapse -

by darrenm In reply to Looping boot

The last two stop addresses are supposed to match to a driver listed at the bottom . Right? None match.

Is there a file somewhere like Autoexec.bat or Config.sys in NT that lists booting drivers? I looked in those two but they contain nothing, I assume because its NT.

Related Discussions

Related Forums