BSOD issue on new computer, minidump included

[Elightos]

And again, i sadly have an issue on a brand new PC. It keeps on rebooting and dropping in BSOD's while playing WoW. Afaik the computer is running stock speeds, so that shouldn't be a problem, could anybody read these 2 minidumps and tell me where the problem lies? :-/

cpu = Q9550
Ram = 4 gb G.skill 1000 Mhz cas 5
GPU = 4870 1 gb
1 500 gb HDD seagate
gigabyte motherboard p45 chipset

 

[usasma]

Quickly (I've gotta go out), it's most likely either your video drivers (dxgkrnl is involved), or it's an issue with your WoW installation. I'd try replacing your video drivers first.

 

[usasma]

Here's the minidumps:

1st one:

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


Loading Dump File [C:\Users\FUBAR-RC1-Desktop\Downloads\Minidump5\Mini052309-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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18226.amd64fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0xfffff800`02006000 PsLoadedModuleList = 0xfffff800`021cbdb0
Debug session time: Sat May 23 11:30:39.982 2009 (GMT-4)
System Uptime: 0 days 1:02:23.231
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa0007bb5530, 0, fffffa6002cc6d31, 5}


Could not read faulting driver name
Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa0007bb5530, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffffa6002cc6d31, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000222f080
 fffffa0007bb5530 

FAULTING_IP: 
dxgkrnl!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
fffffa60`02cc6d31 488b02          mov     rax,qword ptr [rdx]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffffa600367e8e0 -- (.trap 0xfffffa600367e8e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa600367ea98 rbx=0000000000000000 rcx=fffffa8006b2c000
rdx=fffffa0007bb5530 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa6002cc6d31 rsp=fffffa600367ea70 rbp=fffffa80047519c8
 r8=fffffa800465d601  r9=0000000000000000 r10=fffffa800650a000
r11=000000000000f800 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
dxgkrnl!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x19:
fffffa60`02cc6d31 488b02          mov     rax,qword ptr [rdx] ds:3b20:fffffa00`07bb5530=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800020687f2 to fffff8000205a650

STACK_TEXT:  
fffffa60`0367e7e8 fffff800`020687f2 : 00000000`00000050 fffffa00`07bb5530 00000000`00000000 fffffa60`0367e8e0 : nt!KeBugCheckEx
fffffa60`0367e7f0 fffff800`020591d9 : 00000000`00000000 fffff800`0205dced fffffa60`01763100 fffffa80`045c5340 : nt!MmAccessFault+0x4f2
fffffa60`0367e8e0 fffffa60`02cc6d31 : fffffa80`046e7010 00000000`0000e179 ffffffff`ffffffc9 fffffa80`04367010 : nt!KiPageFault+0x119
fffffa60`0367ea70 fffffa60`02cc4a36 : fffffa80`045c5340 00000000`00000000 00000000`00000006 00000000`00000000 : dxgkrnl!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x19
fffffa60`0367eaa0 fffffa60`02ce0200 : fffffa60`01766cc0 fffff880`0b6fbbf0 fffffa80`00000000 fffffa80`0465d6d0 : dxgkrnl!VIDMM_GLOBAL::PrepareDmaBuffer+0x2de
fffffa60`0367eb50 fffffa60`02cdffdc : fffffa60`01766cc0 fffffa80`0398c900 00000000`00000000 fffffa60`00000000 : dxgkrnl!VidSchiSubmitRenderCommand+0x1b0
fffffa60`0367ece0 fffffa60`02cdfce1 : 00000000`00000000 fffffa80`046e7010 00000000`00000080 fffffa80`067ff540 : dxgkrnl!VidSchiSubmitQueueCommand+0x50
fffffa60`0367ed10 fffff800`0227efd3 : fffffa80`06b2bbb0 fffff800`02054947 fffffa60`019db1f0 00000000`00000001 : dxgkrnl!VidSchiWorkerThread+0xb1
fffffa60`0367ed50 fffff800`02094816 : fffffa60`01763180 fffffa80`06b2bbb0 fffffa60`0176cd40 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`0367ed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
fffffa60`02cc6d31 488b02          mov     rax,qword ptr [rdx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgkrnl!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4893b63f

FAILURE_BUCKET_ID:  X64_0x50_dxgkrnl!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19

BUCKET_ID:  X64_0x50_dxgkrnl!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19

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

2nd One:

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


Loading Dump File [C:\Users\FUBAR-RC1-Desktop\Downloads\Minidump5\Mini052309-02.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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18226.amd64fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0xfffff800`0205e000 PsLoadedModuleList = 0xfffff800`02223db0
Debug session time: Sat May 23 11:49:51.944 2009 (GMT-4)
System Uptime: 0 days 0:17:05.112
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8030d8d3e58, 1, fffffa6002cbb434, 5}


Could not read faulting driver name
Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+134 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8030d8d3e58, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffffa6002cbb434, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002287080
 fffff8030d8d3e58 

FAULTING_IP: 
dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+134
fffffa60`02cbb434 488908          mov     qword ptr [rax],rcx

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffffa60078677e0 -- (.trap 0xfffffa60078677e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8030d8d3e58 rbx=0000000000000000 rcx=fffff8010d8d3e58
rdx=fffffa8006843000 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa6002cbb434 rsp=fffffa6007867970 rbp=0000000000000000
 r8=fffffa80068a03b0  r9=0000000000000001 r10=fffffa800689fc30
r11=fffffa6007867940 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+0x134:
fffffa60`02cbb434 488908          mov     qword ptr [rax],rcx ds:79d0:fffff803`0d8d3e58=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800020c07f2 to fffff800020b2650

STACK_TEXT:  
fffffa60`078676e8 fffff800`020c07f2 : 00000000`00000050 fffff803`0d8d3e58 00000000`00000001 fffffa60`078677e0 : nt!KeBugCheckEx
fffffa60`078676f0 fffff800`020b11d9 : 00000000`00000001 fffffa60`02c0676f fffffa80`06837500 fffffa80`045cbea0 : nt!MmAccessFault+0x4f2
fffffa60`078677e0 fffffa60`02cbb434 : fffffa80`045cbea0 fffffa80`045cbea0 fffff880`0ef9d440 00000000`00000000 : nt!KiPageFault+0x119
fffffa60`07867970 fffffa60`02cc8057 : fffff880`00000000 fffffa60`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+0x134
fffffa60`07867a40 fffffa60`02c07a93 : fffffa80`07b988e0 fffffa60`07867ca0 00000000`00000174 fffffa80`6d4d6956 : dxgkrnl!VIDMM_DMA_POOL::RemoveDmaBufferFromPool+0x103
fffffa60`07867a90 fffffa60`02c4cde9 : fffff880`0b16e2c0 fffff880`0b16e2c0 fffffa60`07867ca0 fffff880`0b16e2c0 : dxgkrnl!VIDMM_DMA_POOL::`scalar deleting destructor'+0x6b
fffffa60`07867ac0 fffffa60`02c4e98f : fffffa60`07867ba8 fffffa60`02c071da fffff880`0b16e2c0 fffffa80`065ea000 : dxgkrnl!DXGCONTEXT::Destroy+0x6d
fffffa60`07867b30 fffffa60`02c4c401 : fffff880`09744000 fffffa80`041d1060 00000000`0007ee70 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyContext+0x83
fffffa60`07867b70 fffff960`001c2442 : 00000000`7efdd000 fffffa80`041d1060 00000000`000007f8 00000000`00000020 : dxgkrnl!DxgkDestroyContext+0x1e9
fffffa60`07867bf0 fffff800`020b20f3 : fffffa80`041d1060 fffffa60`07867ca0 00000000`7efdd000 fffffa80`07d71bb0 : win32k!NtGdiDdDDIDestroyContext+0x12
fffffa60`07867c20 00000000`7485b5da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0007e598 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7485b5da


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+134
fffffa60`02cbb434 488908          mov     qword ptr [rax],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+134

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4893b63f

FAILURE_BUCKET_ID:  X64_0x50_dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+134

BUCKET_ID:  X64_0x50_dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+134

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

 

[basshead760]

I had similar problems. I had this problem on two identical computers where they would work fine for a while then BSoD with Kernel Stack Page Errors. Both computers were running 500gig Seagate Hdd Momentus 5400.6. They both cleared the comprehensive hdd test via the BIOS. Finally, HP sent me a WD 500gig Hdd, and now 3 days later, no BSoD's. So it might be your hdd.

 

[Elightos]

i'll try updating the GPU drivers, i don't have a spare HDD, so that's going to be tough

 

[usasma]

I recommend that you use the hard drive test available from the manufacturer of your hard drive (rather than any built in tests). This is because the hard drive manufacturer often builds in additional testing routines that aren't addressed by the more generic tests.

To check the file system on the hard drive:

Go to Start and type in "cmd.exe" (without the quotes) and press Enter
In the black window that appears type "chkdsk /r" (without the quotes) and press Enter
The system will tell you it can't do it right now, and will ask if you want to run it on the next reboot. Answer Y (for yes), press Enter, and then reboot.
Let the test run (it may take a while) until the system boots back into Windows