Solved BSOD while using DeSmuME. (Twice)

Rhopero · Dec 31, 2014

On my new computer, I experienced a BSOD both last night, and the night before. Both crashes were under almost the exact same circumstances. (The program had been running for almost an hour both times) Any help is appreciated.

Update: My computer got another BSOD tonight, this time under completely different circumstances. I'm not sure what could have caused this one.

blueelvis · Jan 1, 2015

Hi Rhopero & Welcome to the forum ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-

Code:

0: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff801`973fa598 fffff801`953e2ae9 nt!KeBugCheckEx
01 fffff801`973fa5a0 fffff801`953e133a nt!KiBugCheckDispatch+0x69
02 fffff801`973fa6e0 fffff800`3bc1a777 nt!KiPageFault+0x23a
03 fffff801`973fa870 fffff800`3bc1b293 USBXHCI!Isoch_Stage_FreeScatterGatherList+0x1f
04 fffff801`973fa8a0 fffff800`3bc1b61e USBXHCI!Isoch_Stage_CompleteTD+0x12f
05 fffff801`973fa920 fffff800`3bc0dc66 USBXHCI!Isoch_ProcessTransferEventWithED1+0x252
06 fffff801`973fa9b0 fffff800`3bc2657f USBXHCI!Endpoint_TransferEventHandler+0x4e
07 fffff801`973faa20 fffff800`3bc1005a USBXHCI!UsbDevice_TransferEventHandler+0x87
08 fffff801`973faa80 fffff800`3a53fc81 USBXHCI!Interrupter_WdfEvtInterruptDpc+0x456
09 fffff801`973fab80 fffff801`952dd1e0 Wdf01000!FxInterrupt::DpcHandler+0xc1
0a fffff801`973fabb0 fffff801`952dc3fb nt!KiExecuteAllDpcs+0x1b0
0b fffff801`973fad00 fffff801`953da0d5 nt!KiRetireDpcList+0xdb
0c fffff801`973fafb0 fffff801`953d9ed9 nt!KxRetireDpcList+0x5
0d ffffd001`e8607a40 00000000`00000000 nt!KiDispatchInterruptContinue

The ZIP File contains only one dump file out of the 3 crashes.
According to the stack of the dump file, USBXHCI.sys called a page fault which is strange.
Below is a list of 3rd party drivers present on your system -

Code:

**************************Wed Dec 31 10:22:44.580 2014 (UTC + 5:30)**************************
[B][U]tosporte.sys                Tue Jun 16 16:18:47 2009 (4A37788F)
tosrfcom.sys                Mon Nov 29 08:14:26 2010 (4CF3138A)
tosrfusb.sys                Thu Dec  2 15:11:56 2010 (4CF769E4)
SASKUTIL64.SYS              Wed Jul 13 02:30:01 2011 (4E1CB5D1)
SASDIFSV64.SYS              Fri Jul 22 04:33:00 2011 (4E28B024)
[/U][/B]Rt630x64.sys                Fri Jun 21 14:59:10 2013 (51C41CE6)
GeneStor.sys                Fri Oct 18 18:45:04 2013 (52613458)
AODDriver2.sys              Tue Feb 11 16:36:52 2014 (52FA044C)
RtkBtfilter.sys             Mon Feb 24 14:59:43 2014 (530B1107)
RTKVHD64.sys                Tue Mar  4 17:56:03 2014 (5315C65B)
AMDACPKSL.SYS               Wed Mar 12 05:19:44 2014 (531FA118)
AtihdWB6.sys                Wed Mar 12 05:20:02 2014 (531FA12A)
rtwlane.sys                 Thu Mar 13 12:57:02 2014 (53215DC6)
LHidEqd.Sys                 Wed Mar 19 05:50:53 2014 (5328E2E5)
LEqdUsb.Sys                 Wed Mar 19 05:50:55 2014 (5328E2E7)
LHidFilt.Sys                Wed Mar 19 05:51:03 2014 (5328E2EF)
LMouFilt.Sys                Wed Mar 19 05:51:03 2014 (5328E2EF)
amd_sata.sys                Fri Mar 21 08:31:59 2014 (532BABA7)
amd_xata.sys                Fri Mar 21 08:32:02 2014 (532BABAA)
atikmpag.sys                Fri Nov 21 07:38:54 2014 (546E9EB6)
atikmdag.sys                Fri Nov 21 08:00:27 2014 (546EA3C3)

Rhopero · Jan 1, 2015

I tried to update those drivers, but I couldn't really figure out how to do it, so I uninstalled both them, and the programs associated. (The highlighted ones were the underlined ones, right..?)

I also thought it might be a good idea to update my graphics driver, which I did, but experiences a BSOD almost immediately after. I tried to use that Driver Verifier you posted, but I'm not sure if it worked or not.. after restarting my computer when prompted, and going back into the Verifier, I can't tell if it's active or not. Ever since that restart, I've been trying to reproduce a BSOD, but I can't seem to get it to trigger yet. I'll leave behind the log from the last few crashes, and give another update when/if I encounter another BSOD.

(And, I guess this goes without saying, but I also unplugged my Astro Device like you suggested)

UPDATE: I left DeSmuME running for about two hours after what I did above (While my Astro Device was unplugged) and it did not crash. (Before it crashed about every 50 minutes while that was open) I had to leave the house for about 6 hours this afternoon, so I plugged back in the Astro Device to see if that would make any difference. I had someone check by the house about 3-4 hours after I left, and I was told that my computer still had not undergone a BSOD. Now that I'm getting home a few more hours later, I'm finding that there *was* a BSOD sometime while I was gone. I'll post another log from the most recent crashes.

I'm pretty sure that the most recent log will have all the data that was in the one I had put here earlier today, but I'm not positive.. so I'll leave them both as attachments just in case.

blueelvis · Jan 4, 2015

Hi Rhopero ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes -

Code:

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001200, (reserved)
Arg3: 000000000410000b, Memory contents of the pool block
Arg4: [COLOR=#FF0000]ffffe0014cf25540[/COLOR], Address of the block of pool being deallocated

Code:

0: kd> !pool [COLOR=#FF0000]ffffe0014cf25540[/COLOR]
Pool page ffffe0014cf25540 region is Unknown
 ffffe0014cf25000 size:  110 previous size:    0  (Allocated)  MmCa
 ffffe0014cf25110 size:  110 previous size:  110  (Allocated)  MmCa
 ffffe0014cf25220 size:   c0 previous size:  110  (Allocated)  FMfc
 ffffe0014cf252e0 size:   60 previous size:   c0  (Allocated)  Io  
 ffffe0014cf25340 size:   50 previous size:   60  (Allocated)  usbp
 ffffe0014cf25390 size:   50 previous size:   50  (Allocated)  usbp
 ffffe0014cf253e0 size:   50 previous size:   50  (Allocated)  usbp
 ffffe0014cf25430 size:   50 previous size:   50  (Allocated)  usbp
 ffffe0014cf25480 size:   b0 previous size:   50  (Allocated)  NpFr Process: a12178790c6c2efe
*ffffe0014cf25530 size:  100 previous size:   b0  (Free ) *Hal 
  [B][U]Pooltag Hal  : Hardware Abstraction Layer, Binary : hal.dll[/U][/B]
 ffffe0014cf25630 size:  170 previous size:  100  (Allocated)  Ntfx
 ffffe0014cf257a0 size:  860 previous size:  170  (Allocated)  AfdB

So, it seems that the HAL.DLL which is the Hardware Abstraction Layer provided by Windows is making the bad pool request. This could mean that hardware is at fault but since the emulators also use the HAL for the emulation purposes, I won't strike DESUME being the problem here as well.
The next bugcheck blames the ATI Driver which caused the bugcheck. So, I am inclining more towards DESUME being at fault here.

Are you getting crashes when the DESUME is not running and the ASTRO Headset USB Device is not connected to the system?
Very little information is stored in the Minidump provided so I would need a Complete Memory Dump for further analysis. Kindly, follow the below guide to generate a Complete Memory Dump -
How to generate a kernel or a complete memory dump file in Windows Server 2008 and Windows Server 2008 R2

Make sure that you ZIP up the dump file before uploading it to a file hoster like OneDrive, Mediafire etc

Let me know how it goes ^_^

-Pranav

Rhopero · Jan 4, 2015

There were maybe three or four crashes that I can recall that seemed completely random to me. My parents pointed out that my computer seemed to bluescreen every time the garage door opened, and that it might be power surge related. I bought a surge protector yesterday afternoon, and there hasn't been a BSOD since.. Is that a possible cause? I'm still not fully convinced that was the only thing causing the problem.

(Forgot to mention before - I have not experienced a crash while my Astro Headset was unplugged, but I also don't really use my computer without the headset, so probably just a coincidence.)

UPDATE: Like I thought, the potential power surges were not the only cause of the crashes. Another BSOD has occurred, and now I'm trying to figure out how to get that complete memory dump that you asked for.. but I can't figure it out. I've been looking at that tutorial you linked for a half hour, but I'm not really understanding what I need to do. If I figure it out, I'll be sure to update this post again with the complete memory dump.

UPDATE 2: Several days ago, I updated my graphics driver via the device manager, with a BSOD occurring immediately after. I looked up more about that today, and tried uninstalling the driver, and reinstalling it from the official website. That seems to have fixed quite a few of the problems I have. But, once again, there is probably more causes for these crashes, but I'm not really sure. From the minidumps, did it appear as if there were different causes for some of the crashes? (I am still having trouble with getting that complete dump file.. I'm not very smart in that area, and the tutorial is confusing to me) I'll add the log from the last few crashes, however.. just in case they can tell us anything new.

Update 3: DeSmuME appears to be the most likely thing causing the crashes at this point. Assuming of course that the graphics driver, and power surges were a cause of any crashes. I'll have to wait and see if it crashes while DeSmuME is not running before I can say for sure. Any thoughts you have based on all that I've said these last few paragraphs would be appreciated (Even though I've failed to figure out how to get the complete dump file for you..)

Update 4: I tested out a bunch of different games today, and so far, other than DeSmuME, I encountered a BSOD in Final Fantasy VII on steam. Since it's technically a port of a PS1 game, I'm not sure if that counts as emulation or not. (Or would be utilizing HAL.DLL) This might be relevant, it might not.. but I feel it's worth stating as both that, and DeSmuME had a BSOD about 10-15 minutes after I opened it today. (While other games I tested did not.)

One quick update - I finally figured out how to turn on a complete memory dump. I'm testing things to make it BSOD now, as soon as it crashes next, I'll post the complete dump.

And here we go! I've finally got the complete memory dump for you - https://www.mediafire.com/?42cdnba82nz2d0e

blueelvis · Jan 8, 2015

Hi Rhopero ^_^,

Did you try using the system normally without the ASTRO Headset and Desume?

The dump file is a large file so I would need some time to download the file. Plus I will be reaching home tomorrow and only after then I can download such a large file.

Are you using a UPS?

-Pranav

Rhopero · Jan 8, 2015

Like I said in the update before, I have experienced at least a few crashes outside of DeSmuME. I will try without the headset later today, and see if that makes a difference.

"Are you using a UPS?"?

I actually had to look that up.. I'd imagine you mean an uninterruptible power supply? I'm not actually sure if I am, or not.. I'll be able to ask the person who helped me hook up my computer tonight, and I'll get back with an answer then.

Edit: No, I'm not using a UPS.

Update: I followed the same steps I took the other day to get the system to crash to get the complete memory dump, except this time without the headset plugged in. It didn't crash (at least not yet) But if it really was the Astro Device causing the problem, then I'm really not sure what I could do to fix it. I'm hoping that the complete memory dump will be able to confirm whether or not it was the headset, or if it's just a coincidence that it didn't crash yet. (I'm going to leave the headset unplugged, and let DeSmuME run for a bit, and I'll update again if it crashes)

blueelvis · Jan 10, 2015

Hi Rhopero ^_^,

Yes, I meant Uninterrupted Power Supply. Sorry for the confusion.

Let me know if you are able to get any crash without the headset ^_^

-Pranav

Rhopero · Jan 10, 2015

I'm yet to see it crash while the headset was unplugged.. so that's probably related in some way. And, while it's nice to know that may be the cause, I'd still like to know exactly why the headset would cause it to crash.

I ran tests while it was unplugged to see if it would crash, but as my computer does not have speakers, I won't really be able to use my computer normally until we are able to figure out the exact cause, and fix it. You're still going to analyze the complete memory dump, right?)

And, thank you for your help so far.

blueelvis · Jan 10, 2015

Rhopero said:
I'm yet to see it crash while the headset was unplugged.. so that's probably related in some way. And, while it's nice to know that may be the cause, I'd still like to know exactly why the headset would cause it to crash.

I ran tests while it was unplugged to see if it would crash, but as my computer does not have speakers, I won't really be able to use my computer normally until we are able to figure out the exact cause, and fix it. You're still going to analyze the complete memory dump, right?)

And, thank you for your help so far.

Yes.

Let me know how it goes ^_^

Rhopero · Jan 14, 2015

I tried plugging my astro headset into a different USB slot several days ago.. and I have not been able to cause a crash since. That most likely fixed it, but I'm not 100% certain. I'd still like the complete memory dump analyzed (if you can) So I know exactly what the problem was. Either way, I'll leave the thread as unsolved until you either get back with the complete memory dump analysis, or enough time passes that I'm convinced it's completely fixed.

blueelvis · Jan 15, 2015

Rhopero said:
I tried plugging my astro headset into a different USB slot several days ago.. and I have not been able to cause a crash since. That most likely fixed it, but I'm not 100% certain. I'd still like the complete memory dump analyzed (if you can) So I know exactly what the problem was. Either way, I'll leave the thread as unsolved until you either get back with the complete memory dump analysis, or enough time passes that I'm convinced it's completely fixed.

I have reached college. I will download the dump file tomorrow and see what I can find.

A faulty USB Port can also cause this issue. Let me know if you experience any further problems ^_^

-Pranav

Rhopero · Jan 24, 2015

It's been a few weeks now, I was about to say that it was completely fixed - just to have another BSOD. I'm not sure if it's the same thing causing this one, but it was under the exact same circumstances as previous crashes. I'll post another log so you can see if anything has changed.

UPDATE: Leaving DeSmuME open for another hour did not cause a crash, which I would say makes it clear that the astro headset's USB port was at least causing some of the issue. (And this also means that I won't be able to test to see if it's fixed anymore..) But hopefully either the log, or the complete memory dump will give us more insight.

blueelvis · Jan 30, 2015

Hi Rhopero ^_^,

Sorry for the late response

. I have been out all night for this week due to too many birthdays :0)
I have analysed the latest minidump file and below has been provided an analysis of the same for informative purposes :-

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem.

Code:

1: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffd001`335cf938 fffff800`05a350ba nt!RtlCompareMemory+0x6a
01 ffffd001`335cf950 ffffe001`06a894c0 [COLOR=#ff0000][U][B]tosrfbd[/B][/U][/COLOR]+0x350ba
02 ffffd001`335cf958 ffffd001`2ca08180 0xffffe001`06a894c0
03 ffffd001`335cf960 ffffd001`2ca142c0 0xffffd001`2ca08180
04 ffffd001`335cf968 ffffe001`05f3ab90 0xffffd001`2ca142c0
05 ffffd001`335cf970 fffff801`cde00000 0xffffe001`05f3ab90
06 ffffd001`335cf978 ffffe001`06a895c0 nt!_guard_check_icall_fptr <PERF> (nt+0x0)
07 ffffd001`335cf980 00000000`00000001 0xffffe001`06a895c0
08 ffffd001`335cf988 fffff801`cde808d6 0x1
09 ffffd001`335cf990 00000000`00000049 nt!KiSwapThread+0x196
0a ffffd001`335cfa30 ffffe001`0aefa010 0x49
0b ffffd001`335cfa38 fffff800`05a258f1 0xffffe001`0aefa010
0c ffffd001`335cfa40 ffffe001`0102e000 tosrfbd+0x258f1
0d ffffd001`335cfa48 ffffe001`0aefa001 0xffffe001`0102e000
0e ffffd001`335cfa50 ffffe001`0102e000 0xffffe001`0aefa001
0f ffffd001`335cfa58 ffffe001`05f6f646 0xffffe001`0102e000
10 ffffd001`335cfa60 ffffd001`335cfac2 0xffffe001`05f6f646
11 ffffd001`335cfa68 00000000`00000000 0xffffd001`335cfac2

Code:

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

Code:

1: kd> lmvm tosrfbd
start             end                 module name
fffff800`05a00000 fffff800`05a45e00   tosrfbd  T (no symbols)           
    Loaded symbol image file: tosrfbd.sys
    Image path: \SystemRoot\System32\drivers\tosrfbd.sys
    Image name: tosrfbd.sys
    Timestamp:        Sat Dec 11 20:38:09 [B][COLOR=#ff0000]2010[/COLOR][/B] (4D0393D9)
    CheckSum:         0004FC51
    ImageSize:        00045E00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

As we can see from the dump file, the Toshiba Bluetooth Driver caused the system to crash. It tried to de-refer NULL which is not allowed and hence the system crashed. Furthermore, the driver is extremely old.
Below is a list of 3rd party drivers present on your system -

Code:

**************************Sun Jan 25 01:40:55.059 2015 (UTC + 5:30)**************************
[COLOR=#ff0000][U][B]Toshidpt.sys                Wed May 20 06:49:57 2009 (4A135ABD)
tosporte.sys                Tue Jun 16 16:18:47 2009 (4A37788F)
Tosrfhid.sys                Mon Aug 30 06:52:44 2010 (4C7B07E4)
tosrfcom.sys                Mon Nov 29 08:14:26 2010 (4CF3138A)
tosrfusb.sys                Thu Dec  2 15:11:56 2010 (4CF769E4)
tosrfbd.sys                 Sat Dec 11 20:38:09 2010 (4D0393D9)
[/B][/U][/COLOR]Rt630x64.sys                Fri Jun 21 14:59:10 2013 (51C41CE6)
GeneStor.sys                Fri Oct 18 18:45:04 2013 (52613458)
AODDriver2.sys              Tue Feb 11 16:36:52 2014 (52FA044C)
RtkBtfilter.sys             Mon Feb 24 14:59:43 2014 (530B1107)
RTKVHD64.sys                Tue Mar  4 17:56:03 2014 (5315C65B)
AMDACPKSL.SYS               Wed Mar 12 05:19:44 2014 (531FA118)
AtihdWB6.sys                Wed Mar 12 05:20:02 2014 (531FA12A)
rtwlane.sys                 Thu Mar 13 12:57:02 2014 (53215DC6)
LHidEqd.Sys                 Wed Mar 19 05:50:53 2014 (5328E2E5)
LEqdUsb.Sys                 Wed Mar 19 05:50:55 2014 (5328E2E7)
LHidFilt.Sys                Wed Mar 19 05:51:03 2014 (5328E2EF)
LMouFilt.Sys                Wed Mar 19 05:51:03 2014 (5328E2EF)
amd_sata.sys                Fri Mar 21 08:31:59 2014 (532BABA7)
amd_xata.sys                Fri Mar 21 08:32:02 2014 (532BABAA)
appexDrv.sys                Mon Oct 13 11:13:47 2014 (543B6693)
atikmpag.sys                Fri Nov 21 07:38:54 2014 (546E9EB6)
amdacpksd.sys               Fri Nov 21 07:48:16 2014 (546EA0E8)
atikmdag.sys                Fri Nov 21 08:00:27 2014 (546EA3C3)

.

Let me know how it goes ^_^
-Pranav

Rhopero · Jan 30, 2015

Ah, yes.. I guess that would make sense. The reason I have the toshiba drivers installed is because, well.. I have a program that I use to connect my Wii U Pro Controller to my computer (I used it on my old computer as well) But the only program that recognizes the controller is Toshiba Bluetooth Stack.

Anyway, I'll see what I can do. Thanks again.

blueelvis · Jan 30, 2015

Rhopero said:
Ah, yes.. I guess that would make sense. The reason I have the toshiba drivers installed is because, well.. I have a program that I use to connect my Wii U Pro Controller to my computer (I used it on my old computer as well) But the only program that recognizes the controller is Toshiba Bluetooth Stack.

Anyway, I'll see what I can do. Thanks again.

Disconnect the Wii U Pro controller physically from the system and remove those Toshiba Drivers from the system.

Let me know how it goes ^_^

-Pranav

Rhopero · Feb 7, 2015

Thank you for your help over the past month. I think that was the last of the issues with my computer.

I'm still not sure exactly what caused the original crashes, but I'm probably just going to go ahead and mark the this thread as solved. I'll give it another day or two, but it's quite likely everything is fixed now.

blueelvis · Feb 8, 2015

Rhopero said:
Thank you for your help over the past month. I think that was the last of the issues with my computer.

I'm still not sure exactly what caused the original crashes, but I'm probably just going to go ahead and mark the this thread as solved. I'll give it another day or two, but it's quite likely everything is fixed now.

Hi Rhopero ^_^,

Glad to hear that the issue has been solved ^_^.
In case of further problems, kindly do not hesitate to post back ^_^

-Pranav

Solved BSOD while using DeSmuME. (Twice)

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer