Blue screen

evo u kratko, nabavio sam novo racunalo i stavio si windows 7 64 bitni..prije toga sam imao jedno tjedan dana xp i sve je super radilo..i sad mi sve radi, ali vec 3x za redom u zadnja 2,3 dana mi se pojavi nakon jedno 40tak min igranja wowa kojeg pokrecem s prijenosnog hard diska blue screen ( i mozda cak jednom sam od sebe dok sam bio na internetu ali se ne sjecam tocno) .. inace sve radi u redu, igro sam jos do sada gta sa i sve je ok..za sada..eto zanima me kako saznati dali je problem harverske ili softverske prirode, dali ako se nastavi ovaj problem bi trebao samo reinstalirati winowse ili je tu moguci nekakav problem s komponentama racunala?

ispricavam se, tek sam sada skuzio da ima post o tome..ev probao sam, nadam se da je to to :

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


Loading Dump File [C:\Windows\Minidump\111809-29109-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02811000 PsLoadedModuleList = 0xfffff800`02a4ee50
Debug session time: Wed Nov 18 00:16:58.899 2009 (GMT+1)
System Uptime: 0 days 1:36:58.920
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff80002888e72}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
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: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002888e72

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  sidebar.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002882469 to fffff80002882f00

STACK_TEXT: 
fffff880`009efc68 fffff800`02882469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009efc70 fffff800`02880932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009efdb0 fffff800`02888e72 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00fff880`02f22fb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterrupt+0x32


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`02880932 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Followup: MachineOwner

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


Loading Dump File [C:\Windows\Minidump\112309-23540-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e67000 PsLoadedModuleList = 0xfffff800`030a4e50
Debug session time: Mon Nov 23 13:45:39.308 2009 (GMT+1)
System Uptime: 0 days 0:30:35.853
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002edcd97, fffff88007d8f050, 0}

Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+47 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002edcd97, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007d8f050, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!PspReturnQuota+47
fffff800`02edcd97 488b5d00        mov     rbx,qword ptr [rbp]

CONTEXT:  fffff88007d8f050 -- (.cxr 0xfffff88007d8f050)
rax=fffff80003086a00 rbx=fffffa80067d8180 rcx=00fffa80058324c0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000070
rip=fffff80002edcd97 rsp=fffff88007d8fa30 rbp=00fffa80058324c0
 r8=0000000000000000  r9=0000000000000070 r10=0000000000000000
r11=fffff88007d8fb38 r12=0000000000000000 r13=0000000000000000
r14=0000000000000005 r15=00fffa80058324c0
iopl=0         nv up ei pl zr ac po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010256
nt!PspReturnQuota+0x47:
fffff800`02edcd97 488b5d00        mov     rbx,qword ptr [rbp] ss:0018:00fffa80`058324c0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800031d2174 to fffff80002edcd97

STACK_TEXT: 
fffff880`07d8fa30 fffff800`031d2174 : fffffa80`067d8180 00000000`00000070 00fffa80`058324c0 00000000`0460f200 : nt!PspReturnQuota+0x47
fffff880`07d8fa90 fffff800`02ede0bc : 00fffa80`058324c0 00000000`00000000 fffffa80`06421b30 fffffa80`039f9200 : nt!ObpFreeObject+0x224
fffff880`07d8fae0 fffff800`031ec194 : fffffa80`06421b30 00000000`00000000 fffffa80`04e63750 00000000`00000000 : nt!ObfDereferenceObject+0xdc
fffff880`07d8fb40 fffff800`031ec094 : 00000000`000002ac fffffa80`06421b30 fffff8a0`071f7790 00000000`000002ac : nt!ObpCloseHandleTableEntry+0xc4
fffff880`07d8fbd0 fffff800`02ed8153 : fffffa80`04e63750 fffff880`07d8fca0 00000000`01a813a0 fffffa80`067e4af0 : nt!ObpCloseHandle+0x94
fffff880`07d8fc20 00000000`76f9ffaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0460ea48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f9ffaa


FOLLOWUP_IP:
nt!PspReturnQuota+47
fffff800`02edcd97 488b5d00        mov     rbx,qword ptr [rbp]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!PspReturnQuota+47

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

STACK_COMMAND:  .cxr 0xfffff88007d8f050 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!PspReturnQuota+47

BUCKET_ID:  X64_0x3B_nt!PspReturnQuota+47

Followup: MachineOwner

eto to su mi 3 minidumpa..