|
Fixing a client's machine which is a Pentium II 333MHz, 160MB RAM running Windows 2000 Professional. It had a virus and finally wouldn't boot with an error after the memory check of HDD not found.
When I got it home and plugged it all into my test bench I found that the virus had already been removed by NAV 2003 and since I had found this out that the HDD was indeed found.
To get in I had to blow away the Administrator password using the magic floppy I mentioned to Michael Barnhart below.
So, the boss had already quoted this bloke 4 hours if the HDD wasn't stuffed. So I thought I would earn a bit of extra pocket money and clean up Windows for him so it didn't fall back in my lap in a few weeks.
I updated NAV and scanned again, nothing. Applied all Windows Updates (bar SP4) and all was well. The CD-ROM was stuffed so I could ionstall SP4 from the CD I have. So I installed off the Windows Update site and went to bed. Got up this morning to find it was waiting for me to click restart, which I dutifully did.
It got passed the moving white line at the bottom of the screen, passed the Windows 2000 Professional bitmap thingy, went black just before you get the login dialog and WHAM.....BSOD.
STOP: 0x0000001E (0xC0000005, 0x80462147, 0x00000000, 0x00006396)
Address 80462147 based at 80400000, DateStamp 3ee6c002 - ntoskrnl.exe
KMODE_EXCEPTION_NOT_HANDLED Google and Microsoft (TechNet, MSDN etc.) haven't been my friend in this case. Besides telling I shouldn't have applied SP4 from the Windows Update site, does anyone have an answer for me on how I can fix this?
I haven't yet tried going into Safe Mode, I didn't have time before having to go to work and will see if this at least works when I get home.
<EDIT>
It works when I boot to Safe Mode with and without Network support. I will be systematically removing hardware device drivers and the devices themselves, such as sound card, modem etc. Upon closer inspection I notice that the Login Dialog box appears for a fraction of a second before the BSOD.
I did notice that it had a Logitech driver loaded even though I didn't have a Logitech mouse. I removed the driver and the problem is still there. Thanks for the mouse advice to whoever it was, as I have forgotten for the moment.
RAM is fine as is the CD-ROM as I have had Knoppix running a treat on the system. I am beginning to get the sh*ts with this machine real bad.
My next step is to download the latest and greatest video drivers (Tseng Labs ET6000), remove the video card in Device Manager, try and boot up again and then install the driver.
</EDIT>
Michael Martin
Australia
"I suspect I will be impressed though, I am easy."
- Paul Watson 21/09/2003
|
|
|
|
|
Y'day only I installed SP4 on my home machine. 
Already few things are not working properly..
Ex: Right click on any folder in the explorer and select "Properties" menu item and I get nothing... 
"Whidbey"..."Orcas"...Roadmap
This signature was created by "Code Project Quoter".
|
|
|
|
|
Are you sure you have admin rights ?
Regardz
Colin J Davies
* WARNING *
This could be addictive
The minion's version of "Catch ![Green Alien | [Alien]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/alien.gif) "
It's a real shame that people as stupid as you can work out how to use a computer. said by Christian Graus in the Soapbox
|
|
|
|
|
|
Straight from Microsoft:
Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED
Resolving the Problem:
If you are not equipped to debug this problem, you should use some basic troubleshooting techniques. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing.
MY OPINION:
If these basic techniques don't work out for you, then you have a bigger problem in your hands. The next step is doing kernel debugging. Do you know how to hook up another system using a serial null modem cable and hooking up a debugger like WinDBG with it? If so, then you would be able to see what driver caused the problem. Then you need to somehow disable that driver or update it with a newer working version of the driver. A boot floppy might come in handy at that point.
|
|
|
|
|
You might want to get a file called (ntoskrnl.exe) from the SP4 CD (just search for it, it's in there somewhere) and put the new one instead of the one that your system currently has. Note that it is a protected file so you may have to copy in DOS mode. (Copying in windows wouldn't have an effect)
|
|
|
|
|
I think that error can come from a big variety of stuff.
1. Bad drivers after windows installs its own.
2. Bad RAM cards (Switch them around)
3. Something in the BIOS like shadow memory (who needs it) or a bad cache.
4. I'd uninstall/unplug that CD
(Also some of those errors are like 'random') maybe it will only happen 6 out of 7 boots
I had problem's about 6 months ago with ntoskrnl. A local business wanted to have there own startup and windows OS messages, so I resource hacked it. Unsure what went wrong but I ended up needing to FDISK and use PM.
Regardz
Colin J Davies
* WARNING *
This could be addictive
The minion's version of "Catch "
It's a real shame that people as stupid as you can work out how to use a computer. said by Christian Graus in the Soapbox
|
|
|
|
|
ColinDavies wrote:
so I resource hacked it
Cool...what kind of things did you change, I know the startup screens can be changed, other than that ??
ColinDavies wrote:
Unsure what went wrong but I ended up needing to FDISK and use PM.
May be they hash the resource size to double check if something is changed or the total hash of the file...
Regards,
Kannan
|
|
|
|
|
Sure the startup screen, the little loading slider graphic, and the shutdown screen (I think). You must stick with 16 colors out of 256 (I think) and there is another dll that has to be modded, to get windows not to refer back to your old ntoskrnl.exe.
The business wanted it to place security warnings for users etc.
Regardz
Colin J Davies
* WARNING *
This could be addictive
The minion's version of "Catch "
It's a real shame that people as stupid as you can work out how to use a computer. said by Christian Graus in the Soapbox
|
|
|
|
|
I've got sometimes this problem because of a RAM chipset which doesn't fit perfectly the motherboard. Moving it and pushing it generally solves the problem.
Silence Means Death
Stand On Your Feet
Inner Fear
Your Worst Enemy
|
|
|
|
|
Is there a Logitech mouse connected? If yes I had that error myself some time ago. Check this:
http://www.jsiinc.com/SUBH/tip3900/rh3979.htm
Cheers
bb |~ bb
|
|
|
|
|
I've seen this before... about 10 out of the 350 machines we have at work did this. Of those 10 we were able to recover 7 of them by removing the USB devices connected to them ( most of these were ergonomic Logitech mice, the others were iPaq docking stations ). After switching back to a PS/2 mouse the machines never could use a USB mouse again, unless we upgraded to WinXP or did a complete reinstall and ran the SP4 from CD. Also... the three that didn't get recovered by removing usb devices had to be formatted and reinstalled.
My code isn't buggy. Those are all fleatures.
|
|
|
|
|
Adam Wimsatt wrote:
Also... the three that didn't get recovered by removing usb devices had to be formatted and reinstalled.
Thabks for the information Adam. This seems to be my fate as well as there are no USB devices plugged in and nothing is making it work.
Michael Martin
Australia
"I suspect I will be impressed though, I am easy."
- Paul Watson 21/09/2003
|
|
|
|
|
I managed to find someone else with the same problem: see Google Groups link[^].
If the system is configured for it, Windows should be generating memory dumps when the problem occurs - typically in C:\WINNT\MiniDump. You could try using WinDbg (part of the Debugging Tools for Windows[^]) to read the dump file.
Start WinDbg, then go to File > Open Crash Dump. Wait for the symbols to download from Microsoft's debugging symbol server (broadband connection very handy!). Use the !analyze -v command. You should ideally do this on a system with the same version of OS and hotfixes that you're trying to read the dump for, or you can point the Image File Path to a location where the correct binaries are stored.
!analyze -v will give a whole bunch of information about the crash - with a bit of luck, it will indicate which driver caused the fault. Note that the address listed is not necessarily the executing line at the point of the fault - it's the address that caused the access violation (code 0xC0000005).
|
|
|
|
|
Uninstall the Logitech driver does NOT help.
You must rename/copy some dlls as shown in my previous link.
bb |~ bb
|
|
|
|
|
I was just wondering if anybody knows if there is a file (text file?) on a windows machine that contains the current process list and if so what is the file?
Regards,
Brian Dela 
http://www.briandela.com[^] IE 6 required.
MFC.NET Application Wizard[^] Mix .NET and MFC easily.
|
|
|
|
|
|
Try the EnumProcesses function.
Software Zen: delete this;
|
|
|
|
|
Yup. I know of that but I was just wondering if there is a file with a list. A friend wanted to get a list of the processes using Java and there is not way of doing it in Java (well... you could use JNI to do it but thats too much overhead) and he asked me if ther was a file on windows that had a list of currently running processes.
Regards,
Brian Dela
http://www.briandela.com[^] IE 6 required.
MFC.NET Application Wizard[^] Mix .NET and MFC easily.
|
|
|
|
|
Does anyone know of what the admin password is for HP's XP home?
Why would anyone put a system together that requires you to enter the admin password to run the recovery but does not give you access to the admin account, Even when you set it up clean! 
Is this just HP's implementation? Did not have time to create a test machine on the side.
"For as long as I can remember, I have had memories. Colin Mochrie."
|
|
|
|
|
Michael A. Barnhart wrote:
Does anyone know of what the admin password is for HP's XP home?
NO, but try this[^], I have used it successfully to reset the Administrator password on a Windows 2000 Professional and Windows XP Professional machine with no problems. Set the password to blank, don't try I change the password to another word using this utility as it doesn't seem to work.
You also might want to try this[^] great tool to write the inage to floppy disk.
Michael Martin
Australia
"I suspect I will be impressed though, I am easy."
- Paul Watson 21/09/2003
|
|
|
|
|
Thanks, I am in now. I still think it was stupid but making progress.
"For as long as I can remember, I have had memories. Colin Mochrie."
|
|
|
|
|
Michael A. Barnhart wrote:
Thanks, I am in now. I still think it was stupid but making progress.
It is stupid, I can't believe that they would lock out the owner of the machine.
Funniest thing is I am currently having to fix a client machine where I haven't been given the Administrator password, it is late and I have to get in. So I had to come back to my original post to you and follow the links I gave you.
Michael Martin
Australia
"I suspect I will be impressed though, I am easy."
- Paul Watson 21/09/2003
|
|
|
|
|
Michael A. Barnhart wrote:
Is this just HP's implementation?
XP Home just leaves the Admin password blank. This would seem just like an OEM to lock the users out of recovering their own systems. I suppose it makes a pretty good tech support revenue a couple years down the road.
Matt Newman
Sonork: 100:11179
"If you're Noah and you're facing the Flood, don't call a lawyer, start building an Ark." - David Cunningham
|
|
|
|
|
Thanks,
It was not blank in this case but Michael's suggestion did clear that up.
Matt Newman wrote:
I suppose it makes a pretty good tech support revenue a couple years down the road.
Or make sure that I will not buy their product(s). Carly F. needs to do a little more on customer attention. 
"For as long as I can remember, I have had memories. Colin Mochrie."
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
XP has tasklist.exe, you could pipe its output to a file, I suppose.