Navigation section

Windows 10 BSOD Memory management

Pep

Pep

New Member
Joined
Sep 4, 2020
Messages
5
Hello, I'been checking on this forum about how to fix bsod Memory management issue, I tried everything, I pass memtest more than 8 hours, no one error coming up, my system is Windows 10 64bits, version 1909

My specs are Cpu AMD threadripper 1950x

Nvidia Quadro P4000

48Gb Ram

I'm using my PC as workstation.

I've got this dump file, I hope someone could guide me what is wrong.

Thank you.

Luis.

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


Loading Dump File [C:\Users\Pep\Desktop\090320-9203-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:N-SymCache*Symbol information
Symbol search path is: SRV*C:N-SymCache*Symbol information
Executable search path is:
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE_TRANSITION ***
*** ***
*************************************************************************
Windows 10 Kernel Version 18362 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff806`48800000 PsLoadedModuleList = 0xfffff806`48c480f0
Debug session time: Thu Sep 3 00:11:56.130 2020 (UTC + 1:00)
System Uptime: 0 days 16:30:26.471
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE_TRANSITION ***
*** ***
*************************************************************************
Loading Kernel Symbols
.
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
DBGHELP: c:n-symcache*Symbol information is not a valid store
..............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
..............

************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
For analysis of this file, run !analyze -v
21: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: fffff6bffee98000
Arg3: 0000000010000000
Arg4: 0000000000000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_EPROCESS ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KTHREAD ***
*** ***
*************************************************************************
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
DBGHELP: C:N-SymCache*Symbol information is not a valid store
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 0

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on PEP

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 0

Key : Analysis.Memory.CommitPeak.Mb
Value: 55

Key : Analysis.System
Value: CreateObject


ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

WRONG_SYMBOLS_TIMESTAMP: 7530c6d3

WRONG_SYMBOLS_SIZE: ab7000

FAULTING_MODULE: fffff80648800000 nt

BUGCHECK_CODE: 1a

BUGCHECK_P1: 41792

BUGCHECK_P2: fffff6bffee98000

BUGCHECK_P3: 10000000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR: ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffff9e83`cc88ab68 fffff806`48a0f56a : 00000000`0000001a 00000000`00041792 fffff6bf`fee98000 00000000`10000000 : nt+0x1c23c0
ffff9e83`cc88ab70 00000000`0000001a : 00000000`00041792 fffff6bf`fee98000 00000000`10000000 00000000`00000000 : nt+0x20f56a
ffff9e83`cc88ab78 00000000`00041792 : fffff6bf`fee98000 00000000`10000000 00000000`00000000 fffff806`00000000 : 0x1a
ffff9e83`cc88ab80 fffff6bf`fee98000 : 00000000`10000000 00000000`00000000 fffff806`00000000 ffffa50e`01fe3980 : 0x41792
ffff9e83`cc88ab88 00000000`10000000 : 00000000`00000000 fffff806`00000000 ffffa50e`01fe3980 ffff9e83`cc88b180 : 0xfffff6bf`fee98000
ffff9e83`cc88ab90 00000000`00000000 : fffff806`00000000 ffffa50e`01fe3980 ffff9e83`cc88b180 ffff9a00`00000000 : 0x10000000


SYMBOL_NAME: ONE_BIT

MODULE_NAME: hardware

IMAGE_NAME: memory_corruption

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

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

21: kd> lmvm hardware
Browse full module list
start end module name
 


Sort by date Sort by votes
Hi Luis,

do you still require help?

If you could post some actual dump files that would help too.

Also is your system bios the latest version?
 


Upvote 0 Downvote
kemical said:
Hi Luis,

do you still require help?

If you could post some actual dump files that would help too.

Also is your system bios the latest version?
Click to expand...
Hi Kemical, yes I still need help, so I already paste my dump file in the original post, I just attached here as well, please take a look, Thank you
 


Attachments

Upvote 0 Downvote
Hi,

looks like the app that tripped the bsod was from 3DConnexion which I think is a mouse/peripheral driver.

You could try either removing the driver if it's no longer used or updating it to a later version, if available.

3Dconnexion UK - SpaceMouse, CadMouse, Drivers

Post back if this is of no help.
 


Upvote 0 Downvote
Solution
Hmmm I thought , the issue caming from any of my memory stick, I will check the driver of 3Dconnexion, also my main SSD "C" where the system is installed, it's 98% health, it could produce any issue ? thank you.
 


Attachments

  • 98%.webp
    98%.webp
    75 KB · Views: 378
Upvote 0 Downvote
I updated to the latest driver, will see if the issue coming again
 


Upvote 0 Downvote
Pep said:
Hmmm I thought , the issue caming from any of my memory stick, I will check the driver of 3Dconnexion, also my main SSD "C" where the system is installed, it's 98% health, it could produce any issue ? thank you.
Click to expand...
As it's a bugcheck of 1a then it is possibly related to RAM but this bugcheck can also be caused by drivers.

98% Health sounds fine, in fact i think my SSD is at 98% and I doubt it's your SSD causing the issue.

Hope the new driver helps but if not please post back..
 


  • Like
Reactions: Pep
Upvote 0 Downvote
Thank you again, in the coming days ,I'll force the hardware to try reproduce any BSDO, if the issue is still in there, I will headed to the shop.
I'll post here the updates.
Thank you.
 


Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

Morrison1995
  • Solved
Help Deciphering DPC_WATCHDOG_VIOLATION Error After System Crash
Replies
1
Views
669
ChatGPT
ChatGPT
Anthony96
  • Solved
Windows 10 bsod memory management when trying to install flight sim 2020
Replies
4
Views
3K
ChatGPT
ChatGPT
GuyPink
  • Question Question
Windows 10 PC issues restart/freeze sound on but keyboard and monitor frozen
Replies
1
Views
1K
GuyPink
GuyPink
M
  • Solved
Windows 7 Event 41 kernel power 63
2
Replies
26
Views
5K
mediator
M
K
  • Solved
Windows 10 BSOD Memory Management / KNode Exception Not Handled
2
Replies
25
Views
7K
kemical
kemical
Back
Top