I get BSOD when I try to stream from my pc to twitch. I have reset the whole computer including windows 10 and all my drivers. I have scanned for viruses and checked all my hardware to the best of my ability with no luck. (amd FX-8350 , radeon rx 460 videocard,16 gb ddr3 ram ipjaws, mb asrock 970A-G/3.1) dump files below https://1drv.ms/f/s!AiYI86xq2w4fhxdUNvBUxh6pt7jZ
BSOD i have tried everything i can think of.
- Thread starter Rhion145
- Start date
- Jun 12, 2015
- 66,935
- 6,932
- 168,140
I can't read dump files but this can - can you download and run whocrashed: http://www.resplendence.com/whocrashed
it will create a summary of the bsod and show us what you dealing with
Copy/paste results in here unless its obvious - it may tell you a driver name, for instance.
it will create a summary of the bsod and show us what you dealing with
Copy/paste results in here unless its obvious - it may tell you a driver name, for instance.
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-A1OI25O
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\Windows
Hardware: ASRock, 970A-G/3.1
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 17148080128 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 12/15/2016 8:36:37 PM your computer crashed
crash dump file: C:\Windows\Minidump\121516-197562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x1E1A07B0, 0xE, 0x0, 0xFFFFF802A56290F5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 12/15/2016 8:36:37 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: mpengine.sys (mpengine!MpContainerWrite+0x93A9A)
Bugcheck code: 0xA (0x1E1A07B0, 0xE, 0x0, 0xFFFFF802A56290F5)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mpengine.sys .
Google query: mpengine.sys IRQL_NOT_LESS_OR_EQUAL
On Thu 12/15/2016 11:42:17 AM your computer crashed
crash dump file: C:\Windows\Minidump\121516-5125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA0 (0x107, 0xA, 0xFFFFA9049982F380, 0x0)
Error: INTERNAL_POWER_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the power policy manager experienced a fatal error.
This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 12/9/2016 8:17:20 AM your computer crashed
crash dump file: C:\Windows\Minidump\120916-229718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xD1 (0x140EFA70, 0x2, 0x8, 0x140EFA70)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 12/8/2016 11:44:41 AM your computer crashed
crash dump file: C:\Windows\Minidump\120816-5203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802A7EFCCB3, 0xFFFF878149A508A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Computer name: DESKTOP-A1OI25O
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\Windows
Hardware: ASRock, 970A-G/3.1
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 17148080128 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 12/15/2016 8:36:37 PM your computer crashed
crash dump file: C:\Windows\Minidump\121516-197562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x1E1A07B0, 0xE, 0x0, 0xFFFFF802A56290F5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 12/15/2016 8:36:37 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: mpengine.sys (mpengine!MpContainerWrite+0x93A9A)
Bugcheck code: 0xA (0x1E1A07B0, 0xE, 0x0, 0xFFFFF802A56290F5)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mpengine.sys .
Google query: mpengine.sys IRQL_NOT_LESS_OR_EQUAL
On Thu 12/15/2016 11:42:17 AM your computer crashed
crash dump file: C:\Windows\Minidump\121516-5125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA0 (0x107, 0xA, 0xFFFFA9049982F380, 0x0)
Error: INTERNAL_POWER_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the power policy manager experienced a fatal error.
This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 12/9/2016 8:17:20 AM your computer crashed
crash dump file: C:\Windows\Minidump\120916-229718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xD1 (0x140EFA70, 0x2, 0x8, 0x140EFA70)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 12/8/2016 11:44:41 AM your computer crashed
crash dump file: C:\Windows\Minidump\120816-5203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802A7EFCCB3, 0xFFFF878149A508A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
- Jun 12, 2015
- 66,935
- 6,932
- 168,140
mpengine.sys - Microsoft Malware Protection... odd to get an irq error in a Microsoft file. What antivirus are you using? Might want to run a scan using Malewarebytes
INTERNAL_POWER_ERROR - 0x107 - A data mismatch has occurred in the internal hibernation data structures. can't say I seen this one before, one possible fix is malware scan. Another fix could be: https://support.microsoft.com/en-us/kb/920730
normally IRQ errors are drivers but alas, none of them are showing any driver names, apart from the file name above they all blame ntoskrnl and its not the cause. Its the heart of windows and isn't normally suicidal
INTERNAL_POWER_ERROR - 0x107 - A data mismatch has occurred in the internal hibernation data structures. can't say I seen this one before, one possible fix is malware scan. Another fix could be: https://support.microsoft.com/en-us/kb/920730
normally IRQ errors are drivers but alas, none of them are showing any driver names, apart from the file name above they all blame ntoskrnl and its not the cause. Its the heart of windows and isn't normally suicidal
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 12/17/2016 2:26:03 PM your computer crashed
crash dump file: C:\Windows\Minidump\121716-256125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x1B18C90, 0xE, 0x0, 0xFFFFF800E54950F5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Crash dumps are enabled on your computer.
On Sat 12/17/2016 2:26:03 PM your computer crashed
crash dump file: C:\Windows\Minidump\121716-256125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x1B18C90, 0xE, 0x0, 0xFFFFF800E54950F5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
I have also noticed that when I power up the computer the disk 0 and disk one process the read and write request stays at about 2% but after the computer has a bsod and restarts I have noticed that both disks are at about +90% for a couple minutes. Thank you so much for working on this with me!
Hmm one of the stop errors 0x000000a0 the internal power stop error maybe related to hibernation
Disable it for now. Open a command prompt as admin. Type in powercfg.exe /hibernate off
I would disable /uninstall this as well ASRock RAM Disk. I would also uninstall/disable ASRock App Charger Driver
Programs like this never work. All they'll do, is crash windows. ASUS and Gigabyte have a similar program for charging. They do the same thing crash
Disable it for now. Open a command prompt as admin. Type in powercfg.exe /hibernate off
I would disable /uninstall this as well ASRock RAM Disk. I would also uninstall/disable ASRock App Charger Driver
Programs like this never work. All they'll do, is crash windows. ASUS and Gigabyte have a similar program for charging. They do the same thing crash
most recent dump after doing the suggestions
On Tue 12/20/2016 11:38:19 AM your computer crashed
crash dump file: C:\Windows\Minidump\122016-211562-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF807F280D02E)
Bugcheck code: 0xD1 (0x153, 0x2, 0x0, 0xFFFFF807F280D02E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 12/20/2016 11:38:19 AM your computer crashed
crash dump file: C:\Windows\Minidump\122016-211562-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF807F280D02E)
Bugcheck code: 0xD1 (0x153, 0x2, 0x0, 0xFFFFF807F280D02E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
TRENDING THREADS
-
-
News AMD says Intel's 'horrible product' is causing Ryzen 9 9800X3D shortages- Started by Admin
- Replies: 88
-
Discussion PSU recommendations and power supply discussion thread - Tom's hardware- Started by Darkbreeze
- Replies: 2K
-
Discussion What's your favourite video game you've been playing?- Started by amdfangirl
- Replies: 4K
-
News Microsoft 365 users still on Windows 10 will be out of luck when Windows 10 is retired in October
- Started by Admin
- Replies: 19
Facebook
Twitter
Instagram