Windows 10: recently upgraded to windows 10 BSOD issues

I am getting random BSOD's even just having a browser open seems to always be "system_service_exception"


Microsoft R Windows Debugger Version 10.0.18362.1 AMD64
Copyright c Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\050120-15453-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 18362 MP 8 procs Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`58a00000 PsLoadedModuleList = 0xfffff802`58e48150
Debug session time: Fri May 1 11:47:38.137 2020 UTC - 4:00
System Uptime: 0 days 1:32:30.842
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION 3b
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80258a8c9ce, Address of the instruction which caused the bugcheck
Arg3: ffffd68075d79930, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER: To be filled by O.E.M.

SYSTEM_PRODUCT_NAME: To be filled by O.E.M.

SYSTEM_SKU: SKU

SYSTEM_VERSION: To be filled by O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 2501

BIOS_DATE: 04/07/2014

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: M5A99FX PRO R2.0

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80258a8c9ce

BUGCHECK_P3: ffffd68075d79930

BUGCHECK_P4: 0

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

FAULTING_IP:
nt!KxWaitForLockOwnerShip+e
fffff802`58a8c9ce 48890a mov qword ptr [rdx],rcx

CONTEXT: ffffd68075d79930 -- .cxr 0xffffd68075d79930
rax=0000000000000000 rbx=ffff8f86164eda40 rcx=ffff8f86164eda40
rdx=8a00000000000000 rsi=0000000000000000 rdi=fffff80258e458e0
rip=fffff80258a8c9ce rsp=ffff8f86164ed9e0 rbp=ffffa3037eaef080
r8=4000000000000404 r9=0000000000000000 r10=0000000000000000
r11=ffffa3036f5fde10 r12=000000001fe3fd18 r13=007ffffffffffef5
r14=0000000000000001 r15=ffffa3037eaef080
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!KxWaitForLockOwnerShip+0xe:
fffff802`58a8c9ce 48890a mov qword ptr [rdx],rcx ds:002b:8a000000`00000000=????????????????
Resetting default scope

BUGCHECK_STR: 0x3B_c0000005

CPU_COUNT: 8

CPU_MHZ: 10ee

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

BLACKBOXBSD: 1 !blackboxbsd


BLACKBOXNTFS: 1 !blackboxntfs


BLACKBOXPNP: 1 !blackboxpnp


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: FiveM_GTAProcess.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: ANDREW-PC

ANALYSIS_SESSION_TIME: 05-01-2020 12:12:23.0549

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

BAD_STACK_POINTER: ffffd68075d78ff8

LAST_CONTROL_TRANSFER: from fffff80258b0f459 to fffff80258a8c9ce

STACK_TEXT:
ffff8f86`164ed9e0 fffff802`58b0f459 : 00000000`00000004 ffff8f86`164eda00 00000000`00000004 fffffccd`fff46b5f : nt!KxWaitForLockOwnerShip+0xe
ffff8f86`164eda10 fffff802`58f972f8 : ffff8f86`164edb80 00000000`00000003 ffffa303`7d814270 ffffa303`7d814270 : nt!ExReleaseResourceLite+0x119
ffff8f86`164eda70 fffff802`58feeed3 : ffffa303`7d814270 ffff8f86`00000003 00000001`415a4fe0 00000000`00000003 : nt!PopReleasePolicyLock+0x18
ffff8f86`164edaa0 fffff802`58bd3c18 : ffffa303`7eaef080 00000000`00000000 ffff8f86`80000002 00000000`00000000 : nt!NtSetThreadExecutionState+0x143
ffff8f86`164edb00 00007ffe`7c61f544 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`1fe3fcd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`7c61f544


THREAD_SHA1_HASH_MOD_FUNC: ba56c60ea14831cad2afa172482b72551d2445fa

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: dfa4c4514ac890e38e42772c7d3a4f3daf13aa17

THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84

FOLLOWUP_IP:
nt!KxWaitForLockOwnerShip+e
fffff802`58a8c9ce 48890a mov qword ptr [rdx],rcx

FAULT_INSTR_CODE: c70a8948

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KxWaitForLockOwnerShip+e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.18362.815

STACK_COMMAND: .cxr 0xffffd68075d79930 ; kb

BUCKET_ID_FUNC_OFFSET: e

FAILURE_BUCKET_ID: 0x3B_c0000005_STACKPTR_ERROR_nt!KxWaitForLockOwnerShip

BUCKET_ID: 0x3B_c0000005_STACKPTR_ERROR_nt!KxWaitForLockOwnerShip

PRIMARY_PROBLEM_CLASS: 0x3B_c0000005_STACKPTR_ERROR_nt!KxWaitForLockOwnerShip

TARGET_TIME: 2020-05-01T15:47:38.000Z

OSBUILD: 18362

OSSERVICEPACK: 815

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: unknown_date

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 4aab

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_c0000005_stackptr_error_nt!kxwaitforlockownership

FAILURE_ID_HASH: {d727c4af-27c7-04e4-888d-ab8b74fdce06}

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

6: kd> lmvm nt
Browse full module list
start end module name
fffff802`58a00000 fffff802`594b7000 nt pdb symbols G:\winSDK\Debuggers\x64\sym\ntkrnlmp.pdb\C96C63D110EDC5BE180C2291321BAAF21\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: G:\winSDK\Debuggers\x64\sym\ntoskrnl.exe\81E3FD80ab7000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 81E3FD80 This is a reproducible build file hash, not a timestamp
CheckSum: 0097EF5E
ImageSize: 00AB7000
File version: 10.0.18362.815
Product version: 10.0.18362.815
File flags: 0 Mask 3F
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 10.0.18362.815
FileVersion: 10.0.18362.815 WinBuild.160101.0800
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.

:)

 

Windows 10 upgrade problem, no input accepted

I really hate having to come here and ask for help, but I really am stumped. It hurts my geek pride. I have a PC with fairly modern hardware in it. It has a p8p67 pro in it. I have tried upgrading windows 10 on it twice now. Both times I have had the same result.

After windows finishes upgrading it goes to the log in/set up screen. I can't do anything. No keyboard or mouse input is accepted.

I will list some, or hopefully all, of the troubleshooting steps I have tried:

• Move keyboard and mouse to different USB ports.
• Try different keyboard or mouse.
• Restart computer, repeatedly.
• Google for related issues.
• Update Bios, because why not.
• Create boot media and revert to windows 7.

The windows 10 system restore boot media works fine with keyboard and mouse. All USB ports work in windows 7. I don't know what is wrong. I suspect that windows 10 is lacking a driver of some sort, but since the computer accepts no input I have no way of checking for which driver let alone installing it.

Please help me figure this out. If I have to revert back to windows 7 again, I am not going to get it upgraded to windows 10. Thank you in advanced.

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

Recent BSoD Issues.

Hi,

There are several reasons why you are experiencing a BSOD issue with your computer. These may include an outdated device driver or corruption within your system files. Answering the following questions may help us in uncovering the underlying cause of the
issue:

• Were there any changes made on your computer prior to the issue?
• Were you able to install all pending updates on your computer?
• What troubleshooting steps have you already performed?

Moreover, we recommend following the steps provided from this article in order to troubleshoot the issue.

Let us know if you need further help.