Solved Random Bluescreens, help a germany guy

madmonkey · Feb 2, 2012

Hi Instinctlol,

Still not really the ideal PSU, only really half addressed the problem by providing additional power.. can you post another CPU-Z log?

Although saying that, there's no signs of memory corruption in the last log.. perhaps too early to tell if this is still an issue. The last error was a video buffer overrun issue.

Code:



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


Loading Dump File [C:\Users\admin\Desktop\PCHF\020212-16046-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Inaccessible path: 'C:\Program Files\Debugging Tools for Windows (x64)\symbols'
Symbol search path is: C:\Program Files\Debugging Tools for Windows (x64)\symbols;http://msdl.microsoft.com/download/symbols;symsrv*symsrv.dll*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a56000 PsLoadedModuleList = 0xfffff800`02c9be90
Debug session time: Thu Feb  2 16:24:22.686 2012 (GMT+0)
System Uptime: 0 days 7:47:11.014
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800534fb99, fffff880021c6068, fffff880021c58c0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DMA_POOL::WaitDmaBufferNotBusy+71 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800534fb99, The address that the exception occurred at
Arg3: fffff880021c6068, Exception Record Address
Arg4: fffff880021c58c0, Context Record Address

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_DMA_POOL::WaitDmaBufferNotBusy+71
fffff880`0534fb99 488b80b0000000  mov     rax,qword ptr [rax+0B0h]

EXCEPTION_RECORD:  fffff880021c6068 -- (.exr 0xfffff880021c6068)
ExceptionAddress: fffff8800534fb99 (dxgmms1!VIDMM_DMA_POOL::WaitDmaBufferNotBusy+0x0000000000000071)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000000b1
Attempt to read from address 00000000000000b1

CONTEXT:  fffff880021c58c0 -- (.cxr 0xfffff880021c58c0)
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000001
rdx=fffffa8008c4d000 rsi=fffffa80086e5850 rdi=fffffa8008c56c60
rip=fffff8800534fb99 rsp=fffff880021c62a0 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=0000000008ef6c90
r11=0000000000000000 r12=fffffa8008c56cc0 r13=0000000000000000
r14=0000000000000000 r15=fffffa8008c4d230
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
dxgmms1!VIDMM_DMA_POOL::WaitDmaBufferNotBusy+0x71:
fffff880`0534fb99 488b80b0000000  mov     rax,qword ptr [rax+0B0h] ds:002b:00000000`000000b1=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000000000b1

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d070e8
 00000000000000b1 

FOLLOWUP_IP: 
dxgmms1!VIDMM_DMA_POOL::WaitDmaBufferNotBusy+71
fffff880`0534fb99 488b80b0000000  mov     rax,qword ptr [rax+0B0h]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff8800534ebc5 to fffff8800534fb99

STACK_TEXT:  
fffff880`021c62a0 fffff880`0534ebc5 : fffffa80`086e5850 00000000`00000000 00000000`80000011 fffffa80`08c02010 : dxgmms1!VIDMM_DMA_POOL::WaitDmaBufferNotBusy+0x71
fffff880`021c6370 fffff880`05349827 : fffffa80`ffffda01 00000000`004f5e6c fffffa80`08c4d230 ffffffff`c01e0001 : dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x2a1
fffff880`021c63c0 fffff880`0534cf05 : fffffa80`00000000 ffffffff`ffffffff 00000000`00000000 fffff8a0`0a997c01 : dxgmms1!VIDMM_GLOBAL::FlushPagingBufferInternal+0x4c3
fffff880`021c6510 fffff880`05348e88 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`021c65c0 : dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+0x26d
fffff880`021c6590 fffff880`05355cf0 : 00000000`00000000 fffffa80`08c4dc60 fffff8a0`0a997ce0 fffff8a0`00000005 : dxgmms1!VIDMM_GLOBAL::DiscardAllocationInternal+0x154
fffff880`021c6710 fffff880`05347904 : fffffa80`086f0870 fffff8a0`0a997ce0 fffff8a0`00000001 fffff880`021c6800 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x530
fffff880`021c6880 fffff880`053477e3 : fffffa80`08c4d000 fffff880`0534776c 00000000`00000000 fffffa80`09fa6aa0 : dxgmms1!VIDMM_GLOBAL::EvictAllAllocationInList+0x40
fffff880`021c68c0 fffff880`0534470d : 00000000`00000123 00000000`00000000 00000000`00000000 fffffa80`00000000 : dxgmms1!VIDMM_GLOBAL::EvictAllReclaimedAllocation+0x43
fffff880`021c6910 fffff880`0535e65d : 00000000`00000000 fffff8a0`002c0cf0 fffffa80`00000000 fffffa80`09fa6aa0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xc79
fffff880`021c6ae0 fffff880`0535e398 : fffff880`0308cfc0 fffff880`0535dd00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`021c6cd0 fffff880`0535de96 : 00000000`00000000 fffffa80`0781dd50 00000000`00000080 fffffa80`08c02010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`021c6d00 fffff800`02d73cce : 00000000`02df5b1c fffffa80`086f0a10 fffffa80`069ab9e0 fffffa80`086f0a10 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`021c6d40 fffff800`02ac7fe6 : fffff880`03088180 fffffa80`086f0a10 fffff880`03093040 fffff880`01233a20 : nt!PspSystemThreadStartup+0x5a
fffff880`021c6d80 00000000`00000000 : fffff880`021c7000 fffff880`021c1000 fffff880`021c6060 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_DMA_POOL::WaitDmaBufferNotBusy+71

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff880021c58c0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_DMA_POOL::WaitDmaBufferNotBusy+71

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_DMA_POOL::WaitDmaBufferNotBusy+71

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

Instinctlol · Feb 2, 2012

Why is it not an ideal PSU? I thought I should get one with 500W and 2 PCI-e connectors :-\

CPU-Z log attached.

madmonkey · Feb 2, 2012

True, but it's only showing a single voltage rail, which was partly what I was worried about. It may be nothing.. as I said it's too early to tell, as there was no signs of memory corruption in your last log. Perhaps there was more than one problem all along, or maybe I'm completely wrong.. need more minidumps when you get them if this is OK? I also forgot that these readings were not available in CPU-Z, are they any more stable in BIOS?

Instinctlol · Feb 2, 2012

Sure, I'll keep you posted with my BSOD's.

12V readings: 12.196 to 12.249

madmonkey · Feb 3, 2012

Looks good. Look forward to the next set of logs. I can't quite grasp though how the blank screen is related to the problem. If the problem with the card, I can't see how it would have made it to the desktop. The card would need to be present to complete the post. If the card had locked up, Windows would have detected the problem and created an 0x116 stop error. There little that can go wrong between that and the actual VGA output of the card itself. Does the monitor go to sleep, or is the picture actually black?

Instinctlol · Feb 3, 2012

It's just black.

madmonkey · Feb 3, 2012

Just something else another colleague of pointed out, can you also confirm it's black from the moment you restart the PC, or at some point when you reach Windows?

Instinctlol · Feb 3, 2012

It's completely black, from the point when I press 'on' to Windows booting. Like there's nothing connected to the screen.

Also, my card makes really weird noises, which I stated before in this thread.
I recorded it. You will hear to different noises, one track is from a cold start (obviously normal), the other one is warm (obviously weird).

EDIT: oh, and when the PC is off (shutdown), my (new) PSU makes a weird high-pitched noise. My old PSU wouldn't do something like that. After some research, I read it could be a faulty capacitor and I should return the PSU. What's your opinion?

EDIT2: Forgot to mention that the noise, coming from my PSU, is gone, when I turn the PSU-switch to off. I can also turn it on again and there won't be a noise.

madmonkey · Feb 4, 2012

OK, graphics card seems to be the next obvious problem by the looks of it. If you have a different VGA cable or preferably, a different monitor you can test on the PC just to be absolutely sure it could be nothing else. The noise you heard from the PSU could have just as easily been caused by a short in a device it's connected to.

Instinctlol · Feb 4, 2012

The card only has DVI or HDMI inputs, so I plugged my PC via HDMI to my TV. Cold boots aren't a problem here.

When the TV is set to an input for example like "HDMI 3", it would show a message "Check signal cable." (The PC is off at this moment)
Now I start the PC and the message would go away, so there's just a black screen, but after 5 seconds the TV shows "No signal." and stays like this.

madmonkey · Feb 4, 2012

You'll need to replace the graphics card then Instinctlol, it's the only remaining component.

Instinctlol · Feb 5, 2012

Okay, I'm going to return it.

Instinctlol · Feb 5, 2012

Here is a new BSOD (still the same card though )

madmonkey · Feb 5, 2012

These are referencing video problems. Not a specific problem as such, but the process active at the time was ATI Control Panel. It's related service had raised an exception which led to the stop error. Different to the previous error but both video related.

Code:


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


Loading Dump File [C:\Users\admin\Desktop\020512-16375-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Inaccessible path: 'C:\Program Files\Debugging Tools for Windows (x64)\symbols'
Symbol search path is: C:\Program Files\Debugging Tools for Windows (x64)\symbols;http://msdl.microsoft.com/download/symbols;symsrv*symsrv.dll*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a10000 PsLoadedModuleList = 0xfffff800`02c55e90
Debug session time: Sun Feb  5 16:53:40.310 2012 (GMT+0)
System Uptime: 0 days 6:20:31.878
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88002db4ea0, fffff88006fe1c10, 0}

Probably caused by : atikmpag.sys ( atikmpag+27ea0 )

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: fffff88002db4ea0, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88006fe1c10, 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: 
atikmpag+27ea0
fffff880`02db4ea0 4c8b4c0af8      mov     r9,qword ptr [rdx+rcx-8]

CONTEXT:  fffff88006fe1c10 -- (.cxr 0xfffff88006fe1c10)
rax=0000000000000040 rbx=fffffa8006b0ee80 rcx=fffff8a10a662990
rdx=00000760b457cf24 rsi=fffffa8006d10700 rdi=fffffa800867c900
rip=fffff88002db4ea0 rsp=fffff88006fe25f8 rbp=fffff8a00a6630f4
 r8=00000000fffff880  r9=0000000007ffffc4 r10=fffff8a00a66305c
r11=fffff8a00a663110 r12=fffffa8006b15040 r13=0000000000000000
r14=fffffa8006b15040 r15=0000000000000008
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
atikmpag+0x27ea0:
fffff880`02db4ea0 4c8b4c0af8      mov     r9,qword ptr [rdx+rcx-8] ds:002b:00000001`bebdf8ac=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  atieclxx.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88002db4ea0

STACK_TEXT:  
fffff880`06fe25f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmpag+0x27ea0


FOLLOWUP_IP: 
atikmpag+27ea0
fffff880`02db4ea0 4c8b4c0af8      mov     r9,qword ptr [rdx+rcx-8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmpag+27ea0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ea760b6

STACK_COMMAND:  .cxr 0xfffff88006fe1c10 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_atikmpag+27ea0

BUCKET_ID:  X64_0x3B_atikmpag+27ea0

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

0: kd> lmvft m atikmpag
start             end                 module name
fffff880`02d8d000 fffff880`02de2000   atikmpag \SystemRoot\system32\DRIVERS\atikmpag.sys
    Loaded symbol image file: atikmpag.sys
    Symbol file: atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Wed Oct 26 02:21:58 2011 (4EA760B6)
    CheckSum:         0005289A
    ImageSize:        00055000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

madmonkey · Feb 21, 2012

Hello Instinctlol, has this helped at all? any update would be great.

-----
Thread marked [Pending]...

Log in or Join Us

Solved Random Bluescreens, help a germany guy

madmonkey Site Manager

Instinctlol Bronze Member

Attached Files:

INSTINCTLOL-PC.txt

madmonkey Site Manager

Google Advertisement

Instinctlol Bronze Member

madmonkey Site Manager

Instinctlol Bronze Member

madmonkey Site Manager

Instinctlol Bronze Member

madmonkey Site Manager

Instinctlol Bronze Member

madmonkey Site Manager

Instinctlol Bronze Member

Instinctlol Bronze Member

Attached Files:

020512-16375-01.zip

madmonkey Site Manager

madmonkey Site Manager

Random Bluescreens, help a germany guy

Log in or Join Us

Solved Random Bluescreens, help a germany guy

madmonkey Site Manager

Instinctlol Bronze Member

Attached Files:

INSTINCTLOL-PC.txt

madmonkey Site Manager

Google Advertisement

Instinctlol Bronze Member

madmonkey Site Manager

Instinctlol Bronze Member

madmonkey Site Manager

Instinctlol Bronze Member

madmonkey Site Manager

Instinctlol Bronze Member

madmonkey Site Manager

Instinctlol Bronze Member

Instinctlol Bronze Member

Attached Files:

020512-16375-01.zip

madmonkey Site Manager

madmonkey Site Manager

Random Bluescreens, help a germany guy

Useful Searches