Constant Blue screen. Need help. Dump file attached.

[Sage Connel]

Hi guys, I'm having constant blue screens, cant pinpoint a solution. Heres the dump file if anyone can help. Thanks!

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.17.amd64fre.th2_release.151121-2308
Machine Name:
Kernel base = 0xfffff801`b9a14000 PsLoadedModuleList = 0xfffff801`b9cf2c70
Debug session time: Tue Jan 12 21:14:20.391 2016 (UTC - 5:00)
System Uptime: 2 days 6:02:33.097
*******************************************************************************
* *
* 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: fffff8011d6f4993, The address that the exception occurred at
Arg3: ffffd0012bb60738, Exception Record Address
Arg4: ffffd0012bb5ff50, Context Record Address

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

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

FAULTING_IP:
dxgmms2!VIDMM_SEGMENT::InvalidateAllVirtualAddress+4f
fffff801`1d6f4993 488b36 mov rsi,qword ptr [rsi]

EXCEPTION_RECORD: ffffd0012bb60738 -- (.exr 0xffffd0012bb60738)
ExceptionAddress: fffff8011d6f4993 (dxgmms2!VIDMM_SEGMENT::InvalidateAllVirtualAddress+0x000000000000004f)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT: ffffd0012bb5ff50 -- (.cxr 0xffffd0012bb5ff50)
rax=ffffe000591cf040 rbx=0000000000000000 rcx=00000000ffffffff
rdx=0000000000000000 rsi=0000000000000000 rdi=ffffc000bf3d7a40
rip=fffff8011d6f4993 rsp=ffffd0012bb60970 rbp=ffffe00058079ec0
r8=ffffc000bf3d7c10 r9=0000000000000000 r10=7fffc000bf3d7c10
r11=7ffffffffffffffc r12=0000000000000010 r13=ffffc000baeca110
r14=ffffc000b66587d8 r15=ffffc000baeca110
iopl=0 nv up ei pl nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010203
dxgmms2!VIDMM_SEGMENT::InvalidateAllVirtualAddress+0x4f:
fffff801`1d6f4993 488b36 mov rsi,qword ptr [rsi] ds:002b:00000000`00000000=0000000000000000
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

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

EXCEPTION_PARAMETER2: 0000000000000000

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000000

FOLLOWUP_IP:
dxgmms2!VIDMM_SEGMENT::InvalidateAllVirtualAddress+4f
fffff801`1d6f4993 488b36 mov rsi,qword ptr [rsi]

BUGCHECK_STR: AV

EXCEPTION_STR: 0x0

LAST_CONTROL_TRANSFER: from fffff8011d6eb0c7 to fffff8011d6f4993

STACK_TEXT:
ffffd001`2bb60970 fffff801`1d6eb0c7 : 00000000`00000000 00000000`00000000 ffffe000`5881b010 ffffe000`5db314c0 : dxgmms2!VIDMM_SEGMENT::InvalidateAllVirtualAddress+0x4f
ffffd001`2bb60a50 fffff801`1ac718d6 : ffffe000`5881b010 fffff801`b9de6101 fffff801`b9da7200 fffff801`1ab41ec5 : dxgmms2!VIDMM_GLOBAL::InvalidateAllVirtualAddresses+0x27
ffffd001`2bb60a80 fffff801`1ac732af : 00000000`00000000 ffffe000`5db314c0 ffffe000`5881b010 00000000`00000000 : dxgkrnl!DXGADAPTER:repareToReset+0x76
ffffd001`2bb60ad0 fffff801`1ac86f55 : ffffe000`57c60160 00000000`00000000 ffff173a`00000000 fffff801`b9da7200 : dxgkrnl!DXGADAPTER::Reset+0x97
ffffd001`2bb60b20 fffff801`1ac870ab : 00000000`00000500 fffff801`b9da7340 ffffe000`5584c1e0 fffff801`1a2fffd0 : dxgkrnl!TdrResetFromTimeout+0x15
ffffd001`2bb60b50 fffff801`b9a7eb79 : ffffe000`591cf040 fffff801`1ac87050 ffffe000`5813bd80 ffffe000`0000b000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x5b
ffffd001`2bb60b80 fffff801`b9a1d125 : fffff901`42282c00 00000000`00000080 ffffe000`558b2040 ffffe000`591cf040 : nt!ExpWorkerThread+0xe9
ffffd001`2bb60c10 fffff801`b9b5b906 : ffffd001`265dc180 ffffe000`591cf040 fffff801`b9a1d0e4 fffff961`6cba7f19 : nt!PspSystemThreadStartup+0x41
ffffd001`2bb60c60 00000000`00000000 : ffffd001`2bb61000 ffffd001`2bb5b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgmms2!VIDMM_SEGMENT::InvalidateAllVirtualAddress+4f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5632d236

STACK_COMMAND: .cxr 0xffffd0012bb5ff50 ; kb

FAILURE_BUCKET_ID: X64_AV_dxgmms2!VIDMM_SEGMENT::InvalidateAllVirtualAddress+4f

BUCKET_ID: X64_AV_dxgmms2!VIDMM_SEGMENT::InvalidateAllVirtualAddress+4f

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


This free analysis is provided by OSR Open Systems Resources, Inc.
Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window)

 

[Laptop_Nerd]

Hi,

When do you get the BSOD? (browsing, playing games or even while on idle)

- Start by running Windows Update, install all updates available.
- Next is to install the latest driver for your Network Adapters. (LAN & Wireless)
- For your graphics card do a clean install of it. Please refer to the link below for the complete guide.
- http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html
- Also do check the motherboard manufacturer site for new updates for BIOS.
- Just to be sure do also a virus/malware scan. Please refer to the link below for tools and guide.
- http://www.tomsguide.com/faq/id-1691891/removing-malware-proven-completely-remove-bitcoin-mining-malware.html
- If all these will not work I would suggest doing a clean install of Windows 10.

 

[Sage Connel]

Sorry. I probably should have stared with I've tried all of those. Except update bios. Will do and update

 

[johnbl]

video card stopped responding and directx attempted to reset it. It still did not respond.
Directx tried to clean up the virutual memory the card was using and one of the memory addresses was bogus, this triggered the bugcheck.

I would look for sound driver conflicts first then hardware problems with the GPU,

Make sure your power is good to the video card, check the power connections, make sure it is not overheating, remove any GPU overclocking, make sure the GPU fans are working. Make sure the PCI/e bus is not overclocked in BIOS (should be 100 MHz)

Make sure you do not have a conflicting high def sound source. IE update the motherboard sound driver or reset the bios to defaults. Turn off disable sound sources that don't have speakers attached to them.

for nvidia cards, make sure your ethernet driver is current or disable shadowplay.

 

[Sage Connel]

video card stopped responding and directx attempted to reset it. It still did not respond.
Directx tried to clean up the virutual memory the card was using and one of the memory addresses was bogus, this triggered the bugcheck.

I would look for sound driver conflicts first then hardware problems with the GPU,

Make sure your power is good to the video card, check the power connections, make sure it is not overheating, remove any GPU overclocking, make sure the GPU fans are working. Make sure the PCI/e bus is not overclocked in BIOS (should be 100 MHz)

Make sure you do not have a conflicting high def sound source. IE update the motherboard sound driver or reset the bios to defaults. Turn off disable sound sources that don't have speakers attached to them.

for nvidia cards, make sure your ethernet driver is current or disable shadowplay.

Thanks for your reply. I have a gigabyte r9 380.
SO I will try these issues and see if I have a problem anywhere.
What i do know is fans work fine, and I doubt my slot is overclocked ( never touched it to my knowledge)\
but ill work through these and see if its a hardware issue and i need a new card


shoulda bought an r9 390

 

[Sage Connel]

ok, so I decided to disable the amd audio drivers as I currently do not need them, I also switched the plugs on my gpu, although they were firmly connected, and my pcie bus speed was 100. so if it still happens I'm guessing that its hardware issue as everything else checks out fine. Thanks