BSOD -SYSTEM_SERVICE_EXCEPTION ntoskrnl.exe

Zionikk

Honorable
Jan 13, 2014
15
0
10,510
0
Hello there,

I've been getting quite a few BSOD lately, ever since upgrading to Windows 10. I assumed it was my GPU drivers, so I did a clean uninstall of my AMD drivers and reinstalled new ones. But that didn't seem to help with the frequent BSOD. I went ahead and made sure all of my other drivers were up to date (not sure if I got them all correctly).

But I still keep getting the crashes and I can't seem to figure out what's causing them.

I'll post my two latest minidumps in case anyone is willing to look them over for me and help me get to the bottom of this.

Crash Dumps

Thanks in advance!
 

Zionikk

Honorable
Jan 13, 2014
15
0
10,510
0


I should have mentioned that I'm running a clean install. Thanks though!
 
you might also consider:
update the BIOS to current version dated 2015-06-15 version 13.6
your bios is version 13.5 dated 9/17/2013

but do update the audio driver to avoid problems with windows 10 and your graphics support.
http://us.msi.com/support/mb/990FXA-GD80.html#down-driver&Win10 64


your system was up 5 days 11 hours.
first bugcheck was a bad memory address passed to the kernel.

Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver
remove \SystemRoot\System32\drivers\ScpVBus.sys Sun May 05 14:31:26 2013
(it corrupts memory)
(systemroot =c:\windows by default)

use this method to remove the driver:https://technet.microsoft.com/en-us/library/cc730875.aspx
other methods tend to leave the driver installed and you just continue to get memory corruptions.



machine info:
BIOS Version V13.5
BIOS Release Date 09/17/2013

Manufacturer MSI
Product Name MS-7640
Version 2.2
Product 990FXA-GD80 (MS-7640)
Processor Version AMD FX(tm)-8350 Eight-Core Processor
Processor Voltage 8dh - 1.3V
External Clock 200MHz
Max Speed 4000MHz
Current Speed 4000MHz


 

Zionikk

Honorable
Jan 13, 2014
15
0
10,510
0


Thanks John,

I've went ahead and updated my bios, and removed ScpVBus.sys using the method that you recommended.

I will leave a follow up if I happen to get another crash.
 

Zionikk

Honorable
Jan 13, 2014
15
0
10,510
0
Unfortunately, I experienced another crash. This time it's a bit different.

It's telling me that it was caused by dxgkrnl.sys. I have no idea what this is.

Here is what I was able to find in the minidump

SYSTEM_VERSION: 2.2

BIOS_DATE: 09/17/2013

BASEBOARD_PRODUCT: 990FXA-GD80 (MS-7640)

BASEBOARD_VERSION: 2.2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80081eefca2

BUGCHECK_P3: ffffd001afd85dc8

BUGCHECK_P4: ffffd001afd855e0

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

FAULTING_IP:
nt!KxWaitForLockOwnerShipWithIrql+12
fffff800`81eefca2 48890a mov qword ptr [rdx],rcx

EXCEPTION_RECORD: ffffd001afd85dc8 -- (.exr 0xffffd001afd85dc8)
ExceptionAddress: fffff80081eefca2 (nt!KxWaitForLockOwnerShipWithIrql+0x0000000000000012)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: ffffd001afd855e0 -- (.cxr 0xffffd001afd855e0)
rax=0000000000000000 rbx=ffffe0013cf916f0 rcx=ffffd001afd86050
rdx=2880000000000000 rsi=ffffe0013cff8840 rdi=ffffd001afd86050
rip=fffff80081eefca2 rsp=ffffd001afd86000 rbp=ffffd001afd86090
r8=ffffd001afd860c0 r9=ffffd001afd86180 r10=0000000000000000
r11=ffffd001afd86000 r12=0000000020180000 r13=ffffe0013cf8f840
r14=0000000000000001 r15=0000000000000000
iopl=0 nv up di ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010082
nt!KxWaitForLockOwnerShipWithIrql+0x12:
fffff800`81eefca2 48890a mov qword ptr [rdx],rcx ds:002b:28800000`00000000=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: fa0

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

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

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: fffff800821df500: Unable to get MiVisibleState
ffffffffffffffff

FOLLOWUP_IP:
dxgkrnl!DXGADAPTER::AcquireDdiSync+80
fffff800`799a35c0 488b5c2448 mov rbx,qword ptr [rsp+48h]

BUGCHECK_STR: AV

ANALYSIS_VERSION: 10.0.10240.9 amd64fre

LAST_CONTROL_TRANSFER: from fffff80081e6da5f to fffff80081eefca2

STACK_TEXT:
ffffd001`afd86000 fffff800`81e6da5f : ffffe001`3cf916f0 00000000`20000000 ffffc000`4ad755b0 fffff800`7d9f40e2 : nt!KxWaitForLockOwnerShipWithIrql+0x12
ffffd001`afd86030 fffff800`799a35c0 : 00000001`00000002 ffffe001`3cf8a010 00000000`00000000 004605b9`00000000 : nt!ExAcquireResourceSharedLite+0x42f
ffffd001`afd860c0 fffff800`79a0d080 : 00000000`00000000 ffffc000`4ad755b0 00000000`00020180 fffff800`7d9ee7bf : dxgkrnl!DXGADAPTER::AcquireDdiSync+0x80
ffffd001`afd86100 fffff800`7d9dd9d4 : ffffd001`afd86330 00000000`00000000 ffffe001`3d04e000 00000000`00000180 : dxgkrnl!ADAPTER_RENDER::DdiBuildPagingBuffer+0x40
ffffd001`afd86140 fffff800`7d99ee7e : ffffc000`4ad755b0 00000000`00000000 00000000`20180000 ffffc000`57dac700 : dxgmms2!VIDMM_GLOBAL::FlushGpuVaTlb+0xcc
ffffd001`afd862f0 fffff800`7d9eda12 : 00000000`00000000 ffffd001`afd86450 00000000`00000000 00000000`00080000 : dxgmms2!CVirtualAddressAllocator::FlushGpuVaTlb+0x8e
ffffd001`afd86350 fffff800`7d9f03c1 : 00000000`00000001 ffffc000`4b7fb100 00000000`00000000 fffff800`00000005 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x632
ffffd001`afd864a0 fffff800`7d9f413c : ffffc000`4ad755b0 ffffc000`5b92a6a0 ffffc000`4b7fb100 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetDriverUpdateAddress+0x20d
ffffd001`afd86560 fffff800`7d9f3f3e : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc000`4b805280 : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTableInvalidate+0x3c
ffffd001`afd86620 fffff800`7d9f3a65 : ffffc000`4b830140 ffffd001`afd86780 00000000`00000030 ffffe001`4d33dc10 : dxgmms2!VIDMM_PAGE_TABLE::UncommitVirtualAddressRange+0xe2
ffffd001`afd86670 fffff800`7d9f36b4 : 00000000`00000000 00000000`00000000 ffffd001`afd86890 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::UncommitVirtualAddressRange+0x349
ffffd001`afd86820 fffff800`7d9e3ee1 : 0004f308`a1feaa7b ffffc000`5afdab80 00000000`00000000 fffff800`7d9b1001 : dxgmms2!CVirtualAddressAllocator::UncommitVirtualAddressRange+0x78
ffffd001`afd86890 fffff800`7d9e3e33 : 00000000`00000000 ffffc000`5afdab80 ffffc000`5afdab01 fffff800`7d996e82 : dxgmms2!VIDMM_GLOBAL::UncommitVirtualAddressRangeSystemCommand+0x95
ffffd001`afd868c0 fffff800`7d9efb23 : 00000000`00000079 ffffc000`4b805280 ffffc000`5afdab98 ffffe001`3d0419a0 : dxgmms2!VIDMM_GLOBAL::UncommitVirtualAddressRange+0x77
ffffd001`afd86940 fffff800`7d9cbb09 : 00000000`00000079 ffffd001`afd86a31 ffffc000`4ad65170 fffff800`81ea9fac : dxgmms2!CVirtualAddressAllocator::FreeAllocMappedVaRangeList+0x4f
ffffd001`afd869a0 fffff800`7d9c917d : ffffc000`4ad65488 fffff800`7d9c5217 ffffc000`4ad65140 ffffc000`4ad65488 : dxgmms2!VIDMM_GLOBAL::processSystemCommand+0x569
ffffd001`afd86a90 fffff800`7d9c8907 : ffffc000`4ad65140 ffffd001`afd86b99 ffffd001`afd86b99 ffffc000`4ad6ede0 : dxgmms2!VIDMM_WORKER_THREAD::SubmitPacket+0x95
ffffd001`afd86af0 fffff800`81f01e88 : ffffe001`38893000 ffffd001`afd86c00 ffffd001`ad51c100 fffff800`81f6e200 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x36b
ffffd001`afd86c00 fffff800`81f6e326 : ffffd001`ad51c180 ffffe001`3cff8840 ffffd001`ad528cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd001`afd86c60 00000000`00000000 : ffffd001`afd87000 ffffd001`afd81000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgkrnl!DXGADAPTER::AcquireDdiSync+80

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 55bebfed

IMAGE_VERSION: 10.0.10240.16425

STACK_COMMAND: .cxr 0xffffd001afd855e0 ; kb

BUCKET_ID_FUNC_OFFSET: 80

FAILURE_BUCKET_ID: AV_dxgkrnl!DXGADAPTER::AcquireDdiSync

BUCKET_ID: AV_dxgkrnl!DXGADAPTER::AcquireDdiSync

PRIMARY_PROBLEM_CLASS: AV_dxgkrnl!DXGADAPTER::AcquireDdiSync

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_dxgkrnl!dxgadapter::acquireddisync

FAILURE_ID_HASH: {e959056c-310a-a834-6a5d-9e6fc7762193}

Followup: MachineOwner
---------
Here is a link to the MiniDump

Any help is greatly appreciated! Thanks
 
the bugcheck was in directx.
you should remove your overclocking driver
C:\Program Files\AMD\ATI.ACE\Fuel\amd64\AODDriver2.sys Tue Feb 11 03:06:52 2014

this driver is still installed. try and delete it directly after you have removed the setup from the driverstore.
c:\windows\System32\drivers\ScpVBus.sys Sun May 05 14:31:26 2013
 

Zionikk

Honorable
Jan 13, 2014
15
0
10,510
0


Thanks for your continued support.

But when I try to remove both of these drivers it won't let me because it says that they are being used in another program. I tried stopping all processes and services that might be related to each driver but it still won't allow me to delete them.
 
run an uninstaller for the program or boot into safe mode and delete the files if you have already removed them from the driver store.



 

Zionikk

Honorable
Jan 13, 2014
15
0
10,510
0
It's been awhile since I left an update.

After everything I tried, the BSODs continued to happen (mainly when playing games). So I went a head and did a clean install of Windows 10.

The computer ran fine for a awhile until I started playing games again, and now it seems I can't play any games without it crashing before I'm ready to finish.

I have two new dumps that I can post:Dumps

I did my best to check my dump files myself, but I have no idea what I am doing. I'm assuming it's memory corruption from a faulty stick or a bad driver. I plan on running MemTest86 over night to be sure my memory is good.

But in the mean time, can anyone help me pinpoint what driver might be causing the crash?

Thank you so much!
 
second bugcheck was a bad memory address again, this time you have underclocked ram, but have a overclock driver installed. Looks likes some older drivers have bee installed on top of a generic windows 10 install.

smart card reader see http://www.sysnative.com/drivers/driver.php?id=GKUPRO2D.sys
SystemRoot\system32\DRIVERS\GKUPRO2D.sys Mon Oct 29 06:10:10 2012
overclock driver:
C:\Program Files\AMD\ATI.ACE\Fuel\amd64\AODDriver2.sys Tue Feb 11 03:06:52 2014

old audio driver?
\SystemRoot\system32\drivers\MBfilt64.sys Thu Jul 30 20:40:32 2009

you will want to remove these drivers and install the updated windows 10 audio driver for your motherboard:
http://us.msi.com/support/mb/990FXA-GD80.html#down-driver&Win10 64


-----------
setup your memory timings to the correct specs of your memory modules, or reset the BIOS to defaults and see if it detects it correctly.
Actually confirm the values in BIOS, then boot memtest86 to confirm they work as expected.
------------
first bugcheck was caused by a bad memory contents.
BIOS reports your memory is F3-2133C9-8GXH 8gb modules but it reports it is running at 667MHz
you should confirm your memory timings and voltage in BIOS

i expect your memory is this one:
http://www.gskill.com/en/product/f3-2133c9d-16gxh
speed 2133MHz, 9-11-11-31-2n at 1.6v
be sure you make the bios has the correct timing and voltage. Also not the 2n command timing, it is called 2T command timings on some bios versions but it means this memory requires 2 clock states to properly set up the memory addressing commands. Most BIOS versions default to 1 Clock state so be sure to confirm your timings in the BIOS or you will get "random" failures in your memory addressing.
 

Zionikk

Honorable
Jan 13, 2014
15
0
10,510
0


Thanks for the reply John. That is the correct memory that I am using.

The ram voltage is currently set to 1.65V. I actually just changed it the other day, because I forgot I reset my BIOS to default and it was no longer getting enough power.

I'll have to double check my timings, but I think they're similar to what you posted. I am going to change them to 9-11-11-31 2T. Would those be the correct timings?

Also, after reading your reply I went ahead and deleted my overclocking driver in safe-mode so I don't think that should be a problem anymore. But the first thing I did after re-installing Windows was update my audio drivers from the MSI site. Which makes me think it couldn't be an outdate audio driver.

UPDATE:

Here is a photo of my current memory timings. Is there anything you recommend I change? Also, I moved the voltage down from 1.65V to 1.605V.


Extra: CPU-Z readings
 
you might also want to see what chrome extensions are running on your machine. Maybe disable them.
you might also pick up the network driver update from:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

it is 4 months more current.

install this:
http://us.msi.com/support/mb/990FXA-GD80.html#down-driver&Win10 64
( looks like you may have already installed it)

remove this:
http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
\SystemRoot\system32\drivers\MBfilt64.sys Thu Jul 30 20:40:32 2009

you have verifier turned on but your memory dump type is a minidump so the debug info is stripped out of the memory dump.
you need to change your memory dump type to kernel memory dump to provide the debug info.
https://www.sophos.com/en-us/support/knowledgebase/111474.aspx
(select kernel memory dump, the default location will change to c:\windows\memory.dmp file

guessing your problem is due to the audio drivers above.
 

fredknex

Distinguished
Dec 29, 2011
6
0
18,510
0
I also have a 990FXA-GD80 and FX-8350, and was getting random crashes since switching to Windows 10.
I turned off turbo core in the bios, and haven't had any crashes since.
 

ASK THE COMMUNITY

TRENDING THREADS