[eddablin]

Hi. Since I built my computer 3 years ago I have had random reboots with no visible BSOD (Despite unchecking auto restart). Sometimes they can happen 2 or 3 a day, sometimes once a month!

I have recently upgraded to win8 and it seems to be a lot more frequent now. Please can you have a look at the attached information and see if there is anything I need to try?

My system:

· Win 8 Pro 64bit (upgraded clean install from full retail win7)
· Intel Core i5 750
· Radeon HD 5750
· Gigabyte GA-P55A-UD4 (BIOS updated to F14)
· Corsair VX550W
· Intel X25-M 80GB SSD (boot drive)
· Samsung 500GB HD502HJ

 

[eddablin]

Re: Random reboots

Just ran a few passes on reach RAM stick and no luck. My RAM is G.Skill F3-10666CL7-2GBRH btw

 

[eddablin]

Re: Random reboots

So I got to stage 8 of a Prime95 test and decided to stop as I didnt want to overheat my processor cores which were getting up to 98 celsius (38 at idle) and it cut off as soon as I pressed stop all workers. Then I tried to replicate it and the same thing happened. WHy would destressing cause the reboot? Does this help diagnosis?

 

[eddablin]

Re: Random reboots

My dump file says this. Looks like a driver is worng. What do I do?

"C:\Windows\Minidump\020313-6676-01.dmp"

Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C000021A, {fffff8a000870ee0, 0, ffffffffc0000001, 973b3704b8}

----- ETW minidump data unavailable-----
Probably caused by : ntkrnlmp.exe ( nt!NtSetSystemPowerState+878 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: fffff8a000870ee0, String that identifies the problem.
Arg2: 0000000000000000, Error Code.
Arg3: ffffffffc0000001
Arg4: 000000973b3704b8

Debugging Details:
------------------

----- ETW minidump data unavailable-----

BUGCHECK_STR:  0xc000021a_0

ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error}  The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x).  The system has been shut down.

EXCEPTION_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error}  The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x).  The system has been shut down.

EXCEPTION_PARAMETER1:  fffff8a000870ee0

EXCEPTION_PARAMETER2:  0000000000000000

EXCEPTION_PARAMETER3:  ffffffffc0000001

EXCEPTION_PARAMETER4: 973b3704b8

ADDITIONAL_DEBUG_TEXT:  initial session process or

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  smss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80355b6f9de to fffff8035587d340

STACK_TEXT:  
fffff880`0314d828 fffff803`55b6f9de : 00000000`0000004c 00000000`c000021a fffff880`0336d540 fffffa80`068e8590 : nt!KeBugCheckEx
fffff880`0314d830 fffff803`55b63228 : 00000000`00000001 00000000`00000002 ffffffff`80000484 00000000`00000002 : nt!PopGracefulShutdown+0x29a
fffff880`0314d870 fffff803`5587c353 : fffffa80`03aa6040 00000000`00000000 00000000`00000001 fffff880`0314db01 : nt!NtSetSystemPowerState+0x878
fffff880`0314d9b0 fffff803`55881530 : fffff803`55e09db7 00000000`00000001 00000000`00000000 fffffa80`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0314db48 fffff803`55e09db7 : 00000000`00000001 00000000`00000000 fffffa80`00000000 fffff803`55806c70 : nt!KiServiceLinkage
fffff880`0314db50 fffff803`55cb44a3 : 00000000`00000000 fffff803`55b5f10c 00000000`00000000 00000000`00000002 : nt! ?? ::NNGAKEGL::`string'+0x3fcdb
fffff880`0314dc10 fffff803`5585d201 : fffffa80`03aa6040 00000000`00000000 00000000`00000002 fffff803`55886ac4 : nt!PopPolicyWorkerAction+0x63
fffff880`0314dc80 fffff803`558b5511 : fffff803`00000002 fffff803`5585d154 fffff803`55a99600 fffffa80`06778100 : nt!PopPolicyWorkerThread+0xad
fffff880`0314dcc0 fffff803`55824551 : 8b4819b2`0000480a 00000000`00000080 fffff803`558b53d0 fffffa80`03aa6040 : nt!ExpWorkerThread+0x142
fffff880`0314dd50 fffff803`55862dd6 : fffff803`55af8180 fffffa80`03aa6040 fffffa80`036f4040 fffffa80`03689040 : nt!PspSystemThreadStartup+0x59
fffff880`0314dda0 00000000`00000000 : fffff880`0314e000 fffff880`03148000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!NtSetSystemPowerState+878
fffff803`55b63228 cc              int     3

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!NtSetSystemPowerState+878

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  50ab0e64

BUCKET_ID_FUNC_OFFSET:  878

FAILURE_BUCKET_ID:  0xc000021a_0_nt!NtSetSystemPowerState

BUCKET_ID:  0xc000021a_0_nt!NtSetSystemPowerState

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: fffff8a000870ee0, String that identifies the problem.
Arg2: 0000000000000000, Error Code.
Arg3: ffffffffc0000001
Arg4: 000000973b3704b8

Debugging Details:
------------------

----- ETW minidump data unavailable-----

BUGCHECK_STR:  0xc000021a_0

ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error}  The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x).  The system has been shut down.

EXCEPTION_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error}  The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x).  The system has been shut down.

EXCEPTION_PARAMETER1:  fffff8a000870ee0

EXCEPTION_PARAMETER2:  0000000000000000

EXCEPTION_PARAMETER3:  ffffffffc0000001

EXCEPTION_PARAMETER4: 973b3704b8

ADDITIONAL_DEBUG_TEXT:  initial session process or

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  smss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80355b6f9de to fffff8035587d340

STACK_TEXT:  
fffff880`0314d828 fffff803`55b6f9de : 00000000`0000004c 00000000`c000021a fffff880`0336d540 fffffa80`068e8590 : nt!KeBugCheckEx
fffff880`0314d830 fffff803`55b63228 : 00000000`00000001 00000000`00000002 ffffffff`80000484 00000000`00000002 : nt!PopGracefulShutdown+0x29a
fffff880`0314d870 fffff803`5587c353 : fffffa80`03aa6040 00000000`00000000 00000000`00000001 fffff880`0314db01 : nt!NtSetSystemPowerState+0x878
fffff880`0314d9b0 fffff803`55881530 : fffff803`55e09db7 00000000`00000001 00000000`00000000 fffffa80`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0314db48 fffff803`55e09db7 : 00000000`00000001 00000000`00000000 fffffa80`00000000 fffff803`55806c70 : nt!KiServiceLinkage
fffff880`0314db50 fffff803`55cb44a3 : 00000000`00000000 fffff803`55b5f10c 00000000`00000000 00000000`00000002 : nt! ?? ::NNGAKEGL::`string'+0x3fcdb
fffff880`0314dc10 fffff803`5585d201 : fffffa80`03aa6040 00000000`00000000 00000000`00000002 fffff803`55886ac4 : nt!PopPolicyWorkerAction+0x63
fffff880`0314dc80 fffff803`558b5511 : fffff803`00000002 fffff803`5585d154 fffff803`55a99600 fffffa80`06778100 : nt!PopPolicyWorkerThread+0xad
fffff880`0314dcc0 fffff803`55824551 : 8b4819b2`0000480a 00000000`00000080 fffff803`558b53d0 fffffa80`03aa6040 : nt!ExpWorkerThread+0x142
fffff880`0314dd50 fffff803`55862dd6 : fffff803`55af8180 fffffa80`03aa6040 fffffa80`036f4040 fffffa80`03689040 : nt!PspSystemThreadStartup+0x59
fffff880`0314dda0 00000000`00000000 : fffff880`0314e000 fffff880`03148000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!NtSetSystemPowerState+878
fffff803`55b63228 cc              int     3

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!NtSetSystemPowerState+878

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  50ab0e64

BUCKET_ID_FUNC_OFFSET:  878

FAILURE_BUCKET_ID:  0xc000021a_0_nt!NtSetSystemPowerState

BUCKET_ID:  0xc000021a_0_nt!NtSetSystemPowerState

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: fffff8a000870ee0, String that identifies the problem.
Arg2: 0000000000000000, Error Code.
Arg3: ffffffffc0000001
Arg4: 000000973b3704b8

Debugging Details:
------------------

----- ETW minidump data unavailable-----

BUGCHECK_STR:  0xc000021a_0

ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error}  The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x).  The system has been shut down.

EXCEPTION_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error}  The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x).  The system has been shut down.

EXCEPTION_PARAMETER1:  fffff8a000870ee0

EXCEPTION_PARAMETER2:  0000000000000000

EXCEPTION_PARAMETER3:  ffffffffc0000001

EXCEPTION_PARAMETER4: 973b3704b8

ADDITIONAL_DEBUG_TEXT:  initial session process or

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  smss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80355b6f9de to fffff8035587d340

STACK_TEXT:  
fffff880`0314d828 fffff803`55b6f9de : 00000000`0000004c 00000000`c000021a fffff880`0336d540 fffffa80`068e8590 : nt!KeBugCheckEx
fffff880`0314d830 fffff803`55b63228 : 00000000`00000001 00000000`00000002 ffffffff`80000484 00000000`00000002 : nt!PopGracefulShutdown+0x29a
fffff880`0314d870 fffff803`5587c353 : fffffa80`03aa6040 00000000`00000000 00000000`00000001 fffff880`0314db01 : nt!NtSetSystemPowerState+0x878
fffff880`0314d9b0 fffff803`55881530 : fffff803`55e09db7 00000000`00000001 00000000`00000000 fffffa80`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0314db48 fffff803`55e09db7 : 00000000`00000001 00000000`00000000 fffffa80`00000000 fffff803`55806c70 : nt!KiServiceLinkage
fffff880`0314db50 fffff803`55cb44a3 : 00000000`00000000 fffff803`55b5f10c 00000000`00000000 00000000`00000002 : nt! ?? ::NNGAKEGL::`string'+0x3fcdb
fffff880`0314dc10 fffff803`5585d201 : fffffa80`03aa6040 00000000`00000000 00000000`00000002 fffff803`55886ac4 : nt!PopPolicyWorkerAction+0x63
fffff880`0314dc80 fffff803`558b5511 : fffff803`00000002 fffff803`5585d154 fffff803`55a99600 fffffa80`06778100 : nt!PopPolicyWorkerThread+0xad
fffff880`0314dcc0 fffff803`55824551 : 8b4819b2`0000480a 00000000`00000080 fffff803`558b53d0 fffffa80`03aa6040 : nt!ExpWorkerThread+0x142
fffff880`0314dd50 fffff803`55862dd6 : fffff803`55af8180 fffffa80`03aa6040 fffffa80`036f4040 fffffa80`03689040 : nt!PspSystemThreadStartup+0x59
fffff880`0314dda0 00000000`00000000 : fffff880`0314e000 fffff880`03148000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!NtSetSystemPowerState+878
fffff803`55b63228 cc              int     3

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!NtSetSystemPowerState+878

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  50ab0e64

BUCKET_ID_FUNC_OFFSET:  878

FAILURE_BUCKET_ID:  0xc000021a_0_nt!NtSetSystemPowerState

BUCKET_ID:  0xc000021a_0_nt!NtSetSystemPowerState

Followup: MachineOwner
---------

 

[writhziden]

Re: Random reboots

.dmp files are inconclusive, but due to the temperature of your processor, your processor overheating would be my first concern. Re-apply your thermal compound and check the processor and/or motherboard for bent pins by removing the processor and visually inspecting all pins that interface with it. Make sure to protect your system from static damage while checking the hardware and reapplying the thermal compound.

Thermal Paste and How To Use It | techPowerUp

Avoid Static Damage to Your PC | PCWorld​

Provide the following information about your hardware so we can check compatibility:

Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot. To upload all screenshots, it would be best to:

1. generate the images using the Snipping Tool,
2. go to where the images are saved,
3. right click in a blank area within the folder where the images are saved,
4. create a new folder,
5. name the folder CPUZ,
6. select all the images,
7. place the pointer over an image,
8. press and hold down the left mouse button and drag the image (all images should move with it),
9. drop the images into the CPUZ directory you created,
10. create a compressed (zipped) folder of CPUZ
11. upload the .zip file to the forums.

-----

 

[eddablin]

Re: Random reboots

CPUZ.zip uploaded.

It could be due to overheating of processor. However, I'm sure because it happens when the temp is less than 50 celsius. i.e. when I'm doing nothing.

I have upped my CPUand RAM voltages slightly and no reboots today so far. If I get one I shall try reapplying compound and inspecting processor.

 

[writhziden]

Re: Random reboots

RAM looks compatible. I would suggest the thermal management I mentioned before. Even if the system crashes at low temperatures, the CPU may have been damaged during a run when it did overheat and now is showing signs even at low temperatures. Also check for the bent pins (also mentioned in last post).



-----

 

[eddablin]

Re: Random reboots

I am not going to mark this as solved yet but since I have upped my voltages I have had no reboots over a week ago, even when trying to replicate post #3 which caused it before.
I'm not going to mark this as solved yet but its starting to look good. Thanks for everyones help so far.

 

[eddablin]

Okay this seemed to work well for me. Two weeks with no reboots and even stress testing it. My procedure was to look at an overclocking guide on youtube for my MOBO (and CPU), see how they increase their voltages and do the same but only ramp by one increment for my CPU and RAM voltages.

 

[writhziden]

Thank you for posting back your solution. :-}

I typically avoid giving advice for voltage changes since the inexperienced user is often uncomfortable making those changes. It also can mask problems rather than actually solving them, so continue to monitor the system. Voltage changes solving problems typically indicate mismatched or incompatible RAM, faulty hardware, or power management issues with the power supply.

I hope the problems are fixed, but if they return, you will have some clues to what the problem is. Best wishes all works as it should from here on. :-}


-----