
Quote: Originally Posted by
wulfstan77
So I recently recieved two HIS 6850's to replace my older ATI 5850. So I do my normal procedure of Uninstalling Drivers and so forth. So I take out the 5850 install the two 6850's, restart computer and install drivers from the CD HIS gave me. I restart log-in and BAM computer screen goes black/red/white and I get BSOD error.
So I figure that I should try each of the cards separately. Do a driver sweep, restart, reinstall drivers again, restart, than I log-in and BAM same dam screen followed by the same BSOD error. The weird thing is both cards do it! Are they DOA or is something else at work? I highly doubt both cards are busted unless UPS dropped the box from 50 feet.
Thanks for your help!
These were caused by your ATItray utility. I would remove it.
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\Seven Forums\021011-34117-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02e52000 PsLoadedModuleList = 0xfffff800`0308fe50
Debug session time: Thu Feb 10 16:04:09.117 2011 (GMT-5)
System Uptime: 0 days 0:00:57.099
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000094, fffffa800560e838, 12, fffff80003051888}
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000094, The exception code that was not handled
Arg2: fffffa800560e838, The address that the exception occurred at
Arg3: 0000000000000012, Parameter 0 of the exception
Arg4: fffff80003051888, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION} Integer division by zero.
FAULTING_IP:
+6558952f041ed920
fffffa80`0560e838 f7f3 div eax,ebx
EXCEPTION_PARAMETER1: 0000000000000012
EXCEPTION_PARAMETER2: fffff80003051888
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: atitray.exe
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff880062ac6f8 -- (.exr 0xfffff880062ac6f8)
ExceptionAddress: fffffa800560e838
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0
TRAP_FRAME: fffff880062ac7a0 -- (.trap 0xfffff880062ac7a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa800560e838 rsp=fffff880062ac930 rbp=0000000000000000
r8=0000000000000080 r9=0000000000000012 r10=fffff80003051888
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
fffffa80`0560e838 f7f3 div eax,ebx
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002efca39 to fffff80002ec2740
STACK_TEXT:
fffff880`062abf28 fffff800`02efca39 : 00000000`0000001e ffffffff`c0000094 fffffa80`0560e838 00000000`00000012 : nt!KeBugCheckEx
fffff880`062abf30 fffff800`02ec1d82 : fffff880`062ac6f8 00000000`00000000 fffff880`062ac7a0 00000000`00000000 : nt!KiDispatchException+0x1b9
fffff880`062ac5c0 fffff800`02ebf574 : fffffa80`0631d370 fffff800`02ee1d1c fffffa80`06a83730 00000000`00000001 : nt!KiExceptionDispatch+0xc2
fffff880`062ac7a0 fffffa80`0560e838 : 00000000`00000000 fffff800`0303ce80 00000000`00000000 fffffa80`0631d370 : nt!KiDivideErrorFault+0xf4
fffff880`062ac930 00000000`00000000 : fffff800`0303ce80 00000000`00000000 fffffa80`0631d370 fffffa80`0631d370 : 0xfffffa80`0560e838
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDispatchException+1b9
fffff800`02efca39 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiDispatchException+1b9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
FAILURE_BUCKET_ID: X64_0x1E_nt!KiDispatchException+1b9
BUCKET_ID: X64_0x1E_nt!KiDispatchException+1b9
Followup: MachineOwner
---------