Airwrck Jan 4, 2005   11:55 PM GMT

All of those blue screens has an associated dmp file. If you are a Windows Professional, you will eventually learn to use the Microsoft Debugging Tools. When you have discovered the source of the crashes, you can look it up using either Google or Microsoft's Knowledge Base for a solution. We train all of our technicians to use this tool because it is such an effective way to diagnose the blue-screen crashes. I am assuming that the machine boots fine in regular mode. You may end up needing to repair it in Safe Mode. Here is the link to the Microsoft debugger and symbol libraries: (pay attention because word wrap may affect this link) http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx You might need more help after downloading the debugger. If so, please send another request.

0 pointsBadges:

Poppaman Jan 5, 2005   8:32 AM GMT

To add to what airwrk and bobkerg (did I get the names right???) have said, I assume (what a nasty word...) that you have searched the MSFT database for the BSOD/STOP error? Is it a KMODE_EXCEPTION_ERROR?; a PROCESS1_INITIALIZATION_FAILED; or.... Each error and/or it's associated STOP code (0x00000000, where the eight "0"'s to the right of the x may be replaced by one or more alpha-numeric characters) has a unique cause, many of which are known issues. If not, or if the cause of your error is obviously not what is listed in the KB article, than the Symbols/Debugger route is the most efficient way to go (unless you have a spare $250.00 and pay Microsoft to do the work for you....) A link to the Microsoft KB for Windows 2000 error messages is here: http://support.microsoft.com/search/default.aspx?qu=windows+2000+error+messages (watch the word wrap...).

0 pointsBadges:

Madwand Jan 5, 2005   9:32 AM GMT

Issue we have seen in our environment .. DLLs install but fail to register ... look up some of the tricks you can do with RegSvr32 ... it may be as simple as manually registering the right DLL file.

0 pointsBadges:

2stroke Jan 5, 2005   10:04 AM GMT

I ass/u/me that when you stated, "I update all drivers that had update available online, but it is not helping.", you meant Windows update? Or did you mean HP's website? Have you updated your BIOS as well? Some of the fixes in SP4 may not be supported by your Hardware or BIOS. Also, there are reported issues with SP4 that could cause problems mounting NTFS volumes and there are updates available to fix this. Might want to check one if these links to see if your system is supported for SP4. http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/default.asp http://www.microsoft.com/windows2000/server/howtobuy/upgrading/compat/search/computers.asp Most likely as previously stated by others, you have a corrupted file after the upgrade. I apologize if I presented more questions than answers. good luck

0 pointsBadges:

Jayaramks Jan 5, 2005   10:08 AM GMT

If you are having problem with only one machine, it will be good to take the bach-up of your important files and install fresh w2k with sp4.This solves most of the blue screen problems. If u r having problems in more machines I suggest to use "Ghost" to reinstall w2k with sp4.

0 pointsBadges:

TedRizzi Jan 7, 2005   2:07 PM GMT

The BSod is always caused by one of two things, hardware problem or a device driver, could be a device driver was installed/replaced in the sp4 patch that is not compatible with your hardware. the bsod usually gives you a driver name. write down the information in the firs 4 or 5 lines and use that to search technet for information. also check HP website to see if there are known issues with that model pc and sp4.

0 pointsBadges:

mparmenter Sep 5, 2014   6:44 PM GMT

Is this still an issue?

55 pointsBadges: