Random crashes (64-bit)

[Sinned87]

Heya. I recently bought a new pc. Im running win 7 64bit. with a 64bit java.
Im getting what seems pretty random bluescreens after 10sec-5mins of playing. It happens with both the original glient and gilbertus.
So i guess it's a problem with my java? could anyone help, anyone been having similiar problems?

System info.
Core i7 - 3.06ghz
Ati HD6970 (R6970)

thanks

[Sinned87]

update.

Also happens with 32bit java.

[Granger]

Try updating (or downgrading) your GFX card driver.

In case this fails: try some 3D benchmark (eg. 3D Mark) to see if you can reproduce the crashes.
If you can: backup your files, wipe them from the drive and return the system through warranty.

[Sinned87]

Thanks for the help Granger.

I might have just solved my problems. I updated my realtek HD audio drivers, and i haven't crashed yet.
I hope this was it. Ill post here if crash again.

So if anyone else is having similiar problems, try this. I hope it helps.

[Sinned87]

today i crashed again. Re-installing didn't seem to help. Here's the report and dump.

Dunno what could be wrong for sure.. but somehow i think it might be the audio drivers.
When i get home at the weekend i will take my old soundcard and install it. See if that helps.

But anyway, if someone understands anything from this feel free to comment.

Code: Select all

Problem signature:
  Problem Event Name:	BlueScreen
  OS Version:	6.1.7600.2.0.0.256.1
  Locale ID:	1035

Additional information about the problem:
  BCCode:	124
  BCP1:	0000000000000000
  BCP2:	FFFFFA8007CAB038
  BCP3:	0000000000000000
  BCP4:	0000000000000000
  OS Version:	6_1_7600
  Service Pack:	0_0
  Product:	256_1

Code: Select all

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8008281038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:
fffff880`035776f0 fffff800`030c9a99 : fffffa80`08281010 fffffa80`05528b60 000000
00`0000000e 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03577c10 fffff800`02fab677 : fffffa80`08281010 fffff800`030245f8 fffffa
80`05528b60 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49

fffff880`03577c40 fffff800`02f13c45 : fffff800`03086360 fffffa80`08247168 fffffa
80`08247160 fffffa80`05528b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03577c80 fffff800`02e8c961 : fffff880`01571e00 fffff800`02f13c20 fffffa
80`05528b60 00000101`4a800000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03577cb0 fffff800`031227c6 : 00000000`00000000 fffffa80`05528b60 000000
00`00000080 fffffa80`0550a9e0 : nt!ExpWorkerThread+0x111
fffff880`03577d40 fffff800`02e5dc26 : fffff880`0336a180 fffffa80`05528b60 fffff8
80`033750c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03577d80 00000000`00000000 : fffff880`03578000 fffff880`03572000 fffff8
80`03d5c560 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

Followup: MachineOwner

[loftar]

It seems that you're having hardware problems. If, as you say, your PC is new, there might just be some manufacturing problem.

To begin with, a bluescreen is never a sign of a crash in a user-space program like Java (it's either a system bug, driver bug, or hardware failure), and as you can see in the error report text, the failure doesn't even happen in the Java process' execution context, but in the NT kernel ("PROCESS_NAME: System").

If anything, it could be a driver bug, but seeing that the actual error is a machine check exception -- indicating that the hardware itself is reporting the failure -- that seems unlikely.

[Sinned87]

Heya, thanks for the comment loftar.

What ive done now is:
-updated bios
-updated all possible drivers
-re-installed windows 7

It hasn't crashed on me yet, but i did only play for like 5 minutes.
Well we will know in a couple of days.

[Sinned87]

Hey all.

Didn't help. Crashed 3 times in 10 mins now. Sucks. I don't know what the cause of the crash really is now though. It's just wierd. Since it ONLY happens during H&H.
Not that i played much other games anyway.. crysis 2 demo worked fine and Left 4 Dead 2, works fine aswell.

sigh...