[SOLVED] [Win 10 x64] BSOD Crash 0x7f (8)

kvizerad

Member
Joined
Aug 8, 2017
Posts
18
Hi everyone!

I browsed your forum for a while and thought that possibly you can help me to specify the sourse of BSOD recently occured at my PC.
My guess - it has something to do with Microsoft USB driver, but I'm not quite sure. I'm bit scared to take any further actions unill I be 100% sure.

Here is my spec:

Operating system: Windows 10 Home (Build 15063), 64-bit
Motherboard: ASUS ROG MAXIMUS IX FORMULA
Monitor Name: Generic PnP Monitor
Monitor Model: ASUS VX239
CPU: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 CPUs), ~4.2GHz (not overlocked)
Memory: 32768MB RAM Corsair Vengeance LPX (4x8Gb)
Hard disk 1: 240Gb SSD Corsair Force LS Series
Hard disk 2: 4Tb SATA-III HGST (Hitachi) Ultrastar 7K6000
Graphics: NVIDIA GeForce GTX 1070
Sound card: Realtek Digital Output (Realtek High Definition Audio)
Power Supply: 750W Corsair RM750i

External devices:
USB3 Hub (with additional power supply)
WD My Passpoet External drives 2Tb x 4


Sorry for a bit rought English - it isn't my first language.
 

Attachments

The problem is due to your Atheros Bluetooth device. See if there are any driver updates for the device.

btfilter.sys Tue Aug 30 23:04:48 2016 (57C66570)
Atheros Bluetooth Driver Official site: Drivers | Qualcomm
Unofficial site: http://www.atheros.cz
http://www.carrona.org/drivers/driver.php?id=btfilter.sys





I also note several other devices that have outdated drivers:

lvuvc64.sys Mon Oct 22 20:12:08 2012 (5085FCF8)
Logitech USB Video Class Driver (WebCam) Logitech Support + Downloads
http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys

ISODrv64.sys Wed Nov 20 18:22:28 2013 (528D6054)
ISO CD-ROM Device Driver - ISODrive http://www.ezbsystems.com/download.htm
http://www.carrona.org/drivers/driver.php?id=ISODrv64.sys

IOMap64.sys Wed Oct 22 18:52:12 2014 (5448513C)
ASUS Kernel Mode Driver ?Asus Smart Doctor/iTracker 2 Asus GPU Tweak and GPU Tweak Streaming from this link: http://www.eightforums.com/bsod-cra...ts-driver_power_state_failure.html#post388083 ) http://support.asus.com/ServiceHome.aspx?SLanguage=en
http://www.carrona.org/drivers/driver.php?id=IOMap64.sys

ICCWDT.sys Sun Sep 20 01:59:19 2015 (55FE6757)
IIntel(R) Watchdog Timer Driver http://downloadcenter.intel.com/
http://www.carrona.org/drivers/driver.php?id=ICCWDT.sys

Read More:
 
So I've updated as many drivers as I could (Atheros Wireless Driver, Intel Ethernet Connection Driver etc.). But thing is that I can't update specificly Bluetooth driver (and btfilter.sys as it's essential part) - Qualcomm does not offer support or drivers to end consumers (OEM only) and http://www.atheros.cz isn't working anymore. I don't quite understand why this driver matters on my PC - ASUS FORMULA IX motherboard haven't got any integrated bluetooth ports.
 
Code:
[COLOR=#ff0000]BugCheck 7F[/COLOR], {[COLOR=#0000cd]8[/COLOR], fffff8030ba22e70, fffff8030ba0afc0, fffff80308f08657}

Probably caused by : [COLOR=#ff0000]btfilter.sys[/COLOR] ( btfilter+1467a )

The first parameter indicates the type of unhandled exception, and although, the other parameters are undocumented by the debugger, they reveal some interesting details:

Code:
0: kd> [COLOR=#008000]r $bug_param2[/COLOR]
$bug_param2=[COLOR=#ff0000]fffff8030ba22e70[/COLOR]

The second parameter indicates the address of the trap frame.

Code:
0: kd> [COLOR=#008000]r $bug_param3[/COLOR]
Last set context:
$bug_param3=[COLOR=#ff0000]fffff8030ba0afc0[/COLOR]

The third parameter indicates the stack frame pointer of the faulting instruction.

Code:
0: kd> [COLOR=#008000]r $bug_param4[/COLOR]
Last set context:
$bug_param4=[COLOR=#ff0000]fffff80308f08657[/COLOR]

The fourth parameter indicates the address of the faulting instruction.

Let's dump the trap frame, and the stack which was saved before the crash:

Code:
0: kd> [COLOR=#008000]knL[/COLOR]
  *** Stack trace for last set context - .thread/.cxr resets it
 # Child-SP          RetAddr           Call Site
00 fffff803`0ba0afc0 fffff803`08d9a831 [COLOR=#ff0000]nt!ExAllocatePoolWithTag+0x2b7[/COLOR] << We crash here!
01 fffff803`0ba0b0b0 fffff801`55a7c22e nt!IoSetCompletionRoutineEx+0x51
02 fffff803`0ba0b0f0 fffff801`55a9e56d Wdf01000!FxIrp::SetCompletionRoutineEx+0x36
03 (Inline Function) --------`-------- Wdf01000!FxDevice::_AcquireOptinRemoveLock+0x47ad9
04 fffff803`0ba0b140 fffff801`55ba1262 Wdf01000!FxDevice::DispatchWithLock+0x47b2d
05 fffff803`0ba0b230 fffff801`5c27467a ACPI!ACPIDispatchIrp+0x1c2
06 fffff803`0ba0b2b0 00000000`00000007 [COLOR=#ff0000]btfilter+0x1467a[/COLOR] << Our faulty driver
07 fffff803`0ba0b2b8 ffff9886`7a653f68 0x7
08 fffff803`0ba0b2c0 ffff9886`7d58ade0 0xffff9886`7a653f68
09 fffff803`0ba0b2c8 ffff9886`7a586180 0xffff9886`7d58ade0
0a fffff803`0ba0b2d0 ffff9886`00000020 0xffff9886`7a586180
0b fffff803`0ba0b2d8 00000000`00000000 0xffff9886`00000020

It appears that a pool allocation was attempted to be made, however, once the stack frame was pushed onto the call stack, the stack overran and the system crashed.

I've examined the pool allocation and it appears it for the I/O Manager, which makes sense since the Atheros Bluetooth driver was making calls in relation to I/O.

Code:
0: kd> [COLOR=#008000]!pooltag IoUs[/COLOR]
Pooltag IoUs
Description: I/O SubSystem completion Context Allocation
Driver!Module: nt!io

The stack consumption of each frame can be found using the !stackusage extension:

Code:
[code]0: kd> [COLOR=#008000]!stackusage[/COLOR]
Stack Usage By Function
=================================================================================

      Size     Count  Module
0x00000140         1  nt!KiBugCheckDispatch
0x000000F0         1  Wdf01000!FxDevice::DispatchWithLock
0x000000F0         1  nt!ExAllocatePoolWithTag
0x00000080         1  ACPI!ACPIDispatchIrp
0x00000050         1  Wdf01000!FxIrp::SetCompletionRoutineEx
0x00000040         1  nt!IoSetCompletionRoutineEx
0x00000008         1  btfilter
0x00000008         2  nt!KeBugCheckEx

Total Size: 0x00000440


Stack Usage By Module
=================================================================================

      Size     Count  Module
0x00000278         5  [COLOR=#ff0000]nt[/COLOR]
0x00000140         2  Wdf01000
0x00000080         1  ACPI
0x00000008         1  [COLOR=#ff0000]btfilter[/COLOR]

The nt! module will have the largest stack consumption due to the number of calls which are made by other drivers.

Please update the driver as suggested in the above post.
 
Hi, x BlueRobot! So, I finally managed to update my bluetooth driver - I've found needed distributives on ASUS site (I guest it is good to remember for all owners of ASUS motherbords that most recent drivers can be found only on their site). I tested my PC for four days - no BSOD so far. I guess we may cosider that problem solved.

Thanks again to everyone on that forum. Your analysis and advices were realy helpful!
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top