BSOD with win 7 64 bit when playing games

Probably heat related because of time frames you mention and when they occur. You're overclocking too much, if you are at all.

Copy the .dmp files to another folder, first.

i dident overclocked anything so far
and overheating would seem a bit weird to me since im having 5 fans in it

added mini's

Great idea to follow these 5 steps to disable jusched.exe. That's an updater for Java and you don't need it. It is mentioned in your latest dump. I do this to my machines immediately upon installing Java, anyhow.

http://www.herongyang.com/Windows/St...a-jusched.html

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Temp\Rar$DI02.093\110209-16906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c07000 PsLoadedModuleList = 0xfffff800`02e44e50
Debug session time: Mon Nov  2 10:46:57.562 2009 (GMT-5)
System Uptime: 0 days 0:13:20.000
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff683ff7eb558, 0, 0, fffff80002c8cae2}

Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1c2 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff683ff7eb558, memory referenced
Arg2: 0000000000000000, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c8cae2, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eaf0e0
 fffff683ff7eb558 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!MiAgeWorkingSet+1c2
fffff800`02c8cae2 488b19          mov     rbx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  jusched.exe

TRAP_FRAME:  fffff880033167a0 -- (.trap 0xfffff880033167a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff683ff7eb558
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c8cae2 rsp=fffff88003316930 rbp=00000003ff7eb55a
 r8=0000000000000001  r9=fffffa80060929f8 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!MiAgeWorkingSet+0x1c2:
fffff800`02c8cae2 488b19          mov     rbx,qword ptr [rcx] ds:fffff683`ff7eb558=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c78469 to fffff80002c78f00

STACK_TEXT:  
fffff880`03316658 fffff800`02c78469 : 00000000`0000000a fffff683`ff7eb558 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`03316660 fffff800`02c770e0 : 00000000`00000000 00000980`00000000 00000000`00001000 fffff800`02dabbfe : nt!KiBugCheckDispatch+0x69
fffff880`033167a0 fffff800`02c8cae2 : 00000000`0000080d 00000000`00000001 00000000`00000002 00000000`0000080c : nt!KiPageFault+0x260
fffff880`03316930 fffff800`02cf9a0e : fffffa80`060929f8 fffff880`00000001 00000000`00000001 fffff880`03316bb0 : nt!MiAgeWorkingSet+0x1c2
fffff880`03316ae0 fffff800`02c8d6e2 : 00000000`00000321 00000000`00000000 fffffa80`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x49926
fffff880`03316b80 fffff800`02c8d96f : 00000000`00000008 fffff880`03316c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03316bd0 fffff800`02f1c166 : fffffa80`03cf2b60 00000000`00000080 fffffa80`03c759e0 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03316d40 fffff800`02c57486 : fffff880`02f63180 fffffa80`03cf2b60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03316d80 00000000`00000000 : fffff880`03317000 fffff880`03311000 fffff880`03316710 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+1c2
fffff800`02c8cae2 488b19          mov     rbx,qword ptr [rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiAgeWorkingSet+1c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiAgeWorkingSet+1c2

BUCKET_ID:  X64_0xA_nt!MiAgeWorkingSet+1c2

Followup: MachineOwner
---------

But, looking at the dump, I don't think it was directly the cause.

"Probably caused by : memory_corruption"

Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

Bsed on the fact that second newest dump mentions "avgcsrva.exe", it's a good idea to completely uninstall 3rd party antivirus and firewall apps. This is a normal troubleshooting step for bsod. Don't just disable them as that will not be of any help.

Test machine and see how it goes after.

If still problems, run memtest for a few hours.
Also, from command prompt, run chkdsk /r for all HDD, especially the one where you have the page file located at.

For example: chkdsk /r C:

I did everything you said well the part where i removed my java update and i uninstalled my virus scan i had...
But im still getting bsod.

I tryed to run those execute's but when i try the chkdsk nothing happens ;x

pin0ob said:

I did everything you said well the part where i removed my java update and i uninstalled my virus scan i had...
But im still getting bsod.

I tryed to run those execute's but when i try the chkdsk nothing happens ;x

Did you try the memory diagnostics as torrentg suggested?

These crashes are very unlikely to be caused by anything other than bad hardware - probably the RAM. If you're confident that it's not overclocked or undercooled, then the BIOS needs an update, the memory is mismatched, the timings are off... or something is just plain broken on a hardware level.

well after trying everything you guys suggested nothing works so i contacted my retailer and the being pretty helpfull there sending a it specalist and everything that might be broken or ****ed the will fix it for free so you can close this

Thanxs for your help anyways =)