This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
So, I’m not sure if this is a Plex specific issue or something else entirely. About 4 months ago I started running into BSOD issues. After quite a bit of troubleshooting I figured it was my RAM and ended up RMA’ing it. I just received it back about a month ago and I’m having the same issues. It seems isolated to whenever plex is running though. If I disable my server, I don’t have any issues, but once the server is up an running it’s anywhere between a couple of hours to a couple of days and I will inevitably blue screen. I tested this all last week by having plex disabled and had no issues whatsoever. Once I started it up again, within 4 hours I had a BSOD. I posted below the minidump from my last crash. Any advice would be appreciated because I’m pretty well stumped at this point.
Hardware Processor : 17-7820X
RAM: 16 GB Trident Z
Video Card: Nvidia GTX 1080 TI
Mobo: Asus Prime X299-Deluxe
Primary OS drive: Samsung 960 pro NVMe
Storage Drive: WD MyBook 4TB
==================================================
Dump File : 062318-23937-01.dmp
Crash Time : 6/23/2018 4:54:30 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : ffff9200`b2a1c0c0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff801`0ae9733b
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+198330
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.17134.112 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+198330
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\062318-23937-01.dmp
Processors Count : 16
Major Version : 15
Minor Version : 17134
Dump File Size : 2,299,954
Dump File Time : 6/23/2018 4:58:26 PM
==================================================
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi NightShadowEXE, to diagnose the underlying issue, I need to analyse your Mini-dump file(s):
Open Windows File Explorer
Navigate to C:\Windows\Minidump
Zip up the contents of that folder
Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
Then post a link here to the zip file, so we can take a look for you . . .
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 72%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESD%3C/text%3E%3C/svg%3E)
We need log files(called dump files) that tell us what lead to crash.
Please share them with us for a better analysis of the problem. Instructions can be found here:
https://answers.microsoft.com/en-us/windows/for...
Please let us know if you need any assistance about posting dump files.
I am a fellow community member who likes to help my peers when able.
Blue Screen errors can have many different causes.
Microsoft has put together an awesome troubleshooting tool to help diagnose and repair these types of errors. It can be found here
https://support.microsoft.com/en-us/help/14238/...
