Windows 10: Thread stuck in driver BSOD, bugcheck reboot error in event viewer

So I've been having these random Thread Stuck In Driver errors in my poor laptop for a good while now. This time around I had Skype Preview open, Chrome, and League. It happened when I wasn't even in a game on League--- I was responding to a friend in chat. I suppose it should help to mention as well that Windows Shell Common DLL crashes when I try to view recording devices in Sound properties as well. Don't know if those are connected. Anyways, the error from what I see in the event viewer says this:

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ea (0xffffcc0befc627c0, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 85a31bdb-ffbb-40f1-a02f-0f9101928d5f.


Then the dump file deletes itself because I have too much stuff on my computer. Though there might be older MEMORY.DMP files that show other instances of the bluescreen.

param1 0x000000ea (0xffffcc0befc627c0, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000) param2 C:\WINDOWS\MEMORY.DMP param3 85a31bdb-ffbb-40f1-a02f-0f9101928d5f

Is the other page. I'm now going to attach the file from my desktop that I was instructed on the FAQ to put in here to help you guys solve my problem.

Thank you in advance!

:)

 

Blue screen upon waking PC

I keep getting system exception BSODs with no error code given other than that upon waking my system from sleep. Recently updated drivers and now it throws a different error code in event viewer than before.

"The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80174c8fb90, 0xffff8181ec6dab50, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 59f26056-d612-40b2-a2de-9cad65a5101d."

082117-17687-01.dmp Here is a link to the dump file that was most recently created.

 

BugCheck Error Event ID 1001

Hello,

I have been running into an issue lately and cannot figure out the root cause. I have been getting a stop error (BSOD) and when I check the event viewer I see this error.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff888d3be1a028, 0x00000000fe000000, 0x0000000000801136). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 593e7c9e-6e0e-441a-9973-3083f449593f.

I do have copies of the dump file and a saved copy of the event viewer. Not sure where I can upload them for viewing. Any help with this would be appreciated.

Thank you,

Guy

 

Did you try the Beta Crimson driver here? Legacy

Attachment 96533

I suggest completely uninstalling the AMD display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then install the beta driver, see if that works.

 

Alright, I've done as you asked but Idk if I'll bluescreen again. I could go a month without the bluescreen and then it'll happen again. As for the Shell Common DLL issue that could also be a problem... What's up with that?

 

No idea about Shell Common DLL as I don't have a dump to look at.

The dump in C:\WINDOWS\MEMORY.DMP is a full kernel dump, not a small kernel dump and there is only one adn it's over written if another occurs.

Please make sure your PC is configured for small dump files:

How to Configure Windows 10 to Create Dump Files on BSOD

 

So far it hasn't blatantly caused a bluescreen, but... I have a screenshot of what happens.

Attachment 96790

Literally happens when I click on a microphone device in recording devices. It doesn't happen if I click on something in playback.

 

Run the following commands in sequence from a Elevated Command Prompt:

Dism /Online /Cleanup-Image /StartComponentCleanup
Dism /Online /Cleanup-Image /RestoreHealth
SFC /scannow

See if that repairs or replaces any corrupted or missing system files.

You should also look at the tests available on the Lenovo website for your laptop:
See here: Laptops-and-netbooks :: ThinkPad-X-Series-laptops :: ThinkPad-X140e - Lenovo Support (US)

There are 12 available.

 

Alright. I have managed to do some of those tests, but nothing has fixed the shell common dll error. I think it's permanently messed up. But, SO FAR I haven't bluescreened but only time will tell since they were kind of random but consistent enough to be annoying. Thank you so much for your help. If you have anything else to suggest, let me know!

 

Did you get any report of errors or problems fixed when you ran the 3 commands I listed?

 

No, I didn't. Which is kinda sad...

 

Yo could try refreshing Windows 10: Refresh Windows 10 - Windows 10 Forums

Before you do, it would be a good idea to backup your data. The best way is to take an image backup using a program like Macrium Reflect Free, to an external hard drive. That way, no matter what happens you can always get back to where you are now.

 

Mmm, I'm gonna try that once I can fix my desktop computer since I don't really have an external harddrive... That's gonna be a while from now since we can't find any bubble wrap to send the desktop in to get fixed.

 

Oh yeah. The refreshing windows thing. I remember wanting to try that a while back. Don't remember my keyboard or mouse even being able to work in it...

 

If you have a wireless k3eyboard and mouse then you may need to use USB ones until the refresh is completed.