BSOD Critical_Structure_Corruption ntoskrnl.exe+14f9a0

Toggle sidebar Toggle sidebar
K

kona144

Reputable
Sep 7, 2015
4
0
4,510
After a couple of hours i get a BSOD and this is what it says with the program BlueScreenView:

==================================================
Dump File : 090415-24937-01.dmp
Crash Time : 4.9.2015 19:07:00
Bug Check String :
Bug Check Code : 0x00000109
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`0000010b
Parameter 4 : fffff801`2b167700
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14f9a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14f9a0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090415-24937-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9600
Dump File Size : 416.760
Dump File Time : 4.9.2015 19:08:13
==================================================

==================================================
Dump File : 090615-25843-01.dmp
Crash Time : 6.9.2015 0:07:00
Bug Check String :
Bug Check Code : 0x00000109
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`0000010b
Parameter 4 : fffff800`39d64700
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14f9a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14f9a0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090615-25843-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9600
Dump File Size : 401.160
Dump File Time : 6.9.2015 0:08:32
==================================================

Here is the minidump.

Here is the memory.dmp.

If you need anything else tell me!
 
Solution
J
anyway, the debugger thinks something corrupted memory, it could be RAM issues (run memtest86), virus, malware, rootkit.
bad drivers... the stack was messed up but right before screwed up it was running code from this driver:
Qualcomm Atheros AR9485WB-EG Wireless Network Adapter or ( AR9002WB-1NG)
\SystemRoot\system32\DRIVERS\athwbx.sys Mon Jul 15 00:29:50 2013
look here: https://www.atheros.cz/atheros-wireless-drivers.html or your vendor of the device for a update.

looks like you have various USB devices installed, one was having problems or the port was confused. Looked like a device went to sleep and later did not respond. but It could be a audio device that was not installed. You might consider putting some of your older...
Sort by date Sort by votes


I get to windows normally but after a couple of hours it BSOD-s and it restarts.
 
Upvote 0 Downvote
anyway, the debugger thinks something corrupted memory, it could be RAM issues (run memtest86), virus, malware, rootkit.
bad drivers... the stack was messed up but right before screwed up it was running code from this driver:
Qualcomm Atheros AR9485WB-EG Wireless Network Adapter or ( AR9002WB-1NG)
\SystemRoot\system32\DRIVERS\athwbx.sys Mon Jul 15 00:29:50 2013
look here: https://www.atheros.cz/atheros-wireless-drivers.html or your vendor of the device for a update.

looks like you have various USB devices installed, one was having problems or the port was confused. Looked like a device went to sleep and later did not respond. but It could be a audio device that was not installed. You might consider putting some of your older, slower USB devices on a USB 2 hub rather than the USB 3 hub.

- you have some special drivers that might depend on the smbus driver being installed, in order to read the sensors.


looks like plug and play to install a device driver for hdaudio and it failed to start and you have a failed install of second driver:

one driver is "PCI\VEN_8086&DEV_9C22&SUBSYS_189D1043&REV_04\3&11583659&0&FB"
I think that is a intel SMBus driver

the second is
InstancePath is "HDAUDIO\FUNC_01&VEN_8086&DEV_2807&SUBSYS_80860101&REV_1000\4&df5f2db&0&0001"
ServiceName is "HdAudAddService"

Intel Display High Definition Audio device of the HDMI port driver???


-------
looks like you have memory modules from different vendors
micron and Hynix/Hyundai you will want to run memtest86 to confirm your BIOS memory timings are good.

your network driver is old
\SystemRoot\system32\DRIVERS\Rt630x64.sys Mon Nov 25 23:32:54 2013
this should be the update:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

- looks like you have a pirate version of windows
- do you have any idea what R9BFXoScSu.exe is? it does not show up on a google search, not a good sign.
- looks like you have a activation server running on your copy of windows. SppExtComObj.Exe


machine info:
BIOS Version X751LK.201
BIOS Starting Address Segment f000
BIOS Release Date 08/19/2014
Manufacturer ASUSTeK COMPUTER INC.
Product X751LK
Version 1.0
Chassis Type Notebook




Processor Version Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 1700MHz

 
Upvote 0 Downvote
Solution


Thank you for the reply, I updated the drives as you said going to run memtest now il report back in a couple of hours.

After about 6 and a half hours, it ran about 46 test and no errors. So the ram isnt the problem il update if it happens again.

Edit:
It happened again, thanks for help but i think il do a clean install of win 10, maybe it will help or if you have any other ideas?
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom