Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Different bluescreens over long period


  • Please log in to reply
35 replies to this topic

#1 FeCoNiCuZn

FeCoNiCuZn

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:57 AM

Posted 16 February 2017 - 04:03 PM

Hey,

I have a problem with my computer which kept me busy for quite some time now. I spent countless hours to solve this problem, so far without success.
I have a lot of BSODs. Earlier they usually occured after the wake up from the enery saving mode. Directly after restarting the computer from it, I saw the error report (which were usually different every time) and nothing else.
Lately the bluescreens occur when the computer is active. Mostly I´m doing something in the internet when I get the problems.
The error report usually tells me "THREAD_STUCK_IN_DEVICE_DRIVER" lately.
I looked up the associated drivers and they seem to be mostly graphic drivers, but I don´t know very much about it.

These are the components of my computer:

processor: Intel i5-4690, 3,5 GHz
graphic card: AMD Radeon R9 200 Series
hard drive: Crucial CT256MX100SSD1, SSD 256 GB
Seagate Barracuda 2TB
motherboard:Gigabyte H97-HD3
RAM:2x 4GB Crucial
power supply: bequiet!, 600W
OS: Windows 10

As I said, I tried several things, I´ll try to list them:

graphic card: I tried every available driver. Also I deactivated the graphic card of the processor and after that I disconnected the AMD graphic card. In both cases there were new BSODs.

I reinstalled the OS several times. I had it on both hard drives and I tried Windows 8.1 and Windows 10. None of that worked.

I basically also excluded the RAM as source of the error. I used every unit seperatedly and tried every slot, but the problems were the same. I also used Memtest with both units and no error was detected.

I´m running out of ideas what else I could try. Does anybody have an idea?

I would be really grateful if anybody could help me. I´d also be willing to reward the one who gives me the the deciding help with 50 $ (PayPal, or if preferd a donation for a good purpose).

Here is a list of the bluescreens. I´ll also add the minidump files.

 

[attachment=190461:Minidump.zip]

 

[attachment=190462:SysnativeFileCollectionApp.zip]




021517-4750-01.dmp    Mi 15 02 2017 11:32:52 Uhr    THREAD_STUCK_IN_DEVICE_DRIVER    0x100000ea    ffffa883`dc071640    00000000`00000000    00000000`00000000    00000000`00000000    dxgkrnl.sys    dxgkrnl.sys+22dff                    x64    ntoskrnl.exe+14a6f0                    C:\WINDOWS\Minidump\021517-4750-01.dmp    4    15    14393    412.588    Mi 15 02 2017 11:41:38 Uhr    
021517-5421-01.dmp    Mi 15 02 2017 09:31:36 Uhr    THREAD_STUCK_IN_DEVICE_DRIVER    0x100000ea    ffffaf84`0480f800    00000000`00000000    00000000`00000000    00000000`00000000    dxgkrnl.sys    dxgkrnl.sys+22dff                    x64    ntoskrnl.exe+14a6f0                    C:\WINDOWS\Minidump\021517-5421-01.dmp    4    15    14393    412.428    Mi 15 02 2017 09:32:50 Uhr    
021317-4718-01.dmp    Mo 13 02 2017 21:08:36 Uhr    THREAD_STUCK_IN_DEVICE_DRIVER    0x100000ea    ffff848b`fd30e080    00000000`00000000    00000000`00000000    00000000`00000000    dxgkrnl.sys    dxgkrnl.sys+22dff                    x64    ntoskrnl.exe+14a6f0                    C:\WINDOWS\Minidump\021317-4718-01.dmp    4    15    14393    412.620    Mo 13 02 2017 23:16:08 Uhr    
021317-5015-01.dmp    Mo 13 02 2017 16:51:33 Uhr    THREAD_STUCK_IN_DEVICE_DRIVER    0x100000ea    ffffab09`c10cf080    00000000`00000000    00000000`00000000    00000000`00000000    dxgkrnl.sys    dxgkrnl.sys+22dff                    x64    ntoskrnl.exe+14a6f0                    C:\WINDOWS\Minidump\021317-5015-01.dmp    4    15    14393    412.628    Mo 13 02 2017 16:53:35 Uhr    
021117-5171-01.dmp    Sa 11 02 2017 21:06:47 Uhr    THREAD_STUCK_IN_DEVICE_DRIVER    0x100000ea    ffffb688`92ce8680    00000000`00000000    00000000`00000000    00000000`00000000    dxgkrnl.sys    dxgkrnl.sys+22dff                    x64    ntoskrnl.exe+14a6f0                    C:\WINDOWS\Minidump\021117-5171-01.dmp    4    15    14393    412.524    Sa 11 02 2017 21:12:27 Uhr    
020917-8734-01.dmp    Do 09 02 2017 07:30:41 Uhr    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff801`719013b7    ffffc301`9f2e5e40    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+14a6f0                    x64    ntoskrnl.exe+14a6f0                    C:\WINDOWS\Minidump\020917-8734-01.dmp    4    15    14393    298.933    Do 09 02 2017 15:23:21 Uhr    
013117-4937-01.dmp    Di 31 01 2017 09:18:49 Uhr    THREAD_STUCK_IN_DEVICE_DRIVER    0x100000ea    ffffa20a`76629080    00000000`00000000    00000000`00000000    00000000`00000000    dxgkrnl.sys    dxgkrnl.sys+22dff                    x64    ntoskrnl.exe+14a6f0                    C:\WINDOWS\Minidump\013117-4937-01.dmp    4    15    14393    412.420    Di 31 01 2017 09:24:54 Uhr    
013017-6046-01.dmp    Mo 30 01 2017 23:25:31 Uhr    THREAD_STUCK_IN_DEVICE_DRIVER    0x100000ea    ffff8085`92176800    00000000`00000000    00000000`00000000    00000000`00000000    dxgkrnl.sys    dxgkrnl.sys+22dff                    x64    ntoskrnl.exe+14a6f0                    C:\WINDOWS\Minidump\013017-6046-01.dmp    4    15    14393    412.420    Mo 30 01 2017 23:27:05 Uhr    
012817-4515-01.dmp    Sa 28 01 2017 10:24:16 Uhr        0x00000139    00000000`00000003    ffff9c01`c5504520    ffff9c01`c5504478    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+14a6f0                    x64    ntoskrnl.exe+14a6f0                    C:\WINDOWS\Minidump\012817-4515-01.dmp    4    15    14393    455.548    Sa 28 01 2017 10:53:13 Uhr    
012717-4406-01.dmp    Fr 27 01 2017 14:34:21 Uhr    THREAD_STUCK_IN_DEVICE_DRIVER    0x100000ea    ffffca89`0e2ff800    00000000`00000000    00000000`00000000    00000000`00000000    dxgkrnl.sys    dxgkrnl.sys+22dff                    x64    ntoskrnl.exe+14a6f0                    C:\WINDOWS\Minidump\012717-4406-01.dmp    4    15    14393    412.468    Fr 27 01 2017 14:35:47 Uhr    
012317-4484-01.dmp    Mo 23 01 2017 15:08:10 Uhr        0x00000109    a39fca59`ea6eb53b    b3b6d6e0`3cee5719    fffff803`da946000    00000000`00000023    kd.dll    kd.dll+2000                    x64    ntoskrnl.exe+14a6f0                    C:\WINDOWS\Minidump\012317-4484-01.dmp    4    15    14393    329.772    Mo 23 01 2017 15:08:59 Uhr    
012317-4687-01.dmp    Mo 23 01 2017 11:52:30 Uhr    THREAD_STUCK_IN_DEVICE_DRIVER    0x100000ea    ffff8583`d3b4a800    00000000`00000000    00000000`00000000    00000000`00000000    dxgkrnl.sys    dxgkrnl.sys+22dff                    x64    ntoskrnl.exe+14a6f0                    C:\WINDOWS\Minidump\012317-4687-01.dmp    4    15    14393    412.548    Mo 23 01 2017 11:53:29 Uhr    
011217-4890-01.dmp    Do 12 01 2017 20:22:42 Uhr    THREAD_STUCK_IN_DEVICE_DRIVER    0x100000ea    ffffc90d`3e8c3080    00000000`00000000    00000000`00000000    00000000`00000000    dxgkrnl.sys    dxgkrnl.sys+22dff                    x64    ntoskrnl.exe+14a6f0                    C:\WINDOWS\Minidump\011217-4890-01.dmp    4    15    14393    412.532    Do 12 01 2017 20:23:42 Uhr    
011217-4968-01.dmp    Do 12 01 2017 16:17:59 Uhr        0x0000012b    ffffffff`c00002c4    00000000`00000612    00000000`054d61b0    ffff9a80`bb47e000    ntoskrnl.exe    ntoskrnl.exe+14a6f0                    x64    ntoskrnl.exe+14a6f0                    C:\WINDOWS\Minidump\011217-4968-01.dmp    4    15    14393    543.788    Do 12 01 2017 16:19:18 Uhr    
010717-7890-01.dmp    Sa 07 01 2017 14:20:25 Uhr    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED    0x1000007e    ffffffff`c0000005    fffff802`6b003bfc    ffffa081`dd7b4368    ffffa081`dd7b3b90    ntoskrnl.exe    ntoskrnl.exe+1f5bfc                    x64    ntoskrnl.exe+1f5bfc                    C:\WINDOWS\Minidump\010717-7890-01.dmp    4    15    14393    398.140    Sa 07 01 2017 15:58:47 Uhr    
122116-8109-01.dmp    Mi 21 12 2016 13:04:41 Uhr    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED    0x1000007e    ffffffff`c000001d    fffff80c`6b865271    ffffbd81`4833f6e8    ffffbd81`4833ef10    srv2.sys    srv2.sys+37000                    x64    srv2.sys+5271                    C:\WINDOWS\Minidump\122116-8109-01.dmp    4    15    14393    412.676    Mi 21 12 2016 13:05:22 Uhr    
121316-6031-01.dmp    Di 13 12 2016 22:44:24 Uhr    BAD_POOL_CALLER    0x000000c2    00000000`0000000d    ffffe387`3555de10    00000000`73634946    02c11b6c`f373b2df    FLTMGR.SYS    FLTMGR.SYS+0                    x64    ntoskrnl.exe+14a6f0                    C:\WINDOWS\Minidump\121316-6031-01.dmp    4    15    14393    412.412    Di 13 12 2016 22:45:08 Uhr    
112416-7343-01.dmp    Do 24 11 2016 13:58:47 Uhr    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    00000000`00000000    00000000`000000ff    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+14a510                    x64    ntoskrnl.exe+14a510                    C:\WINDOWS\Minidump\112416-7343-01.dmp    4    15    14393    110.080    Do 24 11 2016 17:07:29 Uhr    


with best regards

FeCiNiCuZn



BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:02:57 AM

Posted 16 February 2017 - 05:59 PM

Can you provide us with the exact model of your graphics card? Please run Speccy:

 

:step1: Speccy by Piriform

• Download and save Speccy from here.
• Right-click on the downloaded ZIP file, click Extract all, taking note of where the files will be extracted, and then hit Extract.
• Open up the extracted folder, right-click on Speccy64.exe, and select Run as administrator. Please accept any User Account Control prompts.
• After waiting a while, click File, then Publish Snapshot.
• Hit Yes to the Publish Snapshot dialog, then click Copy to Clipboard. Paste the URL in your next reply.


Edited by bwv848, 16 February 2017 - 05:59 PM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 FeCoNiCuZn

FeCoNiCuZn
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:57 AM

Posted 17 February 2017 - 02:54 AM

Thank you for your answer. I did what you told me, here are the results

 

http://speccy.piriform.com/results/3yquMsmWT8mVJjPJQGhC4hh



#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:02:57 AM

Posted 17 February 2017 - 09:58 AM

Is it possible you open the case and identify the exact model number? We know that it's an AMD Radeon R9 200 Series, but there are many, many models carrying that name.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#5 FeCoNiCuZn

FeCoNiCuZn
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:57 AM

Posted 17 February 2017 - 03:19 PM

OK, I opened the case, I only found a sticker on it, but maybe it contains what you are looking for:

 

R9 290 4G GDDR5 PCI-E DUAL DVI-D/HDMI/DP TRI-X OC VERSION (UEFI)

 

PN 299-2E285-100SA              SKU# 11227-00



#6 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:02:57 AM

Posted 17 February 2017 - 03:54 PM

That's all I need, thank you.

I suspect that your graphics card isn't getting enough power. Is it possible you disconnect your other two hard drives to ease the load on the system? Try removing other unnecessary components too.

Results? Thanks.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#7 FeCoNiCuZn

FeCoNiCuZn
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:57 AM

Posted 17 February 2017 - 04:05 PM

That sounds interesting, and when I think about it, it seems possible. I will try, thank you.

I simply removed the graphics card completely, that should tell us, if that was the problem.


Edited by FeCoNiCuZn, 17 February 2017 - 04:20 PM.


#8 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:02:57 AM

Posted 18 February 2017 - 08:31 PM

Honestly, I would still remove the other two hard drives, as they consume a decent amount of power. Is it possible you remove the DVD/CD drive too? Our aim is to strip down the system to the bare minimum as much as possible.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#9 FeCoNiCuZn

FeCoNiCuZn
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:57 AM

Posted 19 February 2017 - 06:22 AM

Yes, I already removed my second hard drive, so I only use my main hard drive right now.

So far I didn´t have another bluescreen, but I will also remove the DVD drive.



#10 FeCoNiCuZn

FeCoNiCuZn
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:57 AM

Posted 19 February 2017 - 04:20 PM

OK, now it happened again. Today I got another bluescreen during a skype call. It was an other error message, but I didn´t remember it and there is no minidump file of it, but it was none of the error messages I received before.

 

I had removed the DVD drive, my second hard drive and my main graphics card.

 

So the only components that were connected were my SSD hard drive, the RAM and the processor (and the corresponding graphics card) and of course the fans.



#11 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:02:57 AM

Posted 19 February 2017 - 05:33 PM

Yes, it probably isn't even related. Can you run the Sysnative File Collection App again?


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#12 FeCoNiCuZn

FeCoNiCuZn
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:57 AM

Posted 20 February 2017 - 04:08 AM

OK, I ran it again, here are the results:
 

Edited by FeCoNiCuZn, 20 February 2017 - 04:18 AM.


#13 FeCoNiCuZn

FeCoNiCuZn
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:57 AM

Posted 20 February 2017 - 08:46 AM

OK, another bluescreen

 

error message: MEMORY_MANAGEMENT

 

shortly before the bluescreen the internet connection stopped working


Edited by FeCoNiCuZn, 20 February 2017 - 08:47 AM.


#14 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:02:57 AM

Posted 20 February 2017 - 10:16 AM

Sorry, but I can't view the attachment for some reason. Anyway, since you experienced another BSOD, can you run the Sysnative File Collection App again?

 

Thanks.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#15 FeCoNiCuZn

FeCoNiCuZn
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:57 AM

Posted 20 February 2017 - 02:40 PM

OK, I ran it again. Can you opne the attachment now?
 
 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users