Windows 10: After Upgrade from Windows 7 Frequent BSOD

Good Morning,


After an upgrade from Windows 7 we're experiencing 7-10 BSOD weekly. I don't see a way to attach the .DMP file so below is the output from Windbg. Any help would be greatly appreciated.




Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Users\Pam\Desktop\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 17134 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 17134.1.amd64fre.rs4_release.180410-1804

Machine Name:

Kernel base = 0xfffff800`bac02000 PsLoadedModuleList = 0xfffff800`bafb0150

Debug session time: Tue Mar 19 08:51:38.222 2019 (UTC - 4:00)

System Uptime: 0 days 23:15:04.921

Loading Kernel Symbols

....................................Page 2001c3233 too large to be in the dump file.

...........................

................................................................

....................................................

Loading User Symbols



Loading unloaded module list

................

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



Use !analyze -v to get detailed debugging information.



BugCheck 1E, {ffffffffc0000005, fffff800bac41e1a, 0, ffffffffffffffff}



Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+20a )



Followup: MachineOwner

---------



0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



KMODE_EXCEPTION_NOT_HANDLED (1e)

This is a very common bugcheck. Usually the exception address pinpoints

the driver/function that caused the problem. Always note this address

as well as the link date of the driver/image that contains this address.

Arguments:

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff800bac41e1a, The address that the exception occurred at

Arg3: 0000000000000000, Parameter 0 of the exception

Arg4: ffffffffffffffff, Parameter 1 of the exception



Debugging Details:

------------------





KEY_VALUES_STRING: 1





STACKHASH_ANALYSIS: 1



TIMELINE_ANALYSIS: 1





DUMP_CLASS: 1



DUMP_QUALIFIER: 401



BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804



SYSTEM_MANUFACTURER: Dell Inc.



SYSTEM_PRODUCT_NAME: XPS 8700



SYSTEM_SKU: 0x05B7



BIOS_VENDOR: Dell Inc.



BIOS_VERSION: A13



BIOS_DATE: 06/13/2018



BASEBOARD_MANUFACTURER: Dell Inc.



BASEBOARD_PRODUCT: 0KWVT8



BASEBOARD_VERSION: A02



DUMP_TYPE: 1



BUGCHECK_P1: ffffffffc0000005



BUGCHECK_P2: fffff800bac41e1a



BUGCHECK_P3: 0



BUGCHECK_P4: ffffffffffffffff



READ_ADDRESS: ffffffffffffffff



EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.



FAULTING_IP:

nt!KiProcessExpiredTimerList+20a

fffff800`bac41e1a 0fb64311 movzx eax,byte ptr [rbx+11h]



EXCEPTION_PARAMETER2: ffffffffffffffff



BUGCHECK_STR: 0x1E_c0000005_R



CPU_COUNT: 8



CPU_MHZ: d40



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 3c



CPU_STEPPING: 3



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



DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



PROCESS_NAME: System



CURRENT_IRQL: 2



ANALYSIS_SESSION_HOST: XPS8700



ANALYSIS_SESSION_TIME: 03-19-2019 10:05:31.0684



ANALYSIS_VERSION: 10.0.17763.132 amd64fre



EXCEPTION_RECORD: 00000000000013b3 -- (.exr 0x13b3)

Cannot read Exception record @ 00000000000013b3



LAST_CONTROL_TRANSFER: from fffff800bae42b3a to fffff800badac0a0



STACK_TEXT:

fffff800`bce5c7d8 fffff800`bae42b3a : 00000000`0000001e ffffffff`c0000005 fffff800`bac41e1a 00000000`00000000 : nt!KeBugCheckEx

fffff800`bce5c7e0 fffff800`badb494d : fffff800`baff3000 fffff800`bac02000 00058218`00953000 fffff803`d0b3f941 : nt!KiFatalExceptionHandler+0x22

fffff800`bce5c820 fffff800`bacc0b16 : fffff800`bce5c950 fffff800`bce5ce10 00000000`00000000 fffff800`bce5d728 : nt!RtlpExecuteHandlerForException+0xd

fffff800`bce5c850 fffff800`bacc2613 : fffff800`bce5d728 fffff800`bce5d470 fffff800`bce5d728 fffbd60e`be8a56f0 : nt!RtlDispatchException+0x416

fffff800`bce5cf40 fffff800`badbcd42 : 00000000`000013b3 00000000`00000000 00000001`00000000 00000000`00000000 : nt!KiDispatchException+0x1f3

fffff800`bce5d5f0 fffff800`badb949c : 00000000`00000000 00000000`00000006 00000000`00000003 00000000`00000016 : nt!KiExceptionDispatch+0xc2

fffff800`bce5d7d0 fffff800`bac41e1a : ffffd60e`be8a5658 ffffd60e`bc632250 fffff800`bce5db18 00000000`00000000 : nt!KiGeneralProtectionFault+0x2dc

fffff800`bce5d960 fffff800`bac40ca7 : 00000000`0000000e 00000000`00000000 00000000`00328c10 00000000`00000019 : nt!KiProcessExpiredTimerList+0x20a

fffff800`bce5da50 fffff800`badaf7da : 00000000`00000000 fffff800`b9cb4180 00000000`001a6570 fffff800`bb06c400 : nt!KiRetireDpcList+0x4c7

fffff800`bce5dc60 00000000`00000000 : fffff800`bce5e000 fffff800`bce58000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a





THREAD_SHA1_HASH_MOD_FUNC: 2540e173ffe9bc0a94c1bcec3f7e1a8d1652e15d



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f672c6e294eea2e2748695fb5596bb7e05999575



THREAD_SHA1_HASH_MOD: bc100a5647b828107ac4e18055e00abcbe1ec406



FOLLOWUP_IP:

nt!KiProcessExpiredTimerList+20a

fffff800`bac41e1a 0fb64311 movzx eax,byte ptr [rbx+11h]



FAULT_INSTR_CODE: 1143b60f



SYMBOL_STACK_INDEX: 7



SYMBOL_NAME: nt!KiProcessExpiredTimerList+20a



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: nt



IMAGE_NAME: ntkrnlmp.exe



DEBUG_FLR_IMAGE_TIMESTAMP: 5c7f858f



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 20a



FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!KiProcessExpiredTimerList



BUCKET_ID: 0x1E_c0000005_R_nt!KiProcessExpiredTimerList



PRIMARY_PROBLEM_CLASS: 0x1E_c0000005_R_nt!KiProcessExpiredTimerList



TARGET_TIME: 2019-03-19T12:51:38.000Z



OSBUILD: 17134



OSSERVICEPACK: 0



SERVICEPACK_NUMBER: 0



OS_REVISION: 0



SUITE_MASK: 784



PRODUCT_TYPE: 1



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal



OS_LOCALE:



USER_LCID: 0



OSBUILD_TIMESTAMP: 2019-03-06 03:32:15



BUILDDATESTAMP_STR: 180410-1804



BUILDLAB_STR: rs4_release



BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804



ANALYSIS_SESSION_ELAPSED_TIME: 5e4



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_nt!kiprocessexpiredtimerlist



FAILURE_ID_HASH: {093b081c-b5d0-9d69-5e7e-fa36d370a9d2}



Followup: MachineOwner

---------




Thanks - john

:)

 

Windows 7 Lover's Club: For Those Who Like Windows 7 As Opposed To Windows 8

Description:

• For anyone who likes Windows 7 as opposed to Windows 8 and wants to keep Windows 7 and not upgrade to Windows 8.
• Also for anyone who does not hate Windows 8 but refuses to upgrade because Windows 7 is perfect.

Requirements:

• Be human. Male or female will suffice.
• Love or Like Windows 7 much more than Windows 8.

To Join:

• Make a post.

Benefits:

• You will find true love one day.
• You have have a chance to get rich one day.
• You will have a chance for your dreams to come true one day.

 

Weird BSOD problem


Hi Everyone,

I have a weird BSOD problem which I cannot solve for a while(it persists still after upgrade to Windows 10 from Windows 7)

The main strange thing about this is that I get BSOD only after cold boot.
So it acts like this:

1. start PC.
2. Get to Windows Logo Screen
3. BSOD
4. Restart
5. Get to menu where I can try to repair or Start NormallyIf I Choose Repair, it will fail to repair and will try to restoreIf I Choose Start Normally, it will start OK, no BSOD, can work normally, games, browse internet, everything is normal.6. Shutdown PC
7. Next time when I start is all over again i.e. Go to Step 1

I have this problem for a while, so what I tried:

1. Another Windows 7
2. Another HDD
3. Only HDD connected
4. Changed RAM
5. Tried with built in GPU
6. Upgraded to Windows 10

Result is the same as above every time.

Please suggest what could be the cause.
Logs collected with DM_Log_Collector, attached.


Thank you

PS. This thread is a continuation of this one: Frequent multiple errors BSOD. Solved - Windows 7 Help Forums the only thing changed is Windows 10 now. instead of Windows 7. If that helps somehow.

 

Frequent BSOD since forced Windows 10 upgrade

Hi,

To assist you further, let me ask.

• 
  What are the changes or troubleshooting steps you have make prior to the issue?
  
• 
  What is the make and model of the computer?
  

I would suggest to refer the suggestion given by Zigzag3143, dated july 26, 2013.

Refer the link:
http://answers.microsoft.com/en-us/windows/wiki/windows_10-update/bsod-finding-and-fixing-them/1939df35-283f-4830-a4dd-e95ee5d8669d

For more information, refer the link.

https://support.microsoft.com/en-us/help/14238/windows-10-troubleshoot-blue-screen-errors

I hope the information is helpful and if the error still persists, we’ll be glad to assists you.

Thank you.