New PC, Keeps Crashing, Can Anybody Help Please?

Status
Not open for further replies.
C

-Clum-

Hi, I've just built a new pc but I have a problem with it's stability. While just running Windows it seems to be ok, but when I play games (Mainly happens on F.E.A.R & Doom 3 [Half Life 2 seems stable for some reason]) my system will either freeze and I have to press the reset button, or it will just restart the system itself (No blue screen or anything). This can happen either as soon as I start the game (On the menu) or after 5mins or 50mins of play. I don't think it's an overheating issue as my CPU temp is 40-50 degrees, my system is about 40 degrees and my GPU is about 50 degrees. No component has been overclocked and I'm using the stock drivers that came on the CD's with the parts. My system is listed below:

AMD 64bit X2 4200+ (AM2)
1GB (2x512) Crucial Ballistix Dual Channel DDR800 PC2-6400 (4-4-4-12)
Asus M2N-E
Seagate Barracuda 7200 250GB SATA-II 16MB
HIS ATI Radeon X1900 XT ICEQ 3 SILENT Heatpipe 512MB GDDR3
Pioneer DVR-111BK 16x16 DVD±RW Dual Layer ReWriter
Antec Sonata II Piano Black Quiet Case - 450W Smart Power PSU
(Running Windows XP Pro SP2)

Please if anybody can think of anything that might be causing this problem I would really like to know as I've just spent a lot of money on it and for it not to be stable is really really annoying and I don't know what to do, I don't have any spare components at the moment to try and switch parts to see if I can determine if anything is faultly, but I doubt there is anyway.

Thanks in advance if anybody replies,
Callum.
 
Thats one sweet system you've got :)

I don't think it's an overheating issue as my CPU temp is 40-50 degrees, my system is about 40 degrees and my GPU is about 50 degrees.
are those temps while the pc is in idle or while doing something intensive?

Go to C:\windows\minidump and see if you got any new ones, and put them up here.

I'm using the stock drivers that came on the CD's with the parts.
Tried checking for updated ones from the manufacturer's websites and windows update?
 
Hi, thanks for the reply, the temps while idle are:

CPU:40-45
System:35-40
GPU:48-50

and while under intense gaming:

CPU:50-55
System:40-45
GPU:55-65

Erm, I checked the minidump folder and there are some, I've just added the most recent as an attachment, is that right? (I'm not sure what they're for hehe).

I'll try getting the updates now also and see if that helps, thanks.
 

Attachments

  • Mini082606-05.dmp
    92 KB · Views: 5
Analysis:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem....

Points to a file ati3duag.dll which is part of your ATI video card drivers.

Add a few more other minidumps that are slightly older (mini082606-xx), maybe 01-04 so i can compare them..
 
Unfortunately I had deleted the previous dumps, but I've attached the 2 latest ones which have happened in the same manner (although this time I got a blue screen since I enabled it in the advanced startup screen, so maybe the dumps will contain different information?). If these don't match up with the previous fault, I'm sure I could run a few games and get some more crashes :p

Anyway, I had wondered if it was the graphics card since it usually only happens while playing games, maybe even trying to use too much power? (I would guess this card is quite power hungry) Just hope it isn't that reason or I'd have to end up spending another £60 or £70 on a new PSU which I really couldn't afford =\

Thanks for taking a look at the files for me.
 
mini082706-01
Code:
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

LAST_CONTROL_TRANSFER:  from 80513c6d to 80521b02

STACK_TEXT:  
f6f288a0 80513c6d c0600620 c00c4558 00000000 nt!MiRemoveZeroPage+0x14
f6f288b8 8051f6c1 188ab000 c00c4558 863832c0 nt!MiResolveDemandZeroFault+0xc5
f6f2891c 80543568 00000001 188ab000 00000001 nt!MmAccessFault+0xbf1
f6f2891c 005591e4 00000001 188ab000 00000001 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012e23c 00000000 00000000 00000000 00000000 0x5591e4


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
!chkimg -lo 50 -d !nt
    80521b02 - nt!MiRemoveZeroPage+14

	[ 8b:cb ]
1 error : !nt (80521b02)

MODULE_NAME:  memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption

mini082706-02
Code:
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_d

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

LAST_CONTROL_TRANSFER:  from 80513c6d to 80521b02

Could be ram...
Try doing a memtest with one stick at a time. How did your driver updates go?
Attached is the report if anyone wish to review it..
 
Status
Not open for further replies.
Back