0x139 BSOD with Ntoskrnl.exe

art1452

Prominent
Feb 11, 2018
6
0
510
Hello, I reinstalled my win10 and, today got a 0x139 BSOD. The PC wasn't under load, it was soon after logging in. Here's the BluScreenView log.
==================================================
Dump File : 021118-6187-01.dmp
Crash Time : 11.02.2018 18:13:25
Bug Check String :
Bug Check Code : 0x00000139
Parameter 1 : 00000000`00000002
Parameter 2 : ffffe081`be66f1f0
Parameter 3 : ffffe081`be66f148
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1756e0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.16299.192 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1756e0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021118-6187-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 16299
Dump File Size : 676 636
Dump File Time : 11.02.2018 18:13:59
==================================================
link for minidump: minidump
link for dxdiag: dxdiag
 


Thank you, found this one, but it's just that, well there's plenty to check, plus haven't added any hardware, don' have any devices with exclamation point, not even sure what else i should do with this. I mean I've stulmbled onto this one but it's kind of general and that's why i"ve posted here
 

Ok, deleted Asrock app charger and XfastRam.
As for the audio driver before installing the current one i've downloaded it from the Realtek website. It was the latest one if i'm not mistaken (did it like 10 days ago).
Yes, I've got alcohol 120 installed.
 


Do you mean the appcharger and the ram related app? Yes, I uninstalled them the moment you said I should.
As for the driver I'd delete this over and will get the one from the mobo's website (it's older though)

UPD: reinstalled the driver to the one that was on mobo's website..
 


I see, well got it installed now. The thing is that before the win reinstall I did have some crashes, mostly 0xA and 0x50. The thing was they were extremely random so it could happen two times a day not under load but then it'd work for two months without any crashes at all even under load.. So might take time till I get one this time, or that'd work and I wouldn't get that stuff (hopefully).