8 replies
by syscokid
Create a hardware profile and boot into it.
Go to the device manager (My Computer, Manage, Device Manager), select View, Show hidden devices, and disable all suspect devices (i.e., non-Microsoft devices) for the current hardware profile. (You disable a device on the General tab of the device's property sheet.)
Reboot using the same hardware profile and try to reproduce the problem. If you can't, start re-enabling drivers and rebooting until the problem reappears. Then delete or update the offending driver.
If the problem persists, disable all unnecessary drivers, update the necessary ones, and try again.
Found that at http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=19972
(Sometimes when I cut and paste URL's it looks ok to me but once the answer is posted, an extraneous space will have crept in. Make sure you delete any extraneous spaces or the page won't load).
by syscokid
Other suggestions:To locate the offending driver:
1. Use %SystemRoot%\System32\Sigverif.exe to check for unsigned drivers.
2. Check for driver updates from your systems vendor.
3. Update any software that contains file system filter drivers.
4. Uninstall non-critical devices and sofware in an attempt to isolate the offending driver.
5. Install an alternate copy of Windows 2000 in a different partition. Add drivers and software until you locate the offending driver
by rturner
by brettcard
Do you have a program called Phone Access Lookup (PAL)installed? If so uninstall it, It can cause this blue screen.
Or do you have Autosave ver 1.04 installed if so you need to upgrade to ver 1.06 or above.
Did you install the update for Media Player 7, and also have Adaptec easy cd creator installed?? If so see MS Knowledge base article Q296584 or Q237468
Do you have Norton CrashGuard 4.0 or 4.01 installed? If so uninstall it, It is not compatible.
Do you have Quicken 2000 installed? If so see MS knowledge base article Q245835
Also what might help is if you give us the full Blue screen error message, For Example...
Stop: 0x000000d1 (0x00000034, 0x00000002, 0x00000000, 0xbfefab7a)
DRIVER_IRQL_NOT_LESS_OR_EQUALaddress bfefab7a base at bfeef000, datestamp
38437eba - ndis.sys beginning dump of physical memory -
by rturner
by rturner
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending