J
Jesse
Ok here is the story from the beginning.
For some time I have gotten blue screen errors while
playing quake1. The blue screen would flash and the system
would reboot itself. This did not happen enough for me to
think there was a problem. Recently however, the frequency
of these errors has become ridiculous. Often times I will
be playing for 5 minutes and I'll get a blue screen, now
though, the system does not reboot so I have written down
a few of the errors:
1)
*** STOP: 0x0000001E
(0xC0000005,0xBC4DDAA5,0x00000000,0x0000E424)
KMODE_EXCEPTION_NOT_HANDLED
*** Address BC4DDAA5 base at BC4D0000, Datestamp 3cdb3dab -
kmixer.sys
Begin Physical Memory Dump..
End Physical Memory Dump.. concact sys admin.
2)
*** STOP: 0x000000A(0x000000FF,0x000000FF,0x00000000,
0x80067B39)
IRQ_NOT_LESS_OR_EQUAL
*** Address 80067B39 base at 80062000, Datestamp 3c989e09 -
hall.dll
Begin Physical Memory Dump..
End Physical Memory Dump.. concact sys admin.
other errors of this type I have encountered include
ntoskrnl.exe.
Also, I have been having problems with a hard drive which
has caused me to reboot and chkdsk several times for long
periods (goes really slow on broken drive). I just
finished formatting the drive in maxtor utility and now
when I boot into win, I get a stop error of the type above
right before win splash screen. the error is of the
KMODE_EXCEPTION.. type with file name ntoskrnl.exe.
The message tells me if this is the 1st time I'm seeing
this I should just reboot, so every time I just reboot and
I see it no more untill next reboot.
This happened 2 or 3 times, but has stopped since
installing sp4.
After installing SP4, I ran quake for 5 min, got another
error:
0x00000075 (0x0000000D... ) unexpected_kernel_mode_trap
looking at ms support website I come across
"You may receive the following error message while running
Windows:
STOP 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP)
To determine an approximate cause, examine the parameters
at the top of the STOP screen:
**STOP 0x0000007F (0x000000XX, 0x00000000, 0x00000000,
0x00000000)
UNEXPECTED_KERNEL_MODE_TRAP"
none of the codes given for the XX in the 2nd address
match, nor does my stop code have an F hex value, but I
have to think this is a very similar problem
"The above STOP error means a trap occurred in kernel mode
and the trap is either one the kernel is not allowed to
have or is always fatal. The most common causes of a STOP
0x7F are:
Low-level hardware corruption, such as corrupt memory (RAM)
Mismatched memory modules
A malfunctioning motherboard"
I have run MemTest to over 12,000% coverage and it has
reported no errors. I have run memtest86 for 14 hours,
pass 36 times, no errors.
CPU temp after blue screen reboot is never over 54°,
system temp never over 28°.
Other times while playing quake1, the system will just
reboot itself with no error messages. Also, the game's
excecutable file often closes, forcing me back to windows,
where I see an .exe error, prpgram closed message box.
I can check to see what memory addresses are assigned to
what device in system information if you think that might
help locate the problem.
Thanks.
Athlon 2100+ @ 1733mhz
EPoX 8k5a2+
512mb Samsung pc2700 non ECC
Windows 2000 PRO SP3
For some time I have gotten blue screen errors while
playing quake1. The blue screen would flash and the system
would reboot itself. This did not happen enough for me to
think there was a problem. Recently however, the frequency
of these errors has become ridiculous. Often times I will
be playing for 5 minutes and I'll get a blue screen, now
though, the system does not reboot so I have written down
a few of the errors:
1)
*** STOP: 0x0000001E
(0xC0000005,0xBC4DDAA5,0x00000000,0x0000E424)
KMODE_EXCEPTION_NOT_HANDLED
*** Address BC4DDAA5 base at BC4D0000, Datestamp 3cdb3dab -
kmixer.sys
Begin Physical Memory Dump..
End Physical Memory Dump.. concact sys admin.
2)
*** STOP: 0x000000A(0x000000FF,0x000000FF,0x00000000,
0x80067B39)
IRQ_NOT_LESS_OR_EQUAL
*** Address 80067B39 base at 80062000, Datestamp 3c989e09 -
hall.dll
Begin Physical Memory Dump..
End Physical Memory Dump.. concact sys admin.
other errors of this type I have encountered include
ntoskrnl.exe.
Also, I have been having problems with a hard drive which
has caused me to reboot and chkdsk several times for long
periods (goes really slow on broken drive). I just
finished formatting the drive in maxtor utility and now
when I boot into win, I get a stop error of the type above
right before win splash screen. the error is of the
KMODE_EXCEPTION.. type with file name ntoskrnl.exe.
The message tells me if this is the 1st time I'm seeing
this I should just reboot, so every time I just reboot and
I see it no more untill next reboot.
This happened 2 or 3 times, but has stopped since
installing sp4.
After installing SP4, I ran quake for 5 min, got another
error:
0x00000075 (0x0000000D... ) unexpected_kernel_mode_trap
looking at ms support website I come across
"You may receive the following error message while running
Windows:
STOP 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP)
To determine an approximate cause, examine the parameters
at the top of the STOP screen:
**STOP 0x0000007F (0x000000XX, 0x00000000, 0x00000000,
0x00000000)
UNEXPECTED_KERNEL_MODE_TRAP"
none of the codes given for the XX in the 2nd address
match, nor does my stop code have an F hex value, but I
have to think this is a very similar problem
"The above STOP error means a trap occurred in kernel mode
and the trap is either one the kernel is not allowed to
have or is always fatal. The most common causes of a STOP
0x7F are:
Low-level hardware corruption, such as corrupt memory (RAM)
Mismatched memory modules
A malfunctioning motherboard"
I have run MemTest to over 12,000% coverage and it has
reported no errors. I have run memtest86 for 14 hours,
pass 36 times, no errors.
CPU temp after blue screen reboot is never over 54°,
system temp never over 28°.
Other times while playing quake1, the system will just
reboot itself with no error messages. Also, the game's
excecutable file often closes, forcing me back to windows,
where I see an .exe error, prpgram closed message box.
I can check to see what memory addresses are assigned to
what device in system information if you think that might
help locate the problem.
Thanks.
Athlon 2100+ @ 1733mhz
EPoX 8k5a2+
512mb Samsung pc2700 non ECC
Windows 2000 PRO SP3