Help ... win2K blue screen at start up

chendol

Member
Oct 21, 2000
44
0
0
I have encountered the dreaded blue scrn at start up with this error message

STOP: 0x0000001E(0xC0000005, 0x00000000, 0x00000000, 0x00000000)
KMODE_EXCEPTION_NOT_HANDLED

I have tried to disable some drivers using Recovery Console n still no luck. Any Ideas?? Or i have to admit defeat n reinstall??:frown:

 

Adrian Tung

Golden Member
Oct 10, 1999
1,370
1
0
Bad memory perhaps?

I just had a bad memory incident last week involving a 128MB stick of SDRAM... it gave me KMODE_EXCEPTION_NOT_HANDLED and DRIVER_IRQL_NOT_LESS_OR_EQUAL errors everywhere; sometimes during boot and sometimes in the middle of anything I do.


:)atwl
 

Panther505

Senior member
Oct 5, 2000
560
0
0
First try VGA mode and Safe mode.... IF you still get the problem look to any recent hardware that you have installled and then look to any recent apps that you have.. I am in favor of a hardware issue bercause you are not getting into the GUI... List your system stats and any recent HW that you have added and we can go from there..
 

MulLa

Golden Member
Jun 20, 2000
1,755
0
0
Like Adrian said I had similar errors before when 2 different brands of memory refuse to co-operate and be nice to each other. Same error messages and the problem is solved by removing one stick of mem.
 

Shadow07

Golden Member
Oct 3, 2000
1,200
0
0
Did you install DirectX 8 or even the new Det 3 drivers?

BTW, visit our site and get a chance to win a Belkin 2x8 KVM switch valued at $1000! Click here to visit.
 

Psychoholic

Elite Member
Oct 11, 1999
2,704
0
76
This link might help you wean some information as to where to find the problem causing the blue screen.

Also bad memory, as it has been mentioned before, can also cause this error.
 

chendol

Member
Oct 21, 2000
44
0
0
Thanx for the tips .. i enventually install win2k on another partition n manage to get into the original win2k ntfs partition to back up some data files before i reformat the whole thing n reintsall win2k. I think it happen after i cancelled an installation of a Hex edit program. When i started up win2k the next morning it happened. Havent had any H/W probs till this so im assuming it was the s/w installation prob.

Yeah i have adaptec Cd creator but have applied the necessary patch for it n never had any probs using it all the time. As for Memory would it affect my win 98 too cos i had no prob booting into win98. All seems back to normal now. Thanx again.
 

Shadow07

Golden Member
Oct 3, 2000
1,200
0
0
"WTF?"

Is it really necessary for profanity?

"Was that a helping hand or a shameless plug? "

You know if you don't want the $1000 KVM switch, then I guess someone else will. But, I have been here for some time now and I have built a reputation of providing good support and advice.

Can't we just get along?

 

mastarecoil

Senior member
Dec 31, 2000
615
0
0
What is this about easy cd creator and patches for windows 2000. I am getting lots of bsod errors.

Thanks
Garrett.
 

Ben

Golden Member
Oct 9, 1999
1,585
0
76


<< What is this about easy cd creator and patches for windows 2000. I am getting lots of bsod errors. >>


I'm referring to this link. I've had this problem with my system.

The Easy CD patches will solve the problem but if you try to install something like WinDVD later, you will hose your system. This is actually a problem with Easy CD, not WinDVD (or other programs that may cause this situation). You can even get this problem if you try to update WinDVD (for example) after you have installed Easy CD Creator.

Intervideo says that to install WinDVD, you must install it before installing Easy CD Creator.

This is a particularly nasty problem since the system cannot be booted in safe mode. Restoring the system files, or even reinstalling W2K will NOT fix the problem.

The only fix is to do a format/reinstallation or to disable the cdr4vsd driver using the utility on the W2K CD.
 

Cweeks

Member
Sep 23, 2000
28
0
0
This maybe a little latebut....
Direct from the Resource Kit. Hope it helps a little.

Error Message:
KMODE_EXCEPTION_NOT_HANDLED

Explanation:
This Stop message indicates that a kernel-mode process tried to execute an incorrect or unknown processor instruction. This error handler is a default error handler that catches errors not associated with other specific error handlers.

User Action:
First, make sure that any new hardware installed is listed on the Microsoft Windows 2000 Hardware Compatibility List (HCL) on http://microsoft.com. In addition, a buggy device driver or system service might be responsible for this error. Hardware issues, such as memory conflicts and IRQ conflicts, can also generate this error. If a driver is listed by name within the Stop message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you need to start the computer by using the Recovery Console to access the file. If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, the service can be removed by starting the system using the Recovery Console and deleting the offending system service file. Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing this Stop message. Disabling memory caching of the BIOS might also resolve the error. Also run hardware diagnostics, especially the memory scanner, supplied by the system manufacturer. For details on these procedures, see the owner?s manual for your computer. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at http://support.microsoft.com/support.


 

OverclockMe

Senior member
Nov 15, 2000
349
0
0
When I got my bluescreen and couldnt boot into windows no matter what, I just got into the recovery console and typed chkdsk/f
it fixed all my errors and voila my comp worked again, hope that will work for you