another BSOD need help with minidump

[Renaudlabrie]

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

 

[zigzag3143]

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
---------

 

[Renaudlabrie]

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

 

[zigzag3143]

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

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

 

[Renaudlabrie]

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

 

[zigzag3143]

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

Did memtest say what problem? Are you overclocing? running a raid? anything unusual like finger print readers, external USB drives, etc

How long did it take memtest to report an error?

Ken

 

[Renaudlabrie]

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.

 

[zigzag3143]

R

did you run that from a cd/dvd or from within windows?

 

[Renaudlabrie]

within windows

 

[zigzag3143]

what memory test did you run (sorry)

 

[Renaudlabrie]

control panel /admin tools / windows memory diagnostic

 

[zigzag3143]

control panel /admin tools / windows memory diagnostic

Great

Im actually glad you did. since it was done within windows there might be some log entries in event viewer. can you go into event viewer windows log>application tab, them system tab. See if there are any listings about the memory test.

If there isnt anything in event viewer you may want to try pulling all but 2 gigs of ram and re-running the test.

The dump did look like memory but it was too ambiguous to tell. Im not certain about voltage settings in quad cores so I have to pass that to someone who knows but sometimes a slight voltage tweak settle the instability down. Dont know

Now comes the hard part. testing until you isolate the individual component.

 

[Renaudlabrie]

Log Name: System
Source: Microsoft-Windows-MemoryDiagnostics-Results
Date: 2009-10-15 19:57:56
Event ID: 1102
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: michel-PC
Description:
The Windows Memory Diagnostic tested the computer's memory and detected hardware errors. To identify and repair these problems, contact the computer manufacturer
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-MemoryDiagnostics-Results" Guid="{5F92BC59-248F-4111-86A9-E393E12C6139}" />
<EventID>1102</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2009-10-15T23:57:56.830865600Z" />
<EventRecordID>8845</EventRecordID>
<Correlation />
<Execution ProcessID="2444" ThreadID="2552" />
<Channel>System</Channel>
<Computer>michel-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<Results xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2005/08/windows/Reliability/Postboot/Events">
<LaunchType>Manual</LaunchType>
<CompletionType>Fail</CompletionType>
<MemorySize>8190</MemorySize>
<TestType>10</TestType>
<TestDuration>630</TestDuration>
<TestCount>12</TestCount>
<NumPagesTested>2095531</NumPagesTested>
<NumPagesUnTested>1123</NumPagesUnTested>
<NumBadPages>13</NumBadPages>
<T1NumBadPages>0</T1NumBadPages>
<T2NumBadPages>0</T2NumBadPages>
<T3NumBadPages>0</T3NumBadPages>
<T4NumBadPages>0</T4NumBadPages>
<T5NumBadPages>0</T5NumBadPages>
<T6NumBadPages>0</T6NumBadPages>
<T7NumBadPages>0</T7NumBadPages>
<T8NumBadPages>0</T8NumBadPages>
<T9NumBadPages>1</T9NumBadPages>
<T10NumBadPages>11</T10NumBadPages>
<T11NumBadPages>0</T11NumBadPages>
<T12NumBadPages>1</T12NumBadPages>
<T13NumBadPages>0</T13NumBadPages>
<T14NumBadPages>0</T14NumBadPages>
<T15NumBadPages>0</T15NumBadPages>
<T16NumBadPages>0</T16NumBadPages>
</Results>
</UserData>
</Event>

 

[Renaudlabrie]

also found this

Log Name: System
Source: Service Control Manager
Date: 2009-10-15 19:46:15
Event ID: 7016
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: michel-PC
Description:
The NVIDIA Display Driver Service service has reported an invalid current state 32.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2009-10-15T23:46:15.953197900Z" />
<EventRecordID>8744</EventRecordID>
<Correlation />
<Execution ProcessID="476" ThreadID="2316" />
<Channel>System</Channel>
<Computer>michel-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">NVIDIA Display Driver Service</Data>
<Data Name="param2">32</Data>
</EventData>
</Event>

 

[zigzag3143]

R

Ok so we know you have a memory problem. might just be voltage. I am out of my element here. You can check what the voltages currently are but someone with some overclocking/unvolting can help you more. In the mean time since you have 8 gigs pull 4 and mem test. if ok swap the other 4 gigs into the same slots you just used for test 1. repeat untill you have tested all 8 gigs let us know the results

Ken

 

[Renaudlabrie]

thanks a lot, i'm running video memory stress test and there is a milion errors found, i'll try pulling out ram after the test.

 

[thefabe]

When I was taught to test memory I was told to test it 1 stick at a time. Why because if you run 2 sticks and it creates errors then you still won't know which stick it is. So I reccommend 1 stick at a time run the test several times |MG| Memtest86 3.5 Download I would also reccomend that you run CPUid to verify that your running the same sticks not so much as manufacturer but timings and voltages CPUID. If purchased at different times and not in sets. Fabe

 

[Renaudlabrie]

ok I didn't run with one stick but two stick, but I did all the combination so I could see which stick was broken...but each time I ran the mem test...no problems were found....

i'm a bit confused

 

[usasma]

It appears that there's a problem with your memory.
Some memory tests test more than just the RAM.
If this is the case with yours, then I'd have to wonder about damage to the VRAM on your video card because of possible overheating due to the inoperative fan.

 

[Renaudlabrie]

the thing is that I've had the same BSOD with other videocards....