Running:
E8500 currently running at stock speeds (problem still occurs), was at 3.8ghz voltage was only at 1.275.
MSI p35 platinum motheboard
tried both Patriot and Crucial Ballistix.
gefoce 8800 gt
System is about 6 months old. Problems started occuring last week.
I have been trouble shooting this PCs problems for a few days now. Still trying to narrow it down could use some help here.
This is a little unexpected so hopefully one of you will recognize these symptoms.
My computer has had various blue screens in the last few days. Mostly its MACHINE_CHECK_EXCEPTION or CRITICAL_STRUCTURE_CORRUPTION. It passes memtest with flying colors...or so I thought! I decided to run orthos over night and I set it to reboot upon bsod. I also inserted the memtest cd so as soon as it rebooted it would start running memtest. Well as soon as it crashed and memtest launched it spammed hundreds of errors. Powered off, turned back on, passed memtest with flying colors.
Any ideas here? Thanks. My next step will be to try a different CPU.
Incase you happen to be able to debug MCE's the parameters for the MACHINE_CHECK_EXCEPTION was:
Arg1: 0000000000000005
Arg2: fffffadfc8c71240
Arg3: 00000000b2000030
Arg4: 0000000008000e0f
and
Arg1: 0000000000000001
Arg2: fffffadf90c71240
Arg3: 00000000b2000000
Arg4: 0000000006000e0f
Update:
Sometimes file checks such as MD5 will come back incorrect but when I reboot they are fine. What could cause that?
I recently recieved another blue screen:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffade9c8b1018, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffffadf8eeac11e, address which referenced memory
referencing inspect.sys which is comodo. I have had comodo for a while now though.
E8500 currently running at stock speeds (problem still occurs), was at 3.8ghz voltage was only at 1.275.
MSI p35 platinum motheboard
tried both Patriot and Crucial Ballistix.
gefoce 8800 gt
System is about 6 months old. Problems started occuring last week.
I have been trouble shooting this PCs problems for a few days now. Still trying to narrow it down could use some help here.
This is a little unexpected so hopefully one of you will recognize these symptoms.
My computer has had various blue screens in the last few days. Mostly its MACHINE_CHECK_EXCEPTION or CRITICAL_STRUCTURE_CORRUPTION. It passes memtest with flying colors...or so I thought! I decided to run orthos over night and I set it to reboot upon bsod. I also inserted the memtest cd so as soon as it rebooted it would start running memtest. Well as soon as it crashed and memtest launched it spammed hundreds of errors. Powered off, turned back on, passed memtest with flying colors.
Any ideas here? Thanks. My next step will be to try a different CPU.
Incase you happen to be able to debug MCE's the parameters for the MACHINE_CHECK_EXCEPTION was:
Arg1: 0000000000000005
Arg2: fffffadfc8c71240
Arg3: 00000000b2000030
Arg4: 0000000008000e0f
and
Arg1: 0000000000000001
Arg2: fffffadf90c71240
Arg3: 00000000b2000000
Arg4: 0000000006000e0f
Update:
Sometimes file checks such as MD5 will come back incorrect but when I reboot they are fine. What could cause that?
I recently recieved another blue screen:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffade9c8b1018, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffffadf8eeac11e, address which referenced memory
referencing inspect.sys which is comodo. I have had comodo for a while now though.
Last edited: