Need Help with Win2k Crashes

I've been running Win2k Pro for about a month and its been very stable until a day ago. I was typing an email in Outlook Express and got a BSOD that said a driver corrupted the memory managment PTE, after which it rebooted.

Windows Hardware 9627 This topic was started by ,



data/avatar/default/avatar19.webp

14 Posts
Location -
Joined 2000-05-22
I've been running Win2k Pro for about a month and its been very stable until a day ago. I was typing an email in Outlook Express and got a BSOD that said "a driver corrupted the memory managment PTE", after which it rebooted. It got into the starting Win2k screen and another BSOD occurred stating "a page error occurred in a non page area -win32k.sys" then rebooted. Now it just reboots over and over, each time with a slightly different BSOD. It will boot up into safe mode ok but everything looks fine. I've tried a new SDram, disabling startup stuff, etc. Once out of 100's of reboots it did finish loading but as soon as I moved the cursor. it got the BSOD and rebooted. At this point I don't know if its hardware or software related. Only recent change was enabling AGP win EPOX's VIAinf patch. I tried disabling AGP but no change. Any help would be greatly appreciated. My system:
 
Antec Tower with 300watt supply
AMD Athalon 750
256mb PC133 ram
EPOX 7KXA Motherboard with onboard VIA audio
Matrox G400MAX Dualhead
Tekram DC390U2W LVD SCSI Controller
Seagate ST118273LW LVD scsi 18.27gb HD
Toshiba 40X scsi CD
TDK VeloCD burner (only device on IDE)
Jaton Xpressnet 10/100 NIC
KDS 19" mon
Win2k build 5.00.2195

Participate on our website and join the conversation

You have already an account on our website? Use the link below to login.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic



data/avatar/default/avatar18.webp

397 Posts
Location -
Joined 1999-08-31
I got similar errors after installing WinDVD. The installation failed due to a corrupt file, but it reset the PC anyway and made a mess. The only way to undo it was to re-install.