[SOLVED] BSOD - switching between the game and desktop.

A

Arinnis

Member
Joined
Feb 11, 2014
Posts
11
Hello.

I have been having a problem recently, BSOD when I'm playing World of Warcraft particulary and switching between the game and desktop. I was having it for like 3 days then I formated system and used fabric image of windows from recovery partition. After the fresh Windows booted I wanted to install new nVidia drivers and first BSOD after the format occured. Now it happens occasionally when I'm playing World of Warcraft and switch between the game and desktop as I said but not everytime. It's unpredictable whether it will happen or not. Everything is fine as long as I don't jump between WoW and desktop. I can play game for the whole time and everything is OK, however, man have occasionally check browser, facebook etc. and it's very annoying sometimes.

So far I tried:
-fabric reboot (recovery partition)
-changing nVidia drivers (now I have the beta ones the lastest)
-cleaning my laptop as I thought it might be caused by overheating (thermal grease changed)
-chkdsk - everything is fine
-memtest86 - 9 passes 0 errors

I forgot to mention specification, it's Laptop Dell Inspiron Q15R (N5110):
Windows 7 x64 Home Premium
Processor: i3 -2310m
Graphics: nVidia 525m
4GB RAM Samsung

View attachment Minidumps.zip

I enclose screened minidumps and I'm sorry for lexical/grammatical mistakes. I'm not a native speaker.

If anything can be done to solve this problem please help me, thank you.
 
I'm sorry, my bad.

Enclosing those files.

· OS - Windows 8.1, 8, 7, Vista ? - Windows 7
· x86 (32-bit) or x64 ? - x64
· What was original installed OS on system? - Windows 7 Home Premium x64
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? - pre-installed with recovery partition.
· Age of system (hardware) - about 2 years
· Age of OS installation - have you re-installed the OS? - fabric reinstall about week ago.

· CPU - i3 - 2310m
· Video Card nVidia 525m
· MotherBoard - Dell Inc. model: 0FXK2Y, A11
· Power Supply - brand & wattage (if laptop, skip this one)

· System Manufacturer - Dell
· Exact model number (if laptop, check label on bottom) Inspiron Q15R (N5110)

· Laptop or Desktop? - Laptop



If anything else should be provided please tell me, thank you Patrick.
 

Attachments

Thanks a lot!

We have two consistent bug checks:

PAGE_FAULT_IN_NONPAGED_AREA (50)

This indicates that invalid system memory has been referenced.

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

If we take a look at the call stack:

Code: 
1: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0a2b77c8 fffff800`03292bf6 : 00000000`00000050 fffff900`c0639770 00000000`00000000 fffff880`0a2b7920 : nt!KeBugCheckEx
fffff880`0a2b77d0 fffff800`0327466e : 00000000`00000000 fffff900`c0639770 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x218b
fffff880`0a2b7920 fffff960`00676d15 : 00000000`000006d0 00000000`00000000 00000000`3e120a12 00000000`00000020 : nt!KiPageFault+0x16e (TrapFrame @ fffff880`0a2b7920)
fffff880`0a2b7ab0 fffff960`00297ec9 : 00000000`00000000 fffff900`c21dcb20 00000000`037ffaf0 00000040`000001c7 : [COLOR=#ff0000][I][B]cdd!DrvAssociateSharedSurface+0x51[/B][/I][/COLOR]
fffff880`0a2b7b10 fffff960`002bb05d : 00000000`00000001 fffff880`0a2b7c60 00000000`037ffaf0 00000000`00007328 : win32k!GreSetRedirectionSurfaceSignaling+0x125
fffff880`0a2b7b60 fffff800`032757d3 : fffffa80`0909d740 fffffa80`090941e0 fffffa80`09117550 fffffa80`090941e0 : win32k!NtGdiHLSurfSetInformation+0x209
fffff880`0a2b7be0 000007fe`fd314efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0a2b7be0)
00000000`037ffa28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd314efa

We have a cdd.dll routine call (Canonical Display Driver).

SYSTEM_SERVICE_EXCEPTION (3b)

This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

If we take a look at the call stack:

Code: 
0: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0a09a7e8 fffff800`03269ae9 : 00000000`0000003b 00000000`c0000005 fffff800`032328ae fffff880`0a09b0b0 : nt!KeBugCheckEx
fffff880`0a09a7f0 fffff800`0326943c : fffff880`0a09b848 fffff880`0a09b0b0 00000000`00000000 fffff960`0033d0f0 : nt!KiBugCheckDispatch+0x69
fffff880`0a09a930 fffff800`0329523d : fffff960`0038e0f0 00000000`00000000 fffff960`000a0000 fffff880`0a09b848 : nt!KiSystemServiceHandler+0x7c
fffff880`0a09a970 fffff800`0329d2b0 : fffff800`033bbd24 fffff880`0a09a9e8 fffff880`0a09b848 fffff800`03204000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0a09a9a0 fffff800`032ab73f : fffff880`0a09b848 fffff880`0a09b0b0 fffff880`00000000 fffffa80`090c6060 : nt!RtlDispatchException+0x410
fffff880`0a09b080 fffff800`03269bc2 : fffff880`0a09b848 00000000`00000000 fffff880`0a09b8f0 fffff900`c2455740 : nt!KiDispatchException+0x16f
fffff880`0a09b710 fffff800`0326873a : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0a09b8f0 fffff800`032328ae : fffff880`0a09bb00 fffff880`04319906 fffff900`c00c0010 00000000`09120dfd : nt!KiPageFault+0x23a (TrapFrame @ fffff880`0a09b8f0)
fffff880`0a09ba80 fffff960`00796d3f : 00000000`00000000 00000000`00000000 00000000`09120d12 00000000`00000020 : nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x26
fffff880`0a09bab0 fffff960`00277ec9 : 00000000`00000000 fffff900`c245a9f0 00000000`038ffa30 00000040`000001c7 : [COLOR=#ff0000][I][B]cdd!DrvAssociateSharedSurface+0x7b[/B][/I][/COLOR]
fffff880`0a09bb10 00000000`00000000 : fffff900`c245a9f0 00000000`038ffa30 00000040`000001c7 fffffa80`00000000 : win32k+0x1d7ec9

We have the same routine being called here as well.

Code: 
0: kd> ln fffff800032328ae
(fffff800`03232888)   nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x26

It appears the exception occurred in ExEnterCriticalRegionAndAcquireFastMutexUnsafe.

----------------

1. Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

2. Run Memtest for NO LESS than ~8 passes (several hours):

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

Regards,

Patrick
 
Hi again.

Sorry for not responding.

I tried memtest86 and had 9 passes and 0 errors again. I installed earlier version of nVidia drivers and it's ok so far. I'll give further information after few days or when another BSOD appear.

Thank you greatly so far Patrick.

With regard.
 
Hi again.

Unfortunately my problem returned. I tried again to reinstall graphic drivers and once BSOD occured, the reason was cdd.dll. Then I tried other drivers once more and again BSOD showed up connected with win32k.sys if I remember. Both drivers were okay back in the days when they were the latest. If anyone know what shall I do, please give me and advice.

With regard.
 
We'll need to see the latest DMP files to see what the next step should be.

Regards,

Patrick
 
Hello Patrick.

Okay, I hope that you meant that I must to use software from page once again and upload it here. So I am doing it now.

Hopefully that will help.

I will try to respond asap.

Thank you once more Patrick.
 

Attachments

Correct, you did just fine. Thanks!

Both of the dumps are still of the *3B bug check as we've seen. At this point, I am concerned of an internal hardware issue (with the laptop's video card). You mentioned you've tried earlier drivers, and the latest, and both worked fine at the time of being the latest. Did you happen to notice if a beta driver was available? If not, given we've passed Memtest, used the recovery partition, etc, this is an internal issue.

Update to Service Pack 1 ASAP: Learn how to install Windows 7 Service Pack 1 (SP1)

Regards,

Patrick
 
So I was trying to install Service Pack through Windows Updater. Everything was fine and about 120 updates were installed and then one about service pack was to install and needed to reboot. After reboot it stopped at configuratin and wanted to close the system and presumably reboot. Unfortunately while closing unexpected BSOD appeard which really surprised me and didn't know what is going on. Well I turned on computer once again and Service Pack wasn't installed so I tried once again to update, however, it doesn't want to proceed. I've got something like 80072F78 error and I used "Troubleshooting Windows Updater" software from Microsoft but it didn't help. No idea what is going on now. I'm enclosing latest DMP and hope that will reveal something.

With regards.
 

Attachments

After few hours, somehow, I have no idea how, I was able to install Service Pack smoothly. That's preety strange to me...
 
If you crash again and the attached DMP is a *3B, it's likely an internal video hardware issue and I would go ahead and contact the manufacturer to discuss your options on repair, replacement, etc.

Regards,

Patrick
 
Hi again Patrick.

Well, this time I had different blue screen connected with DRIVER_POWER_STATE_FAILURE and the code 0x1000009f actually. No idea if it whether changes anything. I enclose lastest DMP.
 

Attachments

The attached DMP file is of the DRIVER_POWER_STATE_FAILURE (9f) bug check.

By default, this bug check indicates that the driver is in an inconsistent or invalid power state. However, because the 1st parameter = 0x4, this implies that a power IRP has failed to synchronize with the PnP Manager.

We might need a kernel-dump to debug this. Can you please set this up for all future dumps after this?

Creating a Kernel-Mode Dump File (Windows Debuggers)

-- I should note that kernel-dumps are large, and won't be able to be attached here directly. You'll need to upload them elsewhere (Onedrive, Dropbox, etc) and paste the link here.

The reason I bold and italicize might is because there's actually mention of a 3rd party driver in the call stack that may be causing this:

Code: 
0: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff880`033b5f30 fffff800`03274112 nt!KiSwapContext+0x7a
01 fffff880`033b6070 fffff800`03275c4f nt!KiCommitThreadWait+0x1d2
02 fffff880`033b6100 fffff880`02ce0706 nt!KeWaitForSingleObject+0x19f
03 fffff880`033b61a0 00000000`00000000 [COLOR=#ff0000][I][B]btmhsf+0x8706[/B][/I][/COLOR]

^^ Intel Proset Bluetooth HighSpeed Filter driver. Check Dell's website and be sure all of your Bluetooth drivers are up to date, and if not listed there, try Intel's auto-update directly: Intel® Driver Update Utility

Regards,

Patrick
 
It's my pleasure, really!

Thanks a bunch for the Kernel, let's take a look!

As said above, it's the same bug check *9F with an 0x4 1st parameter.
Code: 
0: kd> .bugcheck
Bugcheck code 0000009F
Arguments [COLOR=#ff0000][I][B]00000000`00000004[/B][/I][/COLOR] 00000000`00000258 fffffa80`039e0040 fffff800`00b9c4d0

If we take a look at the call stack:
Code: 
0: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff800`00b9c498 fffff800`032feeb6 nt!KeBugCheckEx
01 fffff800`00b9c4a0 fffff800`034ab2fc nt!PnpBugcheckPowerTimeout+0x76
02 fffff800`00b9c500 fffff800`03278ac6 nt!PopBuildDeviceNotifyListWatchdog+0x1c
03 fffff800`00b9c530 fffff800`03277dc6 nt!KiProcessTimerDpcTable+0x66
04 fffff800`00b9c5a0 fffff800`0327899e nt!KiProcessExpiredTimerList+0xc6
05 fffff800`00b9cbf0 fffff800`03278137 nt!KiTimerExpiration+0x1be
06 fffff800`00b9cc90 fffff800`0327519a nt!KiRetireDpcList+0x277
07 fffff800`00b9cd40 00000000`00000000 nt!KiIdleLoop+0x5a

Not really much info, just a few PnP routines that call into the bugcheck eventually. No driver in the stack, etc.

Let's run !locks to see what's going on:

Code: 
0: kd> !locks
**** DUMP OF ALL RESOURCE OBJECTS ****
KD: Scanning for held locks..

Resource @ nt!IopDeviceTreeLock (0xfffff8000346e560)    [COLOR=#ff0000][I][B]Shared 1 owning threads[/B][/I][/COLOR]
     Threads: [COLOR=#ff0000][I][B]fffffa80039e0040[/B][/I][/COLOR]-01<*> 
KD: Scanning for held locks.

Resource @ nt!PiEngineLock (0xfffff8000346e460)    Exclusively owned
    Contention Count = 10
    NumberOfExclusiveWaiters = 2
     Threads: fffffa80039e0040-01<*> 
     Threads Waiting On Exclusive Access:
              fffffa8007ea5b60       fffffa80039e1040       

KD: Scanning for held locks....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
15001 total locks, 2 locks currently held

The guilty one is usually always the one sharing and/or owning multiple threads.

Code: 
0: kd> !thread fffffa80039e0040
THREAD fffffa80039e0040  Cid 0004.0038  Teb: 0000000000000000 Win32Thread: 0000000000000000 WAIT: (Executive) KernelMode Non-Alertable
    fffffa8007f97968  NotificationEvent
IRP List:
    [COLOR=#ff0000][I][B]fffffa800782e440[/B][/I][/COLOR]: (0006,03e8) Flags: 00000000  Mdl: 00000000
Not impersonating
DeviceMap                 fffff8a000006090
Owning Process            fffffa80039ca5f0       Image:         System
Attached Process          N/A            Image:         N/A
Wait Start TickCount      62073          Ticks: 38462 (0:00:10:00.011)
Context Switch Count      972            IdealProcessor: 1  NoStackSwap
UserTime                  00:00:00.000
KernelTime                00:00:00.093
Win32 Start Address nt!ExpWorkerThread (0xfffff80003279b10)
Stack Init fffff880033b6d70 Current fffff880033b5ef0
Base fffff880033b7000 Limit fffff880033b1000 Call 0
Priority 15 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`033b5f30 fffff800`03274112 : fffffa80`039e0040 fffffa80`039e0040 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`033b6070 fffff800`03275c4f : 0000057f`f8080e08 00000000`00000000 fffffa80`00000000 fffff880`010f782e : nt!KiCommitThreadWait+0x1d2
fffff880`033b6100 fffff880`02ce0706 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`033b61a0 fffff880`02cd9e7a : 0000057f`f8073c48 fffffa80`07f97040 fffffa80`07f8c3d0 fffffa80`07f8c3d0 : [COLOR=#ff0000][I][B]btmhsf+0x8706[/B][/I][/COLOR]
fffff880`033b61e0 fffff880`010f385e : fffffa80`07f8c3b0 fffffa80`08b12750 00000000`00000005 fffffa80`07f8c3b0 : [COLOR=#ff0000][I][B]btmhsf+0x1e7a[/B][/I][/COLOR]
fffff880`033b6210 fffff880`010f3a74 : fffffa80`07f8c3b0 00000000`00000001 fffffa80`07f8c300 00000000`00000001 : Wdf01000!FxObject::DisposeChildrenWorker+0x2fa
fffff880`033b6290 fffff880`010f399b : fffffa80`07f8c3b0 00000000`00000000 fffffa80`07f8c301 fffff880`033b6398 : Wdf01000!FxObject::PerformDisposingDisposeChildrenLocked+0xbc
fffff880`033b6300 fffff880`010f3d9b : fffffa80`07f8c3b0 fffffa80`07f94d00 fffffa80`07f94d00 fffffa80`07f8c3b0 : Wdf01000!FxObject::PerformEarlyDisposeWorkerAndUnlock+0xfb
fffff880`033b6370 fffff880`011765f2 : fffffa80`07f94e60 fffffa80`07f94d30 fffffa80`07f94780 fffffa80`08aff020 : Wdf01000!FxObject::EarlyDispose+0x117
fffff880`033b63d0 fffff880`01175745 : 00000000`00000004 fffffa80`08afefc0 00000000`00000124 fffffa80`07f94780 : Wdf01000!FxPkgPnp::PnpEventRemovedCommonCode+0x1e2
fffff880`033b6430 fffff880`0111081d : 00000000`00000124 fffff880`033b64d0 00000000`00000136 fffffa80`07f94780 : Wdf01000!FxPkgFdo::PnpEventFdoRemovedOverload+0x9
fffff880`033b6460 fffff880`01111032 : 00000000`00001000 fffffa80`07f948a8 fffffa80`07f94780 fffffa80`07f94780 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a1
fffff880`033b6500 fffff880`01110cdd : 00000000`00000000 fffff880`033b65e0 fffffa80`07f94890 fffffa80`07f94780 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff880`033b6570 fffff880`01170e4c : 00000000`00000000 00000000`00000001 fffff880`033b66d0 fffff880`033b66e0 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x18d
fffff880`033b6610 fffff880`010f9ecf : fffffa80`0797c802 fffff880`033b66d0 00000000`00000000 fffffa80`0782e7e0 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0xb0
fffff880`033b6680 fffff880`010f19da : fffffa80`0782e440 fffffa80`0782e440 fffffa80`0782e440 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x18f
fffff880`033b66e0 fffff880`010f1aa6 : fffffa80`0782e440 fffffa80`07f97190 fffffa80`07f97040 fffffa80`07f97040 : Wdf01000!FxDevice::Dispatch+0x19a
fffff880`033b6720 fffff880`02da73ed : fffffa80`08b80190 00000000`00000000 fffffa80`08b80190 fffffa80`0782e440 : Wdf01000!FxDevice::DispatchWithLock+0xa6
fffff880`033b6760 fffff880`02da6a92 : fffffa80`08b80190 00000000`00000000 00000000`00000000 fffffa80`0782e440 : [COLOR=#ff0000][I][B]bthport!BthHandleRemoveDevice+0xc1[/B][/I][/COLOR]
fffff880`033b67c0 fffff880`02da6903 : fffffa80`0782e440 00000000`00000701 fffff880`02dbc8c0 00000000`00000000 : [COLOR=#ff0000][I][B]bthport!BthHandlePnp+0x136[/B][/I][/COLOR]
fffff880`033b6830 fffff800`034ceda5 : fffffa80`08b80040 00000000`c00000bb fffffa80`0782e440 fffffa80`0782e440 : [COLOR=#ff0000][I][B]bthport!BthDispatchPnp+0x73[/B][/I][/COLOR]
fffff880`033b6880 fffff800`03653481 : fffffa80`07e8c440 00000000`00000000 fffffa80`079b6980 00000000`00000801 : nt!IopSynchronousCall+0xc5
fffff880`033b68f0 fffff800`0336cde3 : fffff8a0`02899710 fffff8a0`02899710 00000000`00000000 00000000`00000000 : nt!IopRemoveDevice+0x101
fffff880`033b69b0 fffff800`03652fd4 : fffffa80`079b6980 00000000`00000000 00000000`00000002 fffffa80`06d0b050 : nt!PnpRemoveLockedDeviceNode+0x1a3
fffff880`033b6a00 fffff800`036530e0 : 00000000`00000000 fffff8a0`0a0d6c01 fffff8a0`0981fcb0 ffffeb07`7439c9e8 : nt!PnpDeleteLockedDeviceNode+0x44
fffff880`033b6a30 fffff800`036e3ac4 : 00000000`00000002 00000000`00000000 fffffa80`06d0c780 fffff8a0`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`033b6aa0 fffff800`036e411c : fffff880`00000000 fffffa80`07959c00 fffffa80`039e0000 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xc34
fffff880`033b6be0 fffff800`035ce888 : 00000000`00000000 fffffa80`07959c10 fffff8a0`0a7709e0 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`033b6c10 fffff800`03279c21 : fffff800`034ce88c fffff8a0`0a0d6c90 fffff800`0340f638 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x4f8db
fffff880`033b6c70 fffff800`03506ff2 : 00253417`002533ec fffffa80`039e0040 00000000`00000080 fffffa80`039ca5f0 : nt!ExpWorkerThread+0x111
fffff880`033b6d00 fffff800`03249a06 : fffff880`031d3180 fffffa80`039e0040 fffff880`031ddfc0 005e63d8`002538cf : nt!PspSystemThreadStartup+0x5a
fffff880`033b6d40 00000000`00000000 : fffff880`033b7000 fffff880`033b1000 fffff880`0bc3f780 00000000`00000000 : nt!KiStartSystemThread+0x16

Now here's where we have some more info, and a much better stack. We can see a few bthport.sys calls (Bluetooth Bus system driver) and then we have our familiar btmhsf.sys (Intel Proset Bluetooth HighSpeed Filter driver) towards the top of the stack.

Let's go ahead and take a look at the current IRP within the thread:

Code: 
0: kd> !irp fffffa800782e440 7
Irp is active with 11 stacks 11 is current (= 0xfffffa800782e7e0)
 No Mdl: No System Buffer: Thread fffffa80039e0040:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = fffffa80039e0428
ThreadListEntry.Blink = fffffa80039e0428
IoStatus.Status = 00000000
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = fffff880033b68b0
UserEvent = fffff880033b68c0
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000   
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = fffffa800782e4b8
Tail.Overlay.Thread = fffffa80039e0040
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = 00000000
Tail.Overlay.ListEntry.Blink = 00000000
Tail.Overlay.CurrentStackLocation = fffffa800782e7e0
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 1b, 2]   0  0 fffffa8007f97040 00000000 00000000-00000000    
           [COLOR=#ff0000][I][B]\Driver\btmhsf[/B][/I][/COLOR]
            Args: 00000000 00000000 00000000 00000000

Our favorite driver, btmhsf.sys!

If we had verifier enabled, we likely could have kept going and looked into the IO verifier.

-------------

From the above analysis, this is pretty solid evidence that btmhsf.sys is causing a problem here. Since updating the Intel drivers, have you crashed?

I'm enclosing my DMP, however, didn't have any BSOD since the last time.
Click to expand...

If I am understanding you correctly here, you have not?

Regards,

Patrick
 
I haven't crashed since the Intel drivers were updated so far, but it has been only half of the day already.

Hopefully everything will be fine now. I'll get you know if something will happen or after few days if everyhing is OK.

Thank you once more.
 
Hi again.

I guess everything is fine now and the problem is solved. Didn't have any BSOD since the last time reported. Thank you Patrick for your help :) I'm your debtor, for real. I wish there was more people like you in this world.

With regard.

Arinnis (Adrian)
 

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

Back
Top