• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

are these codes pointing me to cpu or mobo???

Duvie

Elite Member
PRIME95 caused an invalid page fault in
module PRIME95.EXE at 015f:005c8358
Registers:
EAX=000000bf CS=015f EIP=005c8358 EFLGS=00010282
EBX=00000000 SS=0167 ESP=019afc58 EBP=01c7a540
ECX=00000000 DS=0167 ESI=0398cb40 FS=0ecf
EDX=00000033 ES=0167 EDI=019c1000 GS=0000
Bytes at CS:EIP:
01 00 66 0f 28 ae 90 10 01 00 66 0f 28 b6 a0 10
Stack dump:
00466951 019afd3e 00000001 019afd5c 0041708b
00000050 00000000 ffffffdf 00000003 00440400
00000000 00000190 83fe36d9 00000000 0f030621
012fffff


This is an error I get when I oc my board past 125fsb no matter the voltage....I have a p4 1.8 that I used to be able to oc to 2.4ghz at 1.65v and 2.52ghz at 1.775v...now I can't do 2.4ghz with even 1.85v using mod trick. Temps are fine...in mid to upper 40's during any of the errors...vcore and 12v look fine no spiking I can see....


I am hoping somebody with some higher end tech experience recognize the addresses as being cpu or mobo....

feel free to pm me with any questions as well...


 
Semiconductors slow down with time. This aging factor is a square to the voltage applied (even higher if the increased temperature from the higher voltage isn't compensated) and merely directly proportional to temperature. 1.775V is pretty high, and 1.85V is very high. You may be running into aging mechanisms far earlier than expected due to the elevated voltage.

As far as the error, it's hard to know. It's a memory error (invalid page fault) but this could be caused by the memory, the CPU (a bad TLB entry caused by a speed path) or even in the chipset itself (garbling a memory address due to a speed path). It's hard to know without isolating the problem further.

As the local advocate for ECC memory, I feel compelled to add that you'd know if it was a memory error if you had ECC. 🙂
 
Back
Top