Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Blue Screen of Death


  • Please log in to reply
1 reply to this topic

#1 MrJamez

MrJamez

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:London
  • Local time:11:52 AM

Posted 30 August 2012 - 03:47 PM

Hey guys,

Playing some BF3 today and I got a BSOD. I had just done a small overclock (only 15 MHz on the GPU and memory clock). Not sure whether that was the cause of it though. It's never happened before so I assume it is but I wouldn't have thought 15MHz would've caused a BSOD.

Here's the Memory dump info:
________

Microsoft ® Windows Debugger Version 6.2.9200.16384 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*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 Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`03a1a000 PsLoadedModuleList = 0xfffff800`03c5e670
Debug session time: Thu Aug 30 20:43:30.797 2012 (UTC + 1:00)
System Uptime: 0 days 6:34:55.921
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols

Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff880071b4d49, fffff88008d9b6a8, fffff88008d9af00}

Probably caused by : hardware ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+7d )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880071b4d49, The address that the exception occurred at
Arg3: fffff88008d9b6a8, Exception Record Address
Arg4: fffff88008d9af00, 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_GLOBAL::ReferenceAllocationForPreparation+7d
fffff880`071b4d49 0000 add byte ptr [rax],al

EXCEPTION_RECORD: fffff88008d9b6a8 -- (.exr 0xfffff88008d9b6a8)
ExceptionAddress: fffff880071b4d49 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x000000000000007d)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

CONTEXT: fffff88008d9af00 -- (.cxr 0xfffff88008d9af00)
rax=0000000000000000 rbx=fffff8a01644a010 rcx=fffffa800902a690
rdx=fffffa8008401f70 rsi=fffffa800901b000 rdi=fffffa800901b000
rip=fffff880071b4d49 rsp=fffff88008d9b8e0 rbp=fffffa800d92c368
r8=fffffa800ae04300 r9=0000000000000000 r10=0000000000000000
r11=0000000000000176 r12=fffffa8008401f70 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x7d:
fffff880`071b4d49 0000 add byte ptr [rax],al ds:002b:00000000`00000000=??
Resetting default scope

DEFAULT_BUCKET_ID: NULL_DEREFERENCE

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

EXCEPTION_PARAMETER2: 0000000000000000

WRITE_ADDRESS: 0000000000000000

FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+7d
fffff880`071b4d49 0000 add byte ptr [rax],al

BUGCHECK_STR: 0x7E

MISALIGNED_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+7d
fffff880`071b4d49 0000 add byte ptr [rax],al

LAST_CONTROL_TRANSFER: from fffff880071b1ed3 to fffff880071b4d49

STACK_TEXT:
fffff880`08d9b8e0 fffff880`071b1ed3 : 00000000`00000000 fffffa80`0c3a6120 00000000`00000152 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x7d
fffff880`08d9b910 fffff880`071cc65d : 00000000`00000000 fffff8a0`019b3d40 fffffa80`00000000 fffffa80`0ae043b0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`08d9bae0 fffff880`071cc398 : fffff800`00b96080 fffff880`071cbd00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`08d9bcd0 fffff880`071cbe96 : 00000000`00000000 fffffa80`0a5a5d50 00000000`00000080 fffffa80`08091010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`08d9bd00 fffff800`03d2fe6a : 00000000`fffffc32 fffffa80`090024b0 fffffa80`06a385a0 fffffa80`090024b0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`08d9bd40 fffff800`03a89ec6 : fffff800`03c0be80 fffffa80`090024b0 fffff800`03c19cc0 fffff880`08d9be40 : nt!PspSystemThreadStartup+0x5a
fffff880`08d9bd80 00000000`00000000 : fffff880`08d9c000 fffff880`08d96000 fffff880`08d9b680 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+7d

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .cxr 0xfffff88008d9af00 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID: X64_IP_MISALIGNED_dxgmms1.sys

BUCKET_ID: X64_IP_MISALIGNED_dxgmms1.sys

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

Any help would be much appreciated.

thanks,
James


BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,646 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:06:52 AM

Posted 30 August 2012 - 04:15 PM

If this didn't happen before you overclocked and it did happen after you overclocked I'm going to go out on a limb and say it's because you overclocked. Set it back to normal speed and see if it recurs.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users