Windows protection error....

Sixide

Junior Member
Aug 2, 2001
3
0
0
I recently installed a new 1.4GHz T-Bird, the 133MHz FSB kind. I left it unlocked, at least until the 30-day OEM warranty is up.

When I attempt to boot windows, it stops with the error:
"Windows protection error. You need to restart your computer."
just prior to loading the GUI.

Safe mode or the command prompt works fine. I don't experience this problem when running at 1050MHz, only at 1400, but it is still unstable.
2 days before getting the CPU, I installed 512(2x256)MB of Mosel Vitelic SDRAM. I tried installing the v4.32 4-in-1s, but they didn't help.
Can anyone tell me what may be wrong here?

Abit KT7A, 4.32 4-in-1s
Thunderbird 1.4GHz
2x256MB Mosel Vitelic SDRAM
GeForce 2 GTS 64MB, 12.41 Detonators
SBLive Value
Linksys 10/100 NIC
Win98

Thanks

 

Sixide

Junior Member
Aug 2, 2001
3
0
0
Thanks, that helped.
setver.exe in config.sys seemed to be causing the problem.
Runs fine now.
 

corkyg

Elite Member | Peripherals
Super Moderator
Mar 4, 2000
27,370
239
106
As a general rule, unless you are running some sort of DOS legacy programs, Windows (any version from 95 on) works much better if you get rid of both AUTOEXEC.BAT and CONFIG.SYS. Rename them to *.DOS and see how your system runs.
 

Sixide

Junior Member
Aug 2, 2001
3
0
0
Ok, seeing as REMming the setenv.exe out only lasted me 2 boots, i decided to try my old 2x128MB Crucial PC133 CAS2, and it works as perfectly as it ever did. Is there any way to fix it so my new memory would work?
Like a windows reinstall? Or am I SOL, and have to return it...

Thanks.

Gr..., scratch that.
It now crashes again, with the crucial.
Vitelic, 7.5*133 (old CPU) works
Vitelic, 10.5*100 (new CPU) works
Vitelic, 10.5*133 (new CPU) doesn't
Crucial, 7.5*133 (old CPU) works
Crucial, 10.5*100 (new CPU) doesn't
Crucial, 10.5*133 (new CPU) doesn't
I am beginning to see a pattern here...
Is it possible to "prove" i have a faulty CPU, or not?