Windows 10 Blue screen after every full night shutdown.

[SnowManBawb]

Hello.



So, I've had this problem with my pc for a while now and I just have no idea what the problem might be anymore. Ive tried posting on different sites but no one answered.



Here is the problem every time my pc has been shut down for longer then an hour, the next boot up will end up in a blue screen displaying a different error code each time. Here are is few ive seen.



IRQL_NOT_LESS_OR_EQUAL



KMODE_EXCEPTION_NOT_HANDLED


Sometimes the blue screen will happen 10 minutes after it has fully started sometimes right after i log in.



Here are my specs.

• CPU Intel Core i5-4440 3.10 GHZ
  
  
• Motherboard Asus H87M-PLUS
  
  
• RAM 2 4gb sticks of Corsair DDR3 vengance ram
  
  
• GPU Asus strix R9 390
  
  
• Case Fractal Design Core 1000
  
  
• Storage Samsung 850 evo 250 gb, 500GB Seagate ST500DM002, and a 1 tb external
  
  
• PSU Corsair CS750M

Ive also ran Windgb and here are the results based on the latest blue screen.
Here is what it came up with.


Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\021516-4484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.103.amd64fre.th2_release.160126-1819
Machine Name:
Kernel base = 0xfffff802`e1404000 PsLoadedModuleList = 0xfffff802`e16e2cf0
Debug session time: Mon Feb 15 15:26:13.882 2016 (UTC + 2:00)
System Uptime: 0 days 0:02:20.537
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

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

Use !analyze -v to get detailed debugging information.

BugCheck 139, {4, ffffe0018343dd60, ffffe0018343dcb8, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )

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

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

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000004, The thread's stack pointer was outside the legal stack
extents for the thread.
Arg2: ffffe0018343dd60, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffe0018343dcb8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.103.amd64fre.th2_release.160126-1819

SYSTEM_MANUFACTURER: ASUS

SYSTEM_PRODUCT_NAME: All Series

SYSTEM_SKU: All

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 0306

BIOS_DATE: 04/07/2013

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: H87M-PLUS

BASEBOARD_VERSION: Rev X.0x

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: 4

BUGCHECK_P2: ffffe0018343dd60

BUGCHECK_P3: ffffe0018343dcb8

BUGCHECK_P4: 0

TRAP_FRAME: 4b6778440205000e -- (.trap 0x4b6778440205000e)
Unable to read trap frame at 4b677844`0205000e

EXCEPTION_RECORD: 0000000000820003 -- (.exr 0x820003)
Cannot read Exception record @ 0000000000820003

CPU_COUNT: 4

CPU_MHZ: c1c

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: ESP_OUT_OF_RANGE

BUGCHECK_STR: 0x139

PROCESS_NAME: AvastSvc.exe

CURRENT_IRQL: 1

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 0000000000000004

WATSON_BKT_EVENT: BEX

ANALYSIS_SESSION_HOST: SNOWMANBAWB-PC

ANALYSIS_SESSION_TIME: 02-25-2016 23:47:29.0881

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

BAD_STACK_POINTER: ffffe0018343da38

LAST_CONTROL_TRANSFER: from fffff802e1550fe9 to fffff802e1546480

FAULTING_THREAD: 0000000000000000

STACK_TEXT:
ffffe001`8343da38 fffff802`e1550fe9 : 00000000`00000139 00000000`00000004 ffffe001`8343dd60 ffffe001`8343dcb8 : nt!KeBugCheckEx
ffffe001`8343da40 fffff802`e1551310 : 00000000`00000000 00000000`00000000 00000180`00000400 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffe001`8343db80 fffff802`e15504f3 : ffffc001`d3e6fba8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiFastFailDispatch+0xd0
ffffe001`8343dd60 fffff802`e155b157 : ffffe001`8343e650 ffffe001`8343ee00 00000000`00000000 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0xf3
ffffe001`8343def0 fffff802`e1408d81 : 00000000`00000000 ffffb000`5fe51000 65657246`00000002 0dc38236`36a514f1 : nt! ?? ::FNODOBFM::`string'+0x6357
ffffe001`8343df20 fffff802`e14075a8 : ffffe001`8343ee38 ffffe001`8343eb50 ffffe001`8343ee38 00000000`00000001 : nt!RtlDispatchException+0x71
ffffe001`8343e620 fffff802`e15510c2 : 00000000`00820003 00000000`00000000 4b677844`0205000e 0dc38236`36a526d1 : nt!KiDispatchException+0x144
ffffe001`8343ed00 fffff802`e154edc6 : ffffe001`8343ef90 ffffe001`834416a0 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
ffffe001`8343eee0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInvalidOpcodeFault+0x106


THREAD_SHA1_HASH_MOD_FUNC: 93ff434f099106b58fd2a86313b2862abc617562

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6ca9d805ff691236db9ae5a22166f7ed00e151d5

THREAD_SHA1_HASH_MOD: 9f457f347057f10e1df248e166a3e95e6570ecfe

FOLLOWUP_IP:
nt!KiFastFailDispatch+d0
fffff802`e1551310 c644242000 mov byte ptr [rsp+20h],0

FAULT_INSTR_CODE: 202444c6

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiFastFailDispatch+d0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 56a849a9

IMAGE_VERSION: 10.0.10586.103

STACK_COMMAND: ~0s ; kb

BUCKET_ID_FUNC_OFFSET: d0

FAILURE_BUCKET_ID: 0x139_MISSING_GSFRAME_STACKPTR_ERROR_nt!KiFastFailDispatch

BUCKET_ID: 0x139_MISSING_GSFRAME_STACKPTR_ERROR_nt!KiFastFailDispatch

PRIMARY_PROBLEM_CLASS: 0x139_MISSING_GSFRAME_STACKPTR_ERROR_nt!KiFastFailDispatch

TARGET_TIME: 2016-02-15T13:26:13.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-01-27 06:38:01

BUILDDATESTAMP_STR: 160126-1819

BUILDLAB_STR: th2_release

BUILDOSVER_STR: 10.0.10586.103.amd64fre.th2_release.160126-1819

ANALYSIS_SESSION_ELAPSED_TIME: 395

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x139_missing_gsframe_stackptr_error_nt!kifastfaildispatch

FAILURE_ID_HASH: {7b0febb5-6007-4f2b-3d38-57fef278d8d5}

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

3: kd> lmvm nt
Browse full module list
start end module name
fffff802`e1404000 fffff802`e1bd0000 nt (pdb symbols) C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\sym\ntkrnlmp.pdb\D03C5CF7862E48FE84A06333F1CFA5981\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\sym\ntoskrnl.exe\56A849A97cc000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Browse all global symbols functions data
Timestamp: Wed Jan 27 06:38:01 2016 (56A849A9)
CheckSum: 00727A26
ImageSize: 007CC000
File version: 10.0.10586.103
Product version: 10.0.10586.103
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 10.0.10586.103
FileVersion: 10.0.10586.103 (th2_release.160126-1819)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.

 

[SnowManBawb]

Along with my above suggestion you could also try checking your CPU with Intel's diagnostic test, (might as well you tried testing almost everything else):
Link Removed

Alright Ill try the hdd then this. Should I also try what @holdum333 said?

 

[holdum333]

Hi @SnowManBawb ! Please follow @kemical's advice! I have ran that on my PC and it didn't find any errors.
I just ran the free version and I'm not sure what all it tested. I'm sure it's like all the rest of the freebies, you have to pay for the pro version to test every thing.
I think that's 20$. Stay with @kemical. He's the best there is with BSOD. IMHO, you have some hardware problems!
I thinking out loud! Wondering if you crash while in a clean boot mode! I'll get out of the way now!
I sure wish you could get rid of MSE. That shouldn't be there. Only Windows Defender should be running as a AV!
https://support.microsoft.com/en-us/kb/929135

 

[kemical]

Alright Ill try the hdd then this. Should I also try what @holdum333 said?

Hi Bawb,
the Intel diagnostic should check your CPU fine but if you feel like running the app as another stress test then go ahead. Just watch your temps.

 

[SnowManBawb]

Hi Bawb,
the Intel diagnostic should check your CPU fine but if you feel like running the app as another stress test then go ahead. Just watch your temps.

The HDD didnt work so Ill try the stress programs i guess.

 

[holdum333]

Hi Bawb! See if you can run in the clean boot mode. It's different then the safe mode!
A clean boot is performed to start Windows by using a minimal set of drivers and startup programs. This helps eliminate software conflicts that occur when you install a program or an update or when you run a program in Windows 10, Windows 8.1, Windows 8, Windows 7, or Windows Vista. You may also troubleshoot or determine what conflict is causing the problem by performing a clean boot.
Why software conflicts occur?
When you start Windows by using a normal startup operation, several applications and services start automatically, and then run in the background. These programs include basic system processes, antivirus software, system utility applications, and other software that has been previously installed. These applications and services can cause software conflicts.

https://support.microsoft.com/en-us/kb/929135

 

[kemical]

The HDD didnt work so Ill try the stress programs i guess.

Hi Bawb,
when you say the HDD didn't work does that mean you unplugged the external drive but still got a bsod anyway?

If this is the case can you please post the dump file. If you get a new bsod at any point please upload the dump as the information is invaluable.

Lastly can you check the Task manager and look under 'Start-up' please. Just see what's starting alongside Windows and if possible take a screenshot.

 

[holdum333]

Hi! Very strange that BSOD only happens when booting up after being shut down. I now wondering about the power supply.
Sorry if that's been suggested before.
Great suggestion on the start ups @kemical ! I never thought of that. Could very well we causing a problem sense BSOD happens on Boot up! I'll get out of the way now.

 

[SnowManBawb]

Hi Bawb,
when you say the HDD didn't work does that mean you unplugged the external drive but still got a bsod anyway?

If this is the case can you please post the dump file. If you get a new bsod at any point please upload the dump as the information is invaluable.

Lastly can you check the Task manager and look under 'Start-up' please. Just see what's starting alongside Windows and if possible take a screenshot.

Oh no. I just meant It didnt fix it. sorry for not being specific.
And Ive removed most unwanted programs from the start up but here is a picture anyway
Link Removed

Hi! Very strange that BSOD only happens when booting up after being shut down. I now wondering about the power supply.
Sorry if that's been suggested before.
Great suggestion on the start ups @kemical ! I never thought of that. Could very well we causing a problem sense BSOD happens on Boot up! I'll get out of the way now.

Its most definitely not the power supply. As I mentioned before this has been happening for a long time and Ive swapped out parts of my PC over the course of this happening the only things that are the same since this started are the CPU, and motherboard.

 

[kemical]

Hi Bawb,
thank you for the update. I'll go back and look at some of your dump files again and see if anything crops up which looks familar now I know whats starting.
Can you run this diagnostic for the CPU? It's probably fine but better off checking:
Link Removed

Have you tried running the RAM in different slots?

Try uninstalling some of these apps like Game Ranger, Apple Push and Raptr. See if the bsod stops.

If you have any new dump files please post them.

 

[kemical]

MEMORY_CORRUPTOR:  STRIDE

I'm very suspicious of the Raptr gaming app especially as it 'optimises' your system. Your memory dumps have 'Stride' mentioned and this can mean an app is causing 'Stride corruption'. These issues occur as the data is going in/out of RAM and can also be caused by faulty RAM. One particular app famous for this is MSI's Afterburner.
So give it a try, if it isn't that it might be something else so it could be worth experimenting?

 

[SnowManBawb]

MEMORY_CORRUPTOR:  STRIDE

I'm very suspicious of the Raptr gaming app especially as it 'optimises' your system. Your memory dumps have 'Stride' mentioned and this can mean an app is causing 'Stride corruption'. These issues occur as the data is going in/out of RAM and can also be caused by faulty RAM. One particular app famous for this is MSI's Afterburner.
So give it a try, if it isn't that it might be something else so it could be worth experimenting?

I have high doubts that it is any kind of software cause Ive reinstalled windows multiple times changed from an hdd to a ssd and still had the problem. No mater what Ive had installed on the drive.

Here is the cpu test Link Removed

 

[kemical]

Hmm...ok

Well have you tried running the RAM in different slots or do you always use the same slots?

Can you run this diagnostic for the CPU? It's probably fine but better off checking:
Link Removed (sorry missed your result above)

Also if your using XMP or extreme memory profiles to clock your RAM to the correct speed try disabling it and set the speed manually.

You could also try tweaking the voltage on the RAM. Usually the voltage will top out at about 1.65v try upping it slightly but don't go past 1.7v.

 

[SnowManBawb]

Hmm...ok

Well have you tried running the RAM in different slots or do you always use the same slots?

Can you run this diagnostic for the CPU? It's probably fine but better off checking:
Link Removed (sorry missed your result above)

Also if your using XMP or extreme memory profiles to clock your RAM to the correct speed try disabling it and set the speed manually.

You could also try tweaking the voltage on the RAM. Usually the voltage will top out at about 1.65v try upping it slightly but don't go past 1.7v.

Ive used different ram configurations but when that failed as well i just left them in the recommended configs set by the manual.

There has been a thing with my ram in the bios that it shows the wrong speed. I googled this before and people said that that isnt a problem i just need to enable xmp and set it to the correct speed which ive done. Ive had the bios displaying the wrong speed for the longest time actually.
Dunno if that could be a problem.

 

[kemical]

Well RAM will always default to 1333mhz and you can use either XMP or manually set the correct speed, this is how the RAM comes. Even 1600MHz will default to 1333mhz.. So if your using XMP to get the correct speed try turning it off and set the speed manually.

So when you re-installed Windows did you actually test Windows running on it's own with just drivers installed and no applications?

Or did you install Windows followed by drivers and apps?

 

[holdum333]

HI! @kemical What do you think about a clean boot??

 

[kemical]

HI! @kemical What do you think about a clean boot??

Hmm well I'm trying to determine if it would be worth running something like that depending on how the op answers my questions above.

 

[SnowManBawb]

Well RAM will always default to 1333mhz and you can use either XMP or manually set the correct speed, this is how the RAM comes. Even 1600MHz will default to 1333mhz.. So if your using XMP to get the correct speed try turning it off and set the speed manually.

So when you re-installed Windows did you actually test Windows running on it's own with just drivers installed and no applications?

Or did you install Windows followed by drivers and apps?

ill try the manual ram speed.

and I tried a clean boot with out any apps installed or anything and it stilled bsod. so yeah >_<

 

[kemical]

ill try the manual ram speed.

Can you post the dump files too?

 

[holdum333]

Hi! I don't want to get in the way. But by asking questions, I learn a lot. The title of the thread is
Blue screen after every full night shutdown.
Wondering if a small crack in the MB could cause the BSOD and the crack heals it's self after power is on for awhile.
Maybe a leaky capacitor. Just some thoughts. Very strange only BSOD after being shut down. I'll get out of the way and watch the best BSOD tech @kemical do his thing! Might look for a bulging cap. One more question. Does it ever BSOD while running??
Thanks!

 

[kemical]

Trouble is Gary many motherboards now use solid caps but inspection of the motherboard is always worthwhile..

Bawb if manually setting the RAM speed doesn't help you could try upping the voltage slightly. If your Vengence RAM runs at 2400MHz then it's voltage will be about 1.65v. Try upping it slightly but don't go over 1.7v. Failing that, do you have access to any other memory or would it be possible to perhaps borrow some off a friend?

Try something for me please, when you next reboot, expecting a bsod, boot straight into safe mode and see if the blue screen still occurs. If it does don't forget to send me the dump.

I also notice you use a Logitech Keyboard and possibly a XTD kone mouse? (I own an XTD Kone and they are an awesome mouse, anyway I digress) Bawb have you tried removing either the mouse or the keyboard and seeing if the bsod still occurs? It's a long shot I know but if you have a spare k'board and mouse see if swapping them over makes any difference.