So, I've been having this problem ever since I put together this build but I hadn't addressed it anywhere yet in an endeavour to find out what exactly is going on. I've tried searching on the web for a solution but I couldn't find anything specific that could really help me.
For the sake of addressing purposes I'm going to post my full system build.
RSoD's do ALWAYS occur whenever I'm in a gaming session for over ten minutes. Apparently, I don't get this problem when playing Minecraft at all, but I keep getting it with games like Metro Last Light, Wildstar, etc.
My personal theory regarding the RSoD's is that the GPU might require more power than the amount that my PSU is capable of providing. However, I highly doupt this possibility since 550 watts is what people seem to recommend around the web for a single R9 380 GPU. Ever since I first installed the GPU I had problems installing the drivers provided in the DVD that came within the box (couldn't install the AMD Gaming Evolved App) but after I uninstalled those drivers and downloaded the new Crimson software, everything installed correctly.
Apart from the RSoD's that are by far the biggest nuisance of all since they don't allow me to run any game at all, the system does also crash quite often with regular BSoD's, usually displaying to me one the following messages:
MEMORY_MANAGEMENT
IRQL_NOT_LESS_OR_EQUAL
PAGE_ERROR_IN_NON_PAGED_AREA
KERNEL_SECURITY_CHECK_FAILURE
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (dxgmms2.sys)
Whenever I get the 'kernel security check failure' crash reason, Windows runs a disk check during the next startup but never finds anything. I've also been getting a couple of other reasons that I cannot quite recall right now to post here. I will update the thread with any new crashes. Whenever I get the 'system exception not handled' reason, Windows will go on a repair-reboot circle that lasts for about 2 seconds per reboot and forces my system to reboot 6-7 times before starting up regularly again.
I've tried to run a repair through the Windows DVD but I would always get a message according to which Windows couldn't run repairs due to a missing file in the system.
I haven't ran a proper temperature or voltage check, etc, yet, but my bare hands suggest that the temperatures inside my build couldn't possibly reach more than 60-65 degrees in a 15 degree environment. I can't stress test that under a game load because, you know, the system crashes soon after I launch the game.
If you have any ideas and suggestions about my issue please post them.
Just to begin I work with computers for my job, though I'm not "too" experienced quite yet. One thing I can say, of all the computers I have worked with, the windows startup repair has "never" worked.
Now, your graphics card has a 150W standard power withdrawal, your 500W should do just fine, though other things in your computer can draw power. Your processor (which is a Quad-Core 3.3ghz) shouldn't be too demanding on power, so I don't suspect that as the problem. I do however note that your graphics card says behind it "overclocked". Are you overclocking your graphics card? What program did you use to overclock it? I'm familiar with your graphics card and I know that overclocking in the high frequencies is highly unstable. I tested this once on an intel based computer, and the card would always crash after about 15 minutes. It was fixed once I removed the overclocking.
If you are using the AMD Catalyist software, try setting they 3D Settings>Standard settings to "optimal performace", as this will eliminate fluff that may interfere with your graphics card performance.
How many ram sticks do you have? I know that DDR4 Ram sometimes will give you a blue screen of death if the ram is having issues. If you have more than one ram stick, try running your games without one ram, then without the other and see if the crashing stops.
Last but not least, make sure your graphics drivers are up to date. If you haven't tried it yet, check out AMD's Crimson Drivers. They're working pretty well right now. Here is the link to the graphics drivers that is specifically for your graphics card and computer setup (make sure to uninstall your current graphics drivers before installing the new ones): http://support.amd.com/en-us/download/desktop?os=Windows 10 - 64
Note: The only last thing I didn't talk about is the fact you are using Windows 10. I've only started working with it and have as of yet to learn the quirks with it and modern graphics cards.
One thing I can say, of all the computers I have worked with, the windows startup repair has "never" worked.
More often than not, sadly yes. It's been my experience as well.
Are you overclocking your graphics card? What program did you use to overclock it?
OP runs Factory Overclocked GPU, should be a non-issue. I run a Factory Overclocked 280X Toxic here, stable as a granite counter top.
All those errors are software related, I know at least ONE of them for sure, IRQL
Also, this is new. I've never encountered a RSOD. Ever.
This bug check indicates that the kernel has detected the corruption of a critical data structure. -Microsoft.com
This might point to something being critically broken in Windows. My guess is a corrupt driver of some kind.
Edit: OP, do me a favor and run a scan with www.malwarebytes.org free edition, will you? It's one of the most powerful scanners I've used, and should find even the nastiest of infections, just to be sure.
All those errors are software related, I know at least ONE of them for sure, IRQL
Also, this is new. I've never encountered a RSOD. Ever.
This bug check indicates that the kernel has detected the corruption of a critical data structure. -Microsoft.com
This might point to something being critically broken in Windows. My guess is a corrupt driver of some kind.
Edit: OP, do me a favor and run a scan with www.malwarebytes.org free edition, will you? It's one of the most powerful scanners I've used, and should find even the nastiest of infections, just to be sure.
Alright, so, I ran a check and Windows crashed midway through checking the System 32 folder. The crash reason was SYSTEM_SERVICE_EXCEPTION followed by another value in double parentheses that I canot recall.
I checked it up on Google, and it seems like the problem is completely driver related. However, how am I supposed to find which driver is faultering amongst the sea of all those drivers installed in my system?
Rollback Post to RevisionRollBack
" Because things are the way they are, things will not stay the way they are. " - Bertolt Brecht
Check for a "One of these things is not like the other!" Icon, my guess is it would be under Display adapters.
http://imgur.com/YdimsHl Notice how the AMD Audio module has a warning. That is because there are no drivers for that component installed (Intentionally). If they're corrupted, it should be the same looking error.
Quote from Tasty_Toast_Son>> http://imgur.com/YdimsHl Notice how the AMD Audio module has a warning. That is because there are no drivers for that component installed (Intentionally). If they're corrupted, it should be the same looking error.
Not required and optional to be installed and even if corrupted driver for it, it would not cause this for there is no actual call to the driver of the device. Separate driver entirely from the Display drivers.
MEMORY_MANAGEMENT
IRQL_NOT_LESS_OR_EQUAL
PAGE_ERROR_IN_NON_PAGED_AREA
These are more pointing at memory problems.
KERNEL_SECURITY_CHECK_FAILURE
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (dxgmms2.sys)
Can be VRAM or system physical RAM (including system shared RAM for graphics processor) given directX module. These are two things to look at.
Firstly, uninstall the AMD GPU drivers (prefer to use Display Driver Uninstaller from Guru3d to cleanup AMD garbage afterwords).
After uninstalling the AMD drivers and optionally used the cleanup tool, physically remove the GPU from the motherboard and use onboard Intel iGPU to see if the crashes still occurs. If they do, that rules out faulty VRAM or in general the Graphics card itself as well AMD drivers. However do not install the GPU nor AMD drivers back yet.
Secondly, if the crashes still occur. Will need to remove one physical ram stick from the motherboard and test to see if still occurs. If they do, put the removed stick back in and remove the other and test. If still happens. Then possibly a very badly corrupted operating system or driver installation and I would just go the route of full operating system reinstall. If still then, likely an faulty CPU or motherboard.
Not required and optional to be installed and even if corrupted driver for it, it would not cause this for there is no actual call to the driver of the device. Separate driver entirely from the Display drivers.
MEMORY_MANAGEMENT
IRQL_NOT_LESS_OR_EQUAL
PAGE_ERROR_IN_NON_PAGED_AREA
These are more pointing at memory problems.
KERNEL_SECURITY_CHECK_FAILURE
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (dxgmms2.sys)
Can be VRAM or system physical RAM (including system shared RAM for graphics processor) given directX module. These are two things to look at.
Firstly, uninstall the AMD GPU drivers (prefer to use Display Driver Uninstaller from Guru3d to cleanup AMD garbage afterwords).
After uninstalling the AMD drivers and optionally used the cleanup tool, physically remove the GPU from the motherboard and use onboard Intel iGPU to see if the crashes still occurs. If they do, that rules out faulty VRAM or in general the Graphics card itself as well AMD drivers. However do not install the GPU nor AMD drivers back yet.
Secondly, if the crashes still occur. Will need to remove one physical ram stick from the motherboard and test to see if still occurs. If they do, put the removed stick back in and remove the other and test. If still happens. Then possibly a very badly corrupted operating system or driver installation and I would just go the route of full operating system reinstall. If still then, likely an faulty CPU or motherboard.
Right, I'll get on to that. I can't run the physical RAM test however since I only have one RAM stick installed. I do suspect a bad system installation myself, so I will try to run a re-install as well.
Rollback Post to RevisionRollBack
" Because things are the way they are, things will not stay the way they are. " - Bertolt Brecht
Hmm, have you reused one of the hard drive in another computer before. Sometimes you might run into issues with having driver for a different computer running on this computer.
Had that happen with my server computer when upgrading the motherboard (new chipset), and result in Windows crashing as soon as it boot and then try to repair itself with no success, but It could cause BSOD.
It could also be bad ram, which would kind of suck.
Not required and optional to be installed and even if corrupted driver for it, it would not cause this for there is no actual call to the driver of the device. Separate driver entirely from the Display drivers.
MEMORY_MANAGEMENT
IRQL_NOT_LESS_OR_EQUAL
PAGE_ERROR_IN_NON_PAGED_AREA
These are more pointing at memory problems.
KERNEL_SECURITY_CHECK_FAILURE
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (dxgmms2.sys)
Can be VRAM or system physical RAM (including system shared RAM for graphics processor) given directX module. These are two things to look at.
Firstly, uninstall the AMD GPU drivers (prefer to use Display Driver Uninstaller from Guru3d to cleanup AMD garbage afterwords).
After uninstalling the AMD drivers and optionally used the cleanup tool, physically remove the GPU from the motherboard and use onboard Intel iGPU to see if the crashes still occurs. If they do, that rules out faulty VRAM or in general the Graphics card itself as well AMD drivers. However do not install the GPU nor AMD drivers back yet.
Secondly, if the crashes still occur. Will need to remove one physical ram stick from the motherboard and test to see if still occurs. If they do, put the removed stick back in and remove the other and test. If still happens. Then possibly a very badly corrupted operating system or driver installation and I would just go the route of full operating system reinstall. If still then, likely an faulty CPU or motherboard.
I've removed the GPU and the drivers and I'm currently operating the system based on the on-CPU Intel graphics unit. I'll post another report in two days. I will also try to run some games that don't rely on great graphical strength such as League of Legends to check if the system insists on crashing into RSoD, which I doupt.
EDIT: Alright, I've got some good news and some bad news. The good news are that the RSoDs did stop happening indeed. However, I cannot decide whether the problem lies in a problematic driver or a faulty GPU. The bad news are that the BSoDs didn't stop. The system has crashed twice thus far and the problem is reported as, yet again, MEMORY_MANAGEMET. Which means that I probably need to send the RAM stick back and request from the company to send me another one...
EDIT #2: I re-installed the GPU. Turns out the RSoDs aren't just gone yet. This time I managed to log a solid 40 minutes into Metro LL before my system broke down into a red screen crash. I do believe that the RSoD problem has to do with the GPU itself now rather than the drivers, since the RSoD got a 20 minute postpone after I plugged the GPU in, as I am either too dumb and can't connect 2 PCI-E 6 pin connectors to the GPU or the bus is faulty and it doesn't make solid contact with the motherboard. Then again, it might be the PSU but I'm quite certain that XFX PSUs are not problematic. And the blue screens continue, this time a new error occured though: FAULTY_HARDWARE_CORRUPTED_PAGE. Does this error point towards the GPU or the RAM though? That I don't know.
Hmm, have you reused one of the hard drive in another computer before. Sometimes you might run into issues with having driver for a different computer running on this computer.
Had that happen with my server computer when upgrading the motherboard (new chipset), and result in Windows crashing as soon as it boot and then try to repair itself with no success, but It could cause BSOD.
It could also be bad ram, which would kind of suck.
Both of my drives are brand new and straight out of the box. If it does turn out to be a bad RAM problem, then I will, unfortunately, have to get a new stick(s).
Rollback Post to RevisionRollBack
" Because things are the way they are, things will not stay the way they are. " - Bertolt Brecht
So, I've been having this problem ever since I put together this build but I hadn't addressed it anywhere yet in an endeavour to find out what exactly is going on. I've tried searching on the web for a solution but I couldn't find anything specific that could really help me.
For the sake of addressing purposes I'm going to post my full system build.
CPU: Intel Core i5-6600k
RAM: Kingston HyperX Fury DDR4 2400Mhz 8Gb
GPU: MSI Radeon R9 380 2Gb factory overclocked
M/B: ASRock H170 Pro4
Kingston SSDNow V300 SSD 120Gb + Seagate Barracuda HDD 1Tb
Coolermaster Hyper 212 Evo
OS: Windows 10
RSoD's do ALWAYS occur whenever I'm in a gaming session for over ten minutes. Apparently, I don't get this problem when playing Minecraft at all, but I keep getting it with games like Metro Last Light, Wildstar, etc.
My personal theory regarding the RSoD's is that the GPU might require more power than the amount that my PSU is capable of providing. However, I highly doupt this possibility since 550 watts is what people seem to recommend around the web for a single R9 380 GPU. Ever since I first installed the GPU I had problems installing the drivers provided in the DVD that came within the box (couldn't install the AMD Gaming Evolved App) but after I uninstalled those drivers and downloaded the new Crimson software, everything installed correctly.
Apart from the RSoD's that are by far the biggest nuisance of all since they don't allow me to run any game at all, the system does also crash quite often with regular BSoD's, usually displaying to me one the following messages:
MEMORY_MANAGEMENT
IRQL_NOT_LESS_OR_EQUAL
PAGE_ERROR_IN_NON_PAGED_AREA
KERNEL_SECURITY_CHECK_FAILURE
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (dxgmms2.sys)
Whenever I get the 'kernel security check failure' crash reason, Windows runs a disk check during the next startup but never finds anything. I've also been getting a couple of other reasons that I cannot quite recall right now to post here. I will update the thread with any new crashes. Whenever I get the 'system exception not handled' reason, Windows will go on a repair-reboot circle that lasts for about 2 seconds per reboot and forces my system to reboot 6-7 times before starting up regularly again.
I've tried to run a repair through the Windows DVD but I would always get a message according to which Windows couldn't run repairs due to a missing file in the system.
I haven't ran a proper temperature or voltage check, etc, yet, but my bare hands suggest that the temperatures inside my build couldn't possibly reach more than 60-65 degrees in a 15 degree environment. I can't stress test that under a game load because, you know, the system crashes soon after I launch the game.
If you have any ideas and suggestions about my issue please post them.
Just to begin I work with computers for my job, though I'm not "too" experienced quite yet. One thing I can say, of all the computers I have worked with, the windows startup repair has "never" worked.
Now, your graphics card has a 150W standard power withdrawal, your 500W should do just fine, though other things in your computer can draw power. Your processor (which is a Quad-Core 3.3ghz) shouldn't be too demanding on power, so I don't suspect that as the problem. I do however note that your graphics card says behind it "overclocked". Are you overclocking your graphics card? What program did you use to overclock it? I'm familiar with your graphics card and I know that overclocking in the high frequencies is highly unstable. I tested this once on an intel based computer, and the card would always crash after about 15 minutes. It was fixed once I removed the overclocking.
If you are using the AMD Catalyist software, try setting they 3D Settings>Standard settings to "optimal performace", as this will eliminate fluff that may interfere with your graphics card performance.
How many ram sticks do you have? I know that DDR4 Ram sometimes will give you a blue screen of death if the ram is having issues. If you have more than one ram stick, try running your games without one ram, then without the other and see if the crashing stops.
Last but not least, make sure your graphics drivers are up to date. If you haven't tried it yet, check out AMD's Crimson Drivers. They're working pretty well right now. Here is the link to the graphics drivers that is specifically for your graphics card and computer setup (make sure to uninstall your current graphics drivers before installing the new ones): http://support.amd.com/en-us/download/desktop?os=Windows 10 - 64
Note: The only last thing I didn't talk about is the fact you are using Windows 10. I've only started working with it and have as of yet to learn the quirks with it and modern graphics cards.
Good luck!
.....................................................
All those errors are software related, I know at least ONE of them for sure, IRQL
Also, this is new. I've never encountered a RSOD. Ever.
This bug check indicates that the kernel has detected the corruption of a critical data structure. -Microsoft.com
This might point to something being critically broken in Windows. My guess is a corrupt driver of some kind.
Edit: OP, do me a favor and run a scan with www.malwarebytes.org free edition, will you? It's one of the most powerful scanners I've used, and should find even the nastiest of infections, just to be sure.
Alright, so, I ran a check and Windows crashed midway through checking the System 32 folder. The crash reason was SYSTEM_SERVICE_EXCEPTION followed by another value in double parentheses that I canot recall.
I checked it up on Google, and it seems like the problem is completely driver related. However, how am I supposed to find which driver is faultering amongst the sea of all those drivers installed in my system?
I go this route the check if I have all my essential drivers after a windows install.
http://www.howtogeek.com/167094/how-to-use-the-windows-device-manager-for-troubleshooting/
Check for a "One of these things is not like the other!" Icon, my guess is it would be under Display adapters.
http://imgur.com/YdimsHl Notice how the AMD Audio module has a warning. That is because there are no drivers for that component installed (Intentionally). If they're corrupted, it should be the same looking error.
Not required and optional to be installed and even if corrupted driver for it, it would not cause this for there is no actual call to the driver of the device. Separate driver entirely from the Display drivers.
MEMORY_MANAGEMENT
IRQL_NOT_LESS_OR_EQUAL
PAGE_ERROR_IN_NON_PAGED_AREA
These are more pointing at memory problems.
KERNEL_SECURITY_CHECK_FAILURE
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (dxgmms2.sys)
Can be VRAM or system physical RAM (including system shared RAM for graphics processor) given directX module. These are two things to look at.
Firstly, uninstall the AMD GPU drivers (prefer to use Display Driver Uninstaller from Guru3d to cleanup AMD garbage afterwords).
After uninstalling the AMD drivers and optionally used the cleanup tool, physically remove the GPU from the motherboard and use onboard Intel iGPU to see if the crashes still occurs. If they do, that rules out faulty VRAM or in general the Graphics card itself as well AMD drivers. However do not install the GPU nor AMD drivers back yet.
Secondly, if the crashes still occur. Will need to remove one physical ram stick from the motherboard and test to see if still occurs. If they do, put the removed stick back in and remove the other and test. If still happens. Then possibly a very badly corrupted operating system or driver installation and I would just go the route of full operating system reinstall. If still then, likely an faulty CPU or motherboard.
Right, I'll get on to that. I can't run the physical RAM test however since I only have one RAM stick installed. I do suspect a bad system installation myself, so I will try to run a re-install as well.
Hmm, have you reused one of the hard drive in another computer before. Sometimes you might run into issues with having driver for a different computer running on this computer.
Had that happen with my server computer when upgrading the motherboard (new chipset), and result in Windows crashing as soon as it boot and then try to repair itself with no success, but It could cause BSOD.
It could also be bad ram, which would kind of suck.
Check out my Animation Channel: https://www.youtube.com/channel/UCVy57y58kWOd6zRYJNGQkNg/feed
I've removed the GPU and the drivers and I'm currently operating the system based on the on-CPU Intel graphics unit. I'll post another report in two days. I will also try to run some games that don't rely on great graphical strength such as League of Legends to check if the system insists on crashing into RSoD, which I doupt.
EDIT: Alright, I've got some good news and some bad news. The good news are that the RSoDs did stop happening indeed. However, I cannot decide whether the problem lies in a problematic driver or a faulty GPU. The bad news are that the BSoDs didn't stop. The system has crashed twice thus far and the problem is reported as, yet again, MEMORY_MANAGEMET. Which means that I probably need to send the RAM stick back and request from the company to send me another one...
EDIT #2: I re-installed the GPU. Turns out the RSoDs aren't just gone yet. This time I managed to log a solid 40 minutes into Metro LL before my system broke down into a red screen crash. I do believe that the RSoD problem has to do with the GPU itself now rather than the drivers, since the RSoD got a 20 minute postpone after I plugged the GPU in, as I am either too dumb and can't connect 2 PCI-E 6 pin connectors to the GPU or the bus is faulty and it doesn't make solid contact with the motherboard. Then again, it might be the PSU but I'm quite certain that XFX PSUs are not problematic. And the blue screens continue, this time a new error occured though: FAULTY_HARDWARE_CORRUPTED_PAGE. Does this error point towards the GPU or the RAM though? That I don't know.
Both of my drives are brand new and straight out of the box. If it does turn out to be a bad RAM problem, then I will, unfortunately, have to get a new stick(s).