• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

App Crash Help?

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

RDWest2005

Member
Joined
Sep 1, 2005
Location
South Carolina
Hi guys
I've posted in the 3dmark team section - but no replies or anything yet

maybe someone can help me in here

I guess i'm posting in the right place

This is where i'm at...
You read my SIG to see my setup

mb don't read mem voltage and timings right by crucial
so i manually set 2.1v at 3-3-3-12 - crucial specs
and i have moved the auto vcore 1.37v up to 1.38v <- i think thats right

i oc mode to manual
then i use cpu/mem - manual mode as fsb goes up mem stays within -5% to +5%

i set nvidia display panel to 3Dmark05 profile

everything runs stable up to 240x4 = fsb960
after i go past 960 fsb the 3dmark05 crashes after all the fast tests
when the 1st test (the lagger i call it) begins, 3dmark05 will crash

it crashed just like a windows app

where it gives you the option to send report to microsoft

but my computer and everything is still running fine

any ideas?

******* EDIT
I just found this in event viewer
---------
Faulting application 3dmark05.exe, version 1.2.0.0, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x00010e18.
---------

tx
~RD
 
Last edited:
hummmm
mem86 and prime i have ran for hours - no errors

its completely stable up to 960fsb
if i go past that, i think its the cpu test it crashing on since i've did a little more reading

the guys with scores like mine and above are not doing cpu test

ok here is where it crashes...

i think there is like 4 test that run smooth and fast

then you get the last 2 that skip/lag or whatever
1-3 fps and oc i get up to 6 - 8 fps

but this is where it crashes
and 3dmark05 crashes just like an app with the error where you can report it to microsoft if you want

bare with me here - i'm just now getting into all this oc-ing etc

tx
~RD
 
If it only crashes when you overclock past a certain point, it's an unstable overclock. You can back down to where it's stable or try to stabalize it with better cooling and/or more voltage (within reason, of course).
 
From all i have read etc - unstable overclocks lock the computer up etc
or it won't post or whatever

and i've been playing(I'm noob now)with all the settings etc
i've had it not post and freeze completely at certain settings

but when 3dmark05 crashes, it same as any win app crashing
here is screen shot...
3dmark05-crash.jpg


it will do this or just completely close out during test
when it just closes out there is no event error in event viewer

but there is 2 different errors if it gives me the crash as in the screen shot

this error...
Faulting application 3dmark05.exe, version 1.2.0.0, faulting module unknown, version 0.0.0.0, fault address 0xffffffff.


or this error...
Faulting application 3dmark05.exe, version 1.2.0.0, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x00010c18.


all else is still running fine when it crashes

any more ideas?

~RD
 
RDWest2005 said:
From all i have read etc - unstable overclocks lock the computer up etc
or it won't post or whatever

Wrong. I gotten those type of crashes before. Usually it's because you have to increase the Vcore or your CPU is at a brick wall. A T-bred 2000+ I used to have did this to me when at 2.1 ghz and wasn't stable beyond 2.0 ghz.
 
tx for the replies - i aint really bumped up no voltages hardly - 1 step on vcore

i did make a stable run at 980fsb/3920mhz today - LDT 2x - no oc on cards
3dmark05 = 10,832

i don't exactly know how to decrease/and or/increase ram timings at high fsb and stuff just yet - lots of reading :(

tx
~RD
 
RJARRRPCGP said:
Wrong. I gotten those type of crashes before. Usually it's because you have to increase the Vcore or your CPU is at a brick wall. A T-bred 2000+ I used to have did this to me when at 2.1 ghz and wasn't stable beyond 2.0 ghz.

yep, me too.
 
Wrong. I gotten those type of crashes before. Usually it's because you have to increase the Vcore or your CPU is at a brick wall.

Me three...
Also could be a cooling issue.
 
Back