Windows 7 64bit bsod

usasma · 20 Mar 2010

I don't have the text file results handy - but that's definitely a hardware error that's occurring.

The most likely issue is the video card - but that's not 100% certain.
I'd suggest purchasing a video card from a store with a good return policy. That way you'll be able to get your money back if it turns out that the card isn't the problem.

n0cturnal · 20 Mar 2010

I just recalled that I have a graphic card built in on my motherboard.
Perhaps I could try using that?

n0cturnal · 21 Mar 2010

Did a 3h blended test without a single error or warning with my built in graphics card.. I guess this doesnt look good for my Radeon 4890 :/

usasma · 21 Mar 2010

Errors on the blended test with your Radeon 4890 installed.
No errors with the onboard video card.

That spells out "Radeon 4890" to me.
Check the warranty to see if it's covered.

n0cturnal · 21 Mar 2010

Thanks for the help.

Ive sent a mail to the retailer about the warranty, theres a 24month manufactorbased warranty so I hope it will get sorted.

zigzag3143 · 21 Mar 2010

n0cturnal said:

zigzag3143 said:

Since the version you used didnt find anything I would use the other. (3.5, or 4.x)

Yeah that doesnt make me any wiser.

Well that last crash wasn't caused by memory. It was caused by the direct X portion of your video driver.

Un-install all remnants of your current driver and install a fresh copy.

Ken

Code:

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


Loading Dump File [C:\Users\K\Desktop\031910-16582-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\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
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0281b000 PsLoadedModuleList = 0xfffff800`02a58e50
Debug session time: Fri Mar 19 11:55:41.260 2010 (GMT-4)
System Uptime: 0 days 3:18:13.649
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff880031000e8, 2, 8, fffff880031000e8}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER::DdiSubmitCommand+1b6 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff880031000e8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff880031000e8, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ac30e0
 fffff880031000e8 

CURRENT_IRQL:  2

FAULTING_IP: 
+5e9a952f0417dbb0
fffff880`031000e8 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880044d3700 -- (.trap 0xfffff880044d3700)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000f rbx=0000000000000000 rcx=fffffa800592f000
rdx=fffffa8004cdafc0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880031000e8 rsp=fffff880044d3898 rbp=0000000000000000
 r8=0000000000e4a33f  r9=000000000000000f r10=0000000000000000
r11=fffff8800197c120 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff880`031000e8 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000288c469 to fffff8000288cf00

FAILED_INSTRUCTION_ADDRESS: 
+5e9a952f0417dbb0
fffff880`031000e8 ??              ???

STACK_TEXT:  
fffff880`044d35b8 fffff800`0288c469 : 00000000`0000000a fffff880`031000e8 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`044d35c0 fffff800`0288b0e0 : fffffa80`04063010 fffffa80`0592f000 00000000`00231a69 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`044d3700 fffff880`031000e8 : fffff880`040d06e6 fffffa80`0592f000 fffffa80`0592f000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`044d3898 fffff880`040d06e6 : fffffa80`0592f000 fffffa80`0592f000 00000000`00000000 00000000`00000000 : 0xfffff880`031000e8
fffff880`044d38a0 fffff880`04007d70 : 00000000`ffffd978 00000000`0000000f fffffa80`05939000 fffffa80`0593a410 : dxgkrnl!DXGADAPTER::DdiSubmitCommand+0x1b6
fffff880`044d38e0 fffff880`04039e65 : fffffa80`05939000 fffffa80`00000000 00000000`00000000 fffffa80`05939000 : dxgmms1!VidSchiSendToExecutionQueue+0x87c
fffff880`044d39e0 fffff880`04038d3c : 00000000`000001fd 00000000`00231a69 fffffa80`0622ec30 fffffa80`05936010 : dxgmms1!VidSchiSendToExecutionQueueWithWait+0x179
fffff880`044d3ae0 fffff880`04038398 : fffff800`03ba4000 fffff880`04037d00 fffffa80`00000000 fffffa80`0001f840 : dxgmms1!VidSchiSubmitRenderCommand+0x920
fffff880`044d3cd0 fffff880`04037e96 : 00000000`00000000 fffffa80`056e4010 00000000`00000080 fffffa80`05936010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`044d3d00 fffff800`02b30166 : 00000000`031cce5e fffffa80`0596f060 fffffa80`03973890 fffffa80`0596f060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`044d3d40 fffff800`0286b486 : fffff800`02a05e80 fffffa80`0596f060 fffff800`02a13c40 fffff880`01220bf0 : nt!PspSystemThreadStartup+0x5a
fffff880`044d3d80 00000000`00000000 : fffff880`044d4000 fffff880`044ce000 fffff880`044d3690 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DXGADAPTER::DdiSubmitCommand+1b6
fffff880`040d06e6 f60523d3010002  test    byte ptr [dxgkrnl!g_loggerInfo+0x8 (fffff880`040eda10)],2

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  dxgkrnl!DXGADAPTER::DdiSubmitCommand+1b6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc590

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_dxgkrnl!DXGADAPTER::DdiSubmitCommand+1b6

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_dxgkrnl!DXGADAPTER::DdiSubmitCommand+1b6

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