Share via

PC freezes and restarts

Anonymous
2023-02-03T02:09:25+00:00

Hi, so I played VALORANT yesterday and I think this is the first time it happened. I've fresh install windows at 18 Nov 2022. I never had any problems before while playing valorant. But suddenly while playing, the pc freezes and restarts. No BSOD, it just restarts. The lockscreen wallpaper is default and after checking the event viewer I saw the bugcheck event. Have done sfc, didn't find any corrupt file. Done the antivirus scan with malwarebytes, no virus detected. I think the only thing that is updating is, steam, and LG hub. After checking the event viewer/windows logs/system, I discovered that windows updating the defender automatically. But so far I haven't update any drivers. I don't know if this is caused by hardware or software, and I fear it might happened again.

I'll post the memory.dmp for further analysis. https://drive.google.com/file/d/1-hWsOmq0dg-pxxWceljJOv6rkogp2z2n/view?usp=sharing

I've done the analysis of the dump using winDbg and this is the result:

SYSTEM_SERVICE_EXCEPTION (3b)

An exception happened while executing a system service routine.

Arguments:

Arg1: 00000000c0000005, Exception code that caused the BugCheck

Arg2: fffff80626c203d4, Address of the instruction which caused the BugCheck

Arg3: ffffd08557666610, Address of the context record for the exception that caused the BugCheck

Arg4: 0000000000000000, zero.

Debugging Details:


KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 4374 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 4382 

Key  : Analysis.Init.CPU.mSec 

Value: 5156 

Key  : Analysis.Init.Elapsed.mSec 

Value: 266358 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 107 

Key  : WER.OS.Branch 

Value: vb\_release 

Key  : WER.OS.Timestamp 

Value: 2019-12-06T14:06:00Z 

Key  : WER.OS.Version 

Value: 10.0.19041.1 

FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80626c203d4

BUGCHECK_P3: ffffd08557666610

BUGCHECK_P4: 0

CONTEXT: ffffd08557666610 -- (.cxr 0xffffd08557666610)

rax=ffff3a430385fd00 rbx=0000000000000000 rcx=eac654e3923d0000

rdx=ffff8a03e0057000 rsi=00003583eee900e2 rdi=ffffd08557667880

rip=fffff80626c203d4 rsp=ffffd08557667010 rbp=ffffd08557667110

r8=00000000c0000271 r9=7fff8a0443709690 r10=7ffffffffffffffc

r11=ffffd08557667008 r12=0000000000000002 r13=0000000000000000

r14=0000000000000000 r15=0000000000000005

iopl=0 nv up ei pl zr na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246

nt!CmpDoParseKey+0x3d4:

fffff80626c203d4 0fb75642 movzx edx,word ptr [rsi+42h] ds:002b:00003583eee90124=????

Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: Discord.exe

STACK_TEXT:

ffffd08557667010 fffff80626c1f133 : ffffc0820000001c ffffd08557667360 ffffd08557667318 ffffc082291f9010 : nt!CmpDoParseKey+0x3d4

ffffd085576672b0 fffff80626c2321e : fffff80626c1ee01 0000000000000000 ffffc082291f9010 ffffd08557667a01 : nt!CmpParseKey+0x2c3

ffffd08557667450 fffff80626c4df8a : ffffc082291f9000 ffffd085576676b8 0000000000000040 ffffc0820aadcd20 : nt!ObpLookupObjectName+0x3fe

ffffd08557667620 fffff80626c4dd6c : 0000000000000000 0000000000000000 0000000000000000 ffffc0820aadcd20 : nt!ObOpenObjectByNameEx+0x1fa

ffffd08557667750 fffff80626c4d881 : 0000000012bce248 ffffd08557667ac0 0000000000000001 fffff80600000009 : nt!ObOpenObjectByName+0x5c

ffffd085576677a0 fffff80626c4d5af : 0000000077814660 0000000012bcfda0 0000000012bce220 0000000002000000 : nt!CmOpenKey+0x2c1

ffffd08557667a00 fffff80626a0e19a : ffffc0821fbac080 0000000000000006 ffffd08500000001 ffffc08200000000 : nt!NtOpenKeyEx+0xf

ffffd08557667a40 00007ffb9548f4b4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExitPico+0x3ef

0000000012bce1e8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffb`9548f4b4

SYMBOL_NAME: nt!CmpDoParseKey+3d4

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .cxr 0xffffd08557666610 ; kb

BUCKET_ID_FUNC_OFFSET: 3d4

FAILURE_BUCKET_ID: AV_nt!CmpDoParseKey

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5a306cbd-50b2-94f0-7c7d-ac7dea9041c4}

==SPECS==

OS: WINDOWS 10 PRO 64bit Version 22H2 Build 19045.2486

CPU: Intel i7 12700F

PSU: CORSAIR VS550

COOLER: COOLER MASTER HYPER 212 BLACK EDITION

CASE FANS: COOLER MASTER MASTERFAN HALO 120 3X

GPU: ASUS STRIX GTX1060 6G DC2O6G

MOBO: GIGABYTE Z690 GAMING X

RAM: 32 GB (2*16GB) TEAM DELTA T-CREATE

SSD/HDD:

C: SAMSUNG 980 PRO NVME SSD 1TB

D: SAMSUNG 860 PRO SATA 500GB

F: WD BLUE 1TB

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2023-02-03T02:48:42+00:00

    Hi, I’m Nicole, I’ll be happy to help you out today.

    Based on the dump file, The common file that causes the crash on the dump files is ntkrnlmp.exe which is an executable file associated with Windows Operating System. When Windows OS starts running on your computer, the programs that contain ntkrnlmp.exe will be executed and loaded into RAM and runs there as an NT Kernel & System process.

    The graphics card driver corruption is one of the main causes of the ntkrnlmp.exe blue screen. And if your computer has a virus or malware, that can bring you the ntkrnlmp.exe blue screen and prevent your PC from running as normal.

    The process that produces the crash is discord.exe. Try to uninstall Discord then do some system check.

    Method 1. Run system file checker.

    Open Powershell admin by right-clicking the Windows logo on the taskbar then click Windows Powershell (admin).

    On Powershell(admin), copy, paste, and enter each command below:

    sfc /scannow

    Dism /Online /Cleanup-Image /CheckHealth

    Dism /Online /Cleanup-Image /ScanHealth

    DISM /Online /Cleanup-Image /RestoreHealth

    Once done restart the PC and check.

    Method 2. Do clean boot:

    A “clean boot” starts Windows with a minimal set of drivers and startup programs so that you can determine whether a background program is interfering with your game or program.

    • In the search box on the taskbar, type msconfig and select System Configuration from the results.
    • On the Services tab of System Configuration, select Hide all Microsoft services, and then select Disable all.
    • On the Startup tab of System Configuration, select Open Task Manager.
    • Under Startup in Task Manager, for each startup item, select the item and then select Disable.
    • Close Task Manager.
    • On the Startup tab of System Configuration, select OK. When you restart the computer, it's in a clean boot environment.

    troubleshooting reference: https://support.microsoft.com/en-us/topic/how-t...

    Method 3. Run memory diagnostic tool: The memory diagnostic tool is a RAM test to check if there are any issues with RAM.

    • Press Windows key + R then type in mdsched.exe hit OK then restart the device.

    It is also recommended to use memtest86 and get at least 8 passes on it to be sure that the RAM is not the one causing the crash.

    Report back the results here afterward.

    Regards.

    0 comments No comments