Bluescreen while loading Win2K

edited May 2004 in Hardware
Ok, I have had my computer on for weeks but I needed to reboot after uninstalling my video drivers... before windows finishes booting it bluescreens with the message:

"*** STOP: 0x0000001E (0xC0000005, 0xEB4B1A59, 0x00000000, 0x00000028) KMODE_EXCEPTION_NOT_HANDLED

If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to be sure you have adequate disk space. If a driver is identified in the Stop 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. If you need to use safe mode to remove or disable components restart your computer press F8 to select advanced startup optinos, and then select safe mode.

Refer to your getting started manual for more info on troubleshooting stop errors."

I tried doing a recovery install and am currently running memtest... I do have enough adequate disk space and I don't have caching or shadowing enabled.

Everything was fine 10 seconds ago until I rebooted :rant:

Any Ideas?

Thanks.

Edit- I probably should add my specs:

Asus A7V8X-X
Barton 2500+ stock
512MB generic PC2700RAM
HIS 9600XT
WD 60GB HDD - Master
WD 200GB HDD - Slave
Burner as Master on other IDE

So far memtest hasnt gotten any errors.

I forgot to say that I have also tried going into safe mode and also tried Last Known Working Config but i hit enter to select them and nothing happens and I have to reset.

Comments

  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited May 2004
    Um, try enabling caching and shadowing for video card. Some cards need this on for drivers to work, and faster boxes tend to like to have system BIOS cached also.

    Second, see if you have managed to get the Video Aperture set too SMALL. Settign ti to half video card RAM will be too small, setting it to at least video card RAM is probably needed for a fast card, and some would say that settign it to TWO TIMES video card RAM is best. I tend to hang with 1.5 times video card RAM for non-gaming boxes.

    Third, run CHKDSK from recovery if you have a retail Win2K Pro CD and not an OEM one. You want a full file system check. It is possible the swap file size is corrupted.

    NOW, try to go into Safe Mode. disable video driver in the control panel, and restart. See what 2000 does, ok?? Tell us, please, good or bad.
  • edited May 2004
    Thanks for the reply John.

    "Um, try enabling caching and shadowing for video card. Some cards need this on for drivers to work, and faster boxes tend to like to have system BIOS cached also.

    Second, see if you have managed to get the Video Aperture set too SMALL. Settign ti to half video card RAM will be too small, setting it to at least video card RAM is probably needed for a fast card, and some would say that settign it to TWO TIMES video card RAM is best. I tend to hang with 1.5 times video card RAM for non-gaming boxes."

    Why would it all of a sudden want different settings? The computer had been working fine since the initial install about a year ago and it had been running for a couple weeks and only when i rebooted did I get this.

    I did run chkdsk, and also tried to get into safe mode but like I said it wouldn't get into safe mode either.

    (Looks like the second post should be in the folding forum ;) )

    I ended up getting it working by reinstalling windows overtop of the old install and now am in the process of backing up stuff and am going to reformat for a clean slate.

    Any ideas why this happened and or what I can do from stopping this from happening again? Memtest ran perfectly with no errors so its no memory.

    Thanks anyway for the help, I hope someone more knowledgeable than myself can explain what happened. :thumbsup:
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited May 2004
    Thanks for the reply John.

    Welcome, will reply inline to your reply now, using italics.

    "Um, try enabling caching and shadowing for video card. Some cards need this on for drivers to work, and faster boxes tend to like to have system BIOS cached also.

    Second, see if you have managed to get the Video Aperture set too SMALL. Settign ti to half video card RAM will be too small, setting it to at least video card RAM is probably needed for a fast card, and some would say that settign it to TWO TIMES video card RAM is best. I tend to hang with 1.5 times video card RAM for non-gaming boxes."

    Why would it all of a sudden want different settings? The computer had been working fine since the initial install about a year ago and it had been running for a couple weeks and only when i rebooted did I get this.


    Some drivers, especially those with DX9 compatibility, and some stock base drivers that 2000 could roll back to, can be best supported this way. Video card RAM or GPU could also have O\H'd, 2000 could have tried to reestablish uninstalled drivers. CMOS battery dying or getting very low on juice could have casued a parameter reset to invalid values for card. Or a combo of such murphyish appearing things. 2000 can also establish a huge swap file when video aperture is crimped, video BIOS is not cached, and shadowing is off. I have seen, in all windows, the swap file get corrupted also, and one such corruption is a size of swap file misstatement (to outrageously huge). Swap file is a hidden system file. Looking at the HD use of normal files might not show accurately what 2000 thought it had at boot under those circumstances.

    I did run chkdsk, and also tried to get into safe mode but like I said it wouldn't get into safe mode either.

    (Looks like the second post should be in the folding forum ;) )

    Yeah, deleted... Hmmm.... Thought I HAD posted it there, it is in my computer's cut-n-paste buffer and will be there shortly... :(

    I ended up getting it working by reinstalling windows overtop of the old install and now am in the process of backing up stuff and am going to reformat for a clean slate.

    Best idea. Other than viruses or what I said above, inline with your questions, no.

    Any ideas why this happened and or what I can do from stopping this from happening again? Memtest ran perfectly with no errors so its no memory.

    So, probably not RAM unless RAM is O\Hing. Not probable if box was not allowed to cool down before Memtest was run after failure. POSSIBLE that video card O\H'd though. They can O\H fast if dusty and crimped for other system resources.

    Thanks anyway for the help, I hope someone more knowledgeable than myself can explain what happened. :thumbsup:

    Probably more than one thing at once, the above are most likely components of problem cause, but any one alone is unlikely to do that.
Sign In or Register to comment.