Hi there,

I've got a notebook it's a HP Pavilion G6 2240sh, running Windows 8.1 N professional 64bit. While i was running Win7, my bluetooth device was working correctly. Its a Ralink. There is a package in Windows Update which is a driver for it, but i could never install. (its downloaded, but set up is never begins)
My device is a Ralink RT3290 Bluetooth 01. There is a program on MediaTek's homesite, which is made for Win8.1, but causing BSoD-s all the time, when i would like to install. I searched so much drivers on HP's support, but every choices finished with BSoD and using a restore point. Do you have a driver made by microsoft and not Ralink? Please, help!

Generic Bluetooth:

USB\VID_0A12&PID_0001&REV_1958
USB\VID_0A12&PID_0001

Ralink Bluetooth PCIe adapters

PCI\VEN_1814&DEV_3298&SUBSYS_18EC103C&REV_00
PCI\VEN_1814&DEV_3298&SUBSYS_18EC103C
PCI\VEN_1814&DEV_3298&CC_0D1100
PCI\VEN_1814&DEV_3298&CC_0D11

USB\VID_148F&PID_3298&REV_0000
USB\VID_148F&PID_3298

• Edited by cdesa Thursday, January 23, 2014 12:47 AM

Hi

Your PC was DOS right?

This what I can find regarding latest driver

http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-125314-1&cc=us&dlc=en&lc=en&os=4132&product=5446899&sw_lang=

http://www.mediatek.com/_en/07_downloads/01_windows.php

Or you can send dump file for us to check.

You should check here or ask HP or ralink regarding compatibility.

• Edited by britishdhez Thursday, January 23, 2014 2:50 AM

We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.   We prefer at least 2 DMP files to spot trends and confirm the cause.
Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here If you have any questions about the procedure please ask

I've found just one .dmp file, rewrite box is checked.

https://www.dropbox.com/sh/ogabck0a7u2h1gw/AoZNFqs1Mk

Please excuse me, my system language is not english. :/

• Edited by qrrr Thursday, January 23, 2014 7:48 AM

Hi,

Here is the result:

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

Implicit thread is now ffffe000`007fa880

DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  ffffe000007fa880

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LOCK_ADDRESS:  fffff800e6143360 -- (!locks fffff800e6143360)

Resource @ nt!PiEngineLock (0xfffff800e6143360)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
	Lock address  : 0xfffff800e6143360
	Thread Count  : 0
	Thread address: 0x0000000000000000
	Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff800e5f1890e to fffff800e5fc4b36

STACK_TEXT:  
ffffd000`21dfa480 fffff800`e5f1890e : ffffd000`210b0180 ffffe000`007fa880 00000000`fffffffe 00000000`fffffffe : nt!KiSwapContext+0x76
ffffd000`21dfa5c0 fffff800`e5f183a7 : 00000000`00000000 fffff800`00000000 00000000`00000000 fffff800`e5f30000 : nt!KiSwapThread+0x14e
ffffd000`21dfa660 fffff800`e5eaf9a8 : ffffe000`02343d30 ffffe000`007fa9c0 ffffe000`06c25a30 ffffc000`0037f910 : nt!KiCommitThreadWait+0x127
ffffd000`21dfa6c0 fffff800`e5f7bb7c : fffff800`e61431e8 fffff800`00000000 fffff800`e6141d00 00000000`00000000 : nt!KeWaitForSingleObject+0x248
ffffd000`21dfa760 fffff800`e62c87a1 : 00000000`00000000 ffffe000`02343d30 fffff800`e6141d00 00000000`00000000 : nt!PnpDeviceCompletionQueueGetCompletedRequest+0x24
ffffd000`21dfa7a0 fffff800`e62c858c : ffffe000`02343d30 ffffd000`21dfa8d0 00000000`00000001 00000000`00000000 : nt!PnpDeviceCompletionProcessCompletedRequests+0x6d
ffffd000`21dfa7d0 fffff800`e62fdfbf : ffffe000`02343d30 00000000`00000001 00000000`00000000 fffff800`e6244542 : nt!PipProcessDevNodeTree+0x480
ffffd000`21dfaa50 fffff800`e5f662f3 : 00000001`00000003 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PiRestartDevice+0xaf
ffffd000`21dfaaa0 fffff800`e5f151b9 : fffff800`e5f65f50 ffffd000`21dfabd0 00000000`00000000 ffffe000`007fa880 : nt!PnpDeviceActionWorker+0x3a3
ffffd000`21dfab50 fffff800`e5f012e4 : 00000000`00000000 ffffe000`007fa880 ffffe000`007fa880 ffffe000`00308900 : nt!ExpWorkerThread+0x2b5
ffffd000`21dfac00 fffff800`e5fc82c6 : ffffd000`20fac180 ffffe000`007fa880 ffffd000`20fb8340 00000000`ffffffff : nt!PspSystemThreadStartup+0x58
ffffd000`21dfac60 00000000`00000000 : ffffd000`21dfb000 ffffd000`21df5000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .thread 0xffffe000007fa880 ; kb

FOLLOWUP_IP: 
nt!KiSwapContext+76
fffff800`e5fc4b36 488d8c2400010000 lea     rcx,[rsp+100h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiSwapContext+76

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  52718d9c

IMAGE_VERSION:  6.3.9600.16452

BUCKET_ID_FUNC_OFFSET:  76

FAILURE_BUCKET_ID:  0x9F_4_nt!KiSwapContext

BUCKET_ID:  0x9F_4_nt!KiSwapContext

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_4_nt!kiswapcontext

FAILURE_ID_HASH:  {e8e4ff91-4633-fc99-d928-aa21c06c4344}

Please check this article and try the driver verifier tool to check your bluetooth driver.

Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE
http://msdn.microsoft.com/en-us/library/windows/hardware/ff559329(v=vs.85).aspx

here

http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-119299-1&cc=us&dlc=en&lc=en&os=4132&product=5319684&sw_lang=

• Edited by britishdhez 9 hours 45 minutes ago

Hi britishdhez,

ESET drivers, in particular the edovmon.sys, may be involved in the crash as reported here.

Make sure the latest version of the ESET software is installed as there have been some recent fixes such as reported here.

 

Hi

I don't know why is related to ESET. Did you check dump files? Or maybe I missed something here? Please let me know

I Checked using debugger, and found what exactly same with Kate mention, its driver windows 8 fault

• Edited by britishdhez 1 hour 55 minutes ago

If you don't want to use driver verifier, please contact HP and ask for the latest update driver from their side. I try to help with link, but seems that link not work well

http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?lang=en&cc=US&swItem=vc_111438_1

• Edited by britishdhez 1 hour 49 minutes ago