PC keeps restarting

I’m running into a bit of a headache with my PC—it keeps rebooting itself right in the middle of gaming sessions. I picked this machine up just two months ago, so it’s practically brand new, yet here we are. For context, the specs are an Intel Core i7-4770K, an NVIDIA GeForce GTX 750 Ti, 8GB of RAM, and so on. My first instinct was that it might be a dust issue, so I gave everything a thorough cleaning—no luck there. I also tried running some temperature monitoring software, but according to the readings, nothing is overheating. Honestly, I'm at a total loss—any ideas on what could be causing this?

Douglas Ramos5 said:I’m running into a frustrating issue with my PC where it just decides to reboot itself right in the middle of a gaming session. I actually just picked this rig up about two months ago, so everything should be pretty fresh, but it's acting up. For context, my specs include an Intel Core i7-4770K, an NVIDIA GeForce GTX 750 Ti, 8GB of RAM, and so on. At first, I thought maybe it was just a dust buildup issue, so I spent some time cleaning everything out thoroughly, but that didn't solve anything. I even went ahead and installed some temperature monitoring software, but according to the readings, nothing seems to be overheating. I'm honestly at a bit of a loss here, so if anyone has any ideas on what might be causing this, I’d really appreciate the help.

Since you're running that processor, you definitely aren't using a laptop, so I'm not quite sure why you posted this under the portable computers section. Beyond that, have you made sure your drivers are fully updated and that you direct x have 11.? Also, where did you get the game—was it an official purchase or a torrent download—and which specific game are we talking about?

Look, it isn't a laptop issue—the games are all legitimate copies, though I haven't messed around with the drivers yet. It’s a bit strange, actually; this only seems to happen when I'm running official titles, whereas the pirated ones run without a hitch. Is that just some weird coincidence, or is there something more to it?

I'm running into this issue with both League of Legends and FIFI14—and I definitely direct x have 11.

I tried running a pirated copy of NBA2K14, and the damn thing just refused to reboot ever since.

Could be a weak PSU or just crappy drivers. Is it rebooting or straight up crashing? Just grab Whocrashed, see what it digs up, and dump the results here...

Here is the path to the crash dump directory: C:\Windows\Minidump

It appears that crash dumps have been enabled on your machine.

On Sun 1/5/2014 2:18:17 PM GMT, my system suffered a total crash.
The crash dump file can be found here: C:\Windows\Minidump\010514-14523-01.dmp
It looks like the culprit behind this mess was most likely the following module: ntoskrnl.exe (nt+0x4A63CC)—just my luck, really.
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007E2E038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
The file path in question is C:\Windows\system32\ntoskrnl.exe.
Microsoft Corporation description : NT kernel & system bug—it's all part of the package when you're dealing with the Microsoft Corporation operating system.
Microsoft Corporation
Microsoft Corporation description : NT kernel & system bug
Bug check description: This specific error code signals that a fatal hardware failure has occurred—essentially, things have gone south at the physical level. This particular bug check relies on the error data supplied by the Windows Hardware Error Architecture (WHEA).
It seems highly probable that we are looking at a hardware failure here—an issue that could very well stem from thermal instability.
The crash occurred within the Windows kernel. It's highly probable—though impossible to say for certain right now—that we're looking at a conflict triggered by some other unidentified driver.

The system went down on Thu 1/2/2014 at 6:05:15 PM GMT—another inevitable failure.
Crash dump file located at: C:\Windows\Minidump\010214-19624-01.dmp
It looks like we’ve pinpointed the culprit—this mess was likely triggered by the following module: ntoskrnl.exe (nt+0x4A63CC).
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007D48038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
The file path in question: C:\Windows\system32\ntoskrnl.exe
The product in question: Microsoft Corporation operating system.
Microsoft Corporation
Microsoft Corporation description : NT kernel & system bug
Bug check description: This specific error indicates that a fatal hardware failure has taken place. The diagnostic information for this crash is pulled directly from the data provided by the Windows Hardware Error Architecture (WHEA).
It’s highly probable that we're looking at a hardware failure here—though, one could easily argue that a thermal issue is the underlying culprit.
The crash occurred within the Windows kernel—it seems. It’s highly probable that some other unidentified driver is pulling the rug out from under the system, though we can't pinpoint the culprit just yet.

Your computer suffered a total crash on Wed 1/1/2014 3:54:53 PM GMT.
Crash dump file: C:\Windows\Minidump\010114-15178-01.dmp
It’s highly probable that this issue stems from the following module: ntoskrnl.exe (nt+0x4A63CC).
Bugcheck code: 0x124 (0x0, 0xFFFFFA80079EE8F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
C:\Windows\system32\ntoskrnl.exe
Microsoft Corporation's operating system—specifically the Microsoft® Windows® Operating system—remains a cornerstone of the digital landscape, though its reliability often feels like a question mark. It’s a complex beast, isn't it? One moment you're productive, and the next, you're staring at a screen wondering where it all went wrong. Regardless of how much we complain about the quirks, it's the platform most of us simply have to live with.
Microsoft Corporation
Microsoft Corporation description : NT kernel & system bug
Bug check description: This specific error signals that a fatal hardware failure has taken place. The diagnostic information utilized here is pulled directly from the data provided by the Windows Hardware Error Architecture (WHEA).
It looks like we’re staring down a hardware failure here—most likely a physical component acting up. There is also a strong possibility that we are dealing with a thermal issue—essentially, things are simply getting too hot to function properly.
The system failure occurred deep within the Windows kernel—it seems. It is entirely possible that we are looking at a conflict triggered by an unidentified driver, though pinpointing the culprit remains out of reach for the moment.

Your computer crashed on Mon 12/30/2013 8:23:32 PM GMT.
crash dump file: C:\Windows\Minidump\123013-20638-01.dmp
It looks like the culprit here is likely this specific module: ntoskrnl.exe (nt+0x4A63CC).
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007C924C8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
C:\Windows\system32\ntoskrnl.exe
Microsoft Corporation description : NT kernel & system bug — an interesting way to look at the Microsoft Corporation operating system, isn't it? It really makes you wonder about the stability we've come to expect from such a massive entity.
Microsoft Corporation
Microsoft Corporation description : NT kernel & system bug
Bug check description: This specific error signals that a fatal hardware failure has taken place. Essentially, this bug check relies on the error data supplied by the Windows Hardware Error Architecture (WHEA).
It’s highly probable that we're looking at a hardware failure here—nothing more, nothing less. There is also the distinct possibility that this stems from a thermal issue—overheating being the silent killer of most components.
The crash occurred within the Windows kernel—it seems. It’s highly probable that some other unidentified driver is pulling the rug out from under the system, though we can't pin down the specific culprit just yet.

Your computer suffered a total crash on Tue 12/17/2013 12:48:44 AM GMT.
Crash dump file: C:\Windows\Minidump\121713-14632-01.dmp
It looks like the culprit here is the following module: ntoskrnl.exe (nt+0x4A63CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007C88038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft Corporation description : NT kernel & system
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This specific bug check points to a fatal hardware failure—essentially, the system has hit a wall. It relies on error data reported by the Windows hardware ERROR Architecture (WHEA).
We are likely looking at a physical hardware malfunction—possibly a thermal issue where things are getting too hot.
The crash occurred within the Windows kernel; there is also a chance an unidentified driver is pulling the plug.

Your system went down on Fri 12/13/2013 12:39:16 PM GMT
crash dump file: C:\Windows\Minidump\121313-13759-01.dmp
The issue appears to stem from this module: ntoskrnl.exe (nt+0x4A63CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007D348F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft Corporation description : NT kernel & system
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a 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.

Your system went down on Tue 12/10/2013 1:01:26 PM GMT
crash dump file: C:\Windows\Minidump\121013-12885-01.dmp
The following module seems responsible: ntoskrnl.exe (nt+0x4A63CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007BD1038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft Corporation description : NT kernel & system
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a 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.

Your system went down on Sun 11/10/2013 12:00:17 AM GMT
crash dump file: C:\Windows\Minidump\111013-15646-01.dmp
The probable cause is the following module: ntoskrnl.exe (nt+0x4A63CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007D94038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft Corporation description : NT kernel & system
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a 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.

The Windows kernel keeps crashing at the exact same spot. Could be a failing hard drive, could be some buggy driver... 🤷 anyone here dealt with this error before? Just hang tight and we'll see...

I went ahead and installed the latest drivers, but—surprise, surprise—it’s the exact same story.