New
#1
Computer randomly restarting while playing gaming
Hi first time posting here, hope I'm posting in the right section. Lately for the past 2ish weeks my computer would randomly restart while gaming, mainly while playing DayZ Standalone. I have some WhoCrashed reports from my last crash. I don't get BSOD's, my computer just restarts and says it recovered from an unexpected shutdown once I'm logged into my account.
On Mon 2/17/2014 8:22:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021714-15880-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
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 Mon 2/17/2014 4:23:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021614-16317-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x56F06)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
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.
-----
These are the two that I get in my reports. Not sure what to do so I came here in hopes of getting some help and learning something new. Sorry about the title, was really tired when I made this.
Last edited by RawNG; 17 Feb 2014 at 16:11.