New
#1
another BSOD need help with minidump
HI,
I just got a EVGA gtx 260, downloaded the newest drivers and just got a BSOD,
I uploaded the minidump file if someone can help me with this.
thanks a lot
Renaud
another BSOD need help with minidump
-
-
New #2
This dump looks like you were playing AION and the video driver crashed killing dxgmms1.sys.. Since its Wow I assume the game is 32bit. It looks like the video driver is the probable cause.
Remedies. check and re-install the vid driver if necessary. Heat a possible issue?
Run sfc /scannow to verify the system files. Run Memetest on the memory.
Hope this helps
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\101509-21450-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*Symbol information
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`02a4b000 PsLoadedModuleList = 0xfffff800`02c88e50
Debug session time: Thu Oct 15 18:58:52.736 2009 (GMT-4)
System Uptime: 0 days 0:56:48.624
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8800418b7ac, fffff8800acff5c0, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec )
Followup: MachineOwner
---------
0: 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: fffff8800418b7ac, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800acff5c0, 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:
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec
fffff880`0418b7ac 488b11 mov rdx,qword ptr [rcx]
CONTEXT: fffff8800acff5c0 -- (.cxr 0xfffff8800acff5c0)
rax=0000000000000000 rbx=0000000000000000 rcx=0040000000000000
rdx=fffff8a008a194c0 rsi=fffff8a008a194c0 rdi=0000000000000000
rip=fffff8800418b7ac rsp=fffff8800acfffa0 rbp=fffffa8008931000
r8=0000000000044000 r9=0000000000000000 r10=0000000000000001
r11=fffff8a008a195c8 r12=0000000000000000 r13=0000000000000001
r14=fffffa80089406f0 r15=fffff8a008a195c8
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0xfec:
fffff880`0418b7ac 488b11 mov rdx,qword ptr [rcx] ds:002b:00400000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: AION.bin
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8800418b7ac
STACK_TEXT:
fffff880`0acfffa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0xfec
FOLLOWUP_IP:
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec
fffff880`0418b7ac 488b11 mov rdx,qword ptr [rcx]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
STACK_COMMAND: .cxr 0xfffff8800acff5c0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec
BUCKET_ID: X64_0x3B_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec
Followup: MachineOwner
---------
-
New #3
Thanks a lot for the super quick reply,
just found out that one of my fan wasn't working but the GPU was at around 70 C is it too much?
And I know how to run the mem test but I dont know what is a sfc / scannow
-
New #4
R
I dont even know what computer you have. You can find out by going to the vdei card maker for it and the computer maker for that. 70C is pretty warm. If the BSOD's stop now that the other fan is running that was the culprit. If not and you get another one post it and someone will track it down
Ken
-
New #5
memtest report that there is a hardware problem...and to contact manufacturer
what should I do next?
thank you for your time
Renaud
that is my computer
OS
windows 7 x64
CPU
Intel Core 2 Quad Q9550 Yorkfield 2.83GHz 12MB L2 Cache
Motherboard
ASUS P5Q3 LGA 775 Intel P45 ATX Intel Motherboard
Memory
OCZ Reaper HPC 8GB (4 x 2GB) DDR3 1600 (PC3 12800)
Graphics Card(s)
BFG 9500GT for now (evga 260 gtx coming (RMA))
Hard Drives
Seagate Barracuda 7200.10 ST3250310AS 250GB 7200 RPM 8MB Cache
PSU
CORSAIR CMPSU-750TX 750W ATX12V / EPS12V SLI Ready CrossFire
Case
XCLIO A380BK Fully Black SECC 1.0mm thickness ATX Full Tower
Cooling
2x 250mm 1x 120mm
-
New #6
-
New #7
I'm not overclocking, it didn'y say what problem : on reboot it said ''your computer as a memory problem'' I'm not running a raid, no external drive, just a display mouse and keyboard.
the memtest reported a problem in the second phase of the test.
-
New #8
R
did you run that from a cd/dvd or from within windows?
-
New #9
within windows
-
New #10
what memory test did you run (sorry)
Quote
Related Discussions