Getting BSOD while playing games (DOTA 2,Windows 10 ) help please

Cem___

Commendable
Feb 16, 2016
18
0
1,510
After getting windows 10 im getting bsod while playing some games (dota 2,stellaris) and my pc resets.I updated drives and checked my RAM and it seems there is no problem

What can cause this?

My crash dump is like this --------->








* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.306.amd64fre.th2_release_sec.160422-1850
Kernel base = 0xfffff802`a061b000 PsLoadedModuleList = 0xfffff802`a08f9cd0
Debug session time: Sun Jun 5 20:26:55.974 2016 (GMT+3)
System Uptime: 0 days 0:36:36.696
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
..............................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..........
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe00120c3c028, b6000000, 100153}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : hardware
 
Solution
your debugger need to have its symbol path set.
control+s then paste in
http://msdl.microsoft.com/download/symbols

save the workspace, exit the debugger and restart it again and load the memory dump.,

for this error you want to look at the system up time, if it is very small (under 15 seconds or so)
then your CPU was reset because the power to the CPU reset line dropped too low.
this tends to happen if a GPU pulls too much power from the PCI/e bus. The motherboard logic or the power supply can do this to protect the system.

if the uptime is longer, then you are more likely having a overheating problem.

in the debugger you can enter the command
!errrec (on the second parameter of the bugcheck)
like this in your case
!errrec...
your debugger need to have its symbol path set.
control+s then paste in
http://msdl.microsoft.com/download/symbols

save the workspace, exit the debugger and restart it again and load the memory dump.,

for this error you want to look at the system up time, if it is very small (under 15 seconds or so)
then your CPU was reset because the power to the CPU reset line dropped too low.
this tends to happen if a GPU pulls too much power from the PCI/e bus. The motherboard logic or the power supply can do this to protect the system.

if the uptime is longer, then you are more likely having a overheating problem.

in the debugger you can enter the command
!errrec (on the second parameter of the bugcheck)
like this in your case
!errrec ffffe00120c3c028

and it will show the reason the CPU called the bugcheck. (parameter 1=0 means the CPU shutdown the system)
(it would be parameter 1=4 if the PCI/e bus shut it down)

most likely a power problem was detected by the motherboard or PSU, it reset the CPU, then the power supply did not stop the CPU from restarting.
The CPU restarted before the power was stable, this allowed errors to occur in the CPU cache memory, the cpu memory controller detected the errors and the CPU called the bugcheck. This happens with some power supplies that fake the logic that indicates the power is ok.

you want to focus on the reason the CPU was reset in the first place rather than the bugcheck.
look for GPU or CPU overclocking and remove overclocking drivers, look for under rated power supplies.
look for overheated graphic cards, make sure the GPU fans are spinning up and at full speed if they are overheating.
for overheating, you also want to blow out dust from the GPU, PSU and CPU fans.



 
Solution