Windows 10: Computer randomly crashes, "Kernel address space is available, user address space may not...

Hi there,
I recently swapped my self built computer into another cabinet, after this - my computer seems to be randomly crashing while i am gaming/watching youtube and such. Its set up completely the same way, other than that i dont have the CPU fan plug plugged into CPUFAN but on CHA_FAN1, as i was getting CPU fan power errors, hence why its moved.

I am unsure as of why my computer might have started crashing like this now.

This is a self built computer with the following specs

Evga Geforce 1080 ftw,
Asus z170 Pro gaming
i7-7700k
Nzxt kraken x61 cooler.
The PSU i dont remember, but i dont think its the issue here.

Does anyone know why this might be happening?



I opened the error log in windbg and got the following;

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


Loading Dump File [C:\Windows\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 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`63c00000 PsLoadedModuleList = 0xfffff802`64048210
Debug session time: Sat Oct 19 01:50:40.253 2019 (UTC + 2:00)
System Uptime: 1 days 3:57:20.888
Loading Kernel Symbols
...............................................................
................................................................
.Page 408f3 not present in the dump file. Type ".hh dbgerr004" for details
.Page 5460a not present in the dump file. Type ".hh dbgerr004" for details
.............................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000008d`204e9018). Type ".hh dbgerr001" for details
Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`63dc1220 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff880e`2999f730=000000000000000a

Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Can't set dump file contexts
MachineInfo::SetContext failed - Thread: 000001FF8C7B3450 Handle: 8 Id: 8 - Error == 0x8000FFFF

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
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`63c00000 PsLoadedModuleList = 0xfffff802`64048210
Debug session time: Sat Oct 19 01:50:40.253 2019 (UTC + 2:00)
System Uptime: 1 days 3:57:20.888
Loading Kernel Symbols
...............................................................
................................................................
.Page 408f3 not present in the dump file. Type ".hh dbgerr004" for details
.Page 5460a not present in the dump file. Type ".hh dbgerr004" for details
.............................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000008d`204e9018). Type ".hh dbgerr001" for details
Loading unloaded module list
................
nt!KeBugCheckEx:
fffff802`63dc1220 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff880e`2999f730=000000000000000a

This is from the event viewer

- System
- Provider
[ Name] Microsoft-Windows-WER-SystemErrorReporting
[ Guid] {ABCE23E7-DE45-4366-8631-84FA6C525952}
[ EventSourceName] BugCheck
- EventID 1001
[ Qualifiers] 16384
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2019-10-18T23:52:28.266834100Z
EventRecordID 3968
Correlation
- Execution
[ ProcessID] 0
[ ThreadID] 0
Channel System
Computer DESKTOP-CNRJB3O
Security
- EventData
param1 0x0000000a (0xffffffffffffffd1, 0x00000000000000ff, 0x00000000000000ff, 0xfffff80263dd2beb)
param2 C:\WINDOWS\MEMORY.DMP
param3 03ef3b71-ac7d-4cac-8710-5c7eca45f384

:)

 

Large Address Aware

The address space is 4 GB. By default user space gets 2 GB and kernel space gets 2 GB. All the /3GB switch does is change this layout. Phil, you don't make sense.

 

Large Address Aware

I'm sorry, but Microsoft, who writes the code for their popular operating system "Says a lot of things...some of which are even true."

Implying they don't know the flags the kernel uses and can use for hardware access and resource management, in the operating system they wrote........ interesting thoughts you have there, but they are wrong. Please don't thread crap, I fail to see the software or anything you have written or done other than writing incorrect posts here. Please stop.

https://msdn.microsoft.com/en-us/library/windows/hardware/ff542202(v=vs.85).aspx

"
increaseuserva Megabytes

Specifies the amount of memory, in megabytes, for user-mode virtual address space.

On 32-bit editions of Windows, applications have 4 gigabyte (GB) of virtual address space available. The virtual address space is divided so that 2 GB is available to the application and the other 2 GB is available only to the system.

The 4-gigabyte tuning feature, enabled with the increaseuserva option, allows you to increase the virtual address space that is available to the application up to 3 GB, which reduces the amount available to the system to between 1 and 2 GB. The BCEdit /set increaseuserva Megabytes command can specify any value between 2048 (2 GB) and 3072 (3 GB) megabytes in decimal notation. Windows uses the remaining address space (4 GB minus the specified amount) as its kernel-mode address space.

See 4-Gigabyte Tuning (Windows) for additional information about this feature."

Merely using the /3GB switch on XP enables the system to manage the memory up to the 3GB boundary.


"
Windows Server 2003 and earlier: To enable 4GT, add the /3GB switch to the Boot.ini file. The /3GB switch is supported on the following systems:

• Windows Server 2003
• Windows XP Professional

In Windows Vista X86 and later you could specify how much to allocate to the user space, but by this point X64 had become native and or applications were large address aware, or could be set to large address aware by other programs.

 

Large Address Aware

The article is talking about how the OS is handling virtual to physical memory mappings - it takes up address space. By lowering the size of the kernel space, you lower how much physical memory the OS can handle.