Windows 10: How to fix my Blue Screen . plz help!

computer boots fine runs without any problems but sometimes runs into a blue screen, Ive gotten about 4 blue screens in the past 3 days first one was a SYSTEM_SERVICE_EXCEPTION the last three were IRQL_NOT_LESS_OR_EQUAL this is the dumb file form the last crash.


This is a new PC I just built.


MSI tomahawk b450

Ryzen 5 3600

AMD RX 5700XT

corsair vengeance 16gb ddr4 3200mhz





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


Loading Dump File [C:\Windows\minidump\$R28UV9R.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff806`54200000 PsLoadedModuleList = 0xfffff806`54646490
Debug session time: Wed Aug 14 22:18:44.481 2019 (UTC - 7:00)
System Uptime: 0 days 20:40:18.147
Loading Kernel Symbols
...............................................................
................................................................
.............................................................
Loading User Symbols
Loading unloaded module list
..............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`543bfcc0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffdf87`e896f830=000000000000000a
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000ffff8087, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80654242cb6, address which referenced memory

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 9

Key : Analysis.Elapsed.Sec
Value: 27

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


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: Micro-Star International Co., Ltd

SYSTEM_PRODUCT_NAME: MS-7C02

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

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1.A0

BIOS_DATE: 07/22/2019

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd

BASEBOARD_PRODUCT: B450 TOMAHAWK (MS-7C02)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

BUGCHECK_P1: ffff8087

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80654242cb6

READ_ADDRESS: fffff806547713b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
00000000ffff8087

CURRENT_IRQL: 2

FAULTING_IP:
nt!RtlpHpVsChunkSplit+5a6
fffff806`54242cb6 334ff8 xor ecx,dword ptr [rdi-8]

CPU_COUNT: c

CPU_MHZ: e10

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: firefox.exe

ANALYSIS_SESSION_HOST: DESKTOP

ANALYSIS_SESSION_TIME: 08-15-2019 00:38:47.0157

ANALYSIS_VERSION: 10.0.18914.1001 amd64fre

TRAP_FRAME: ffffdf87e896f970 -- (.trap 0xffffdf87e896f970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffff808f rbx=0000000000000000 rcx=00000000a0ca33a9
rdx=00000000002b0000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80654242cb6 rsp=ffffdf87e896fb00 rbp=ffffdf87e896fb79
r8=411880b95f35b32e r9=0000000000000000 r10=0000000000000000
r11=0101010101010101 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!RtlpHpVsChunkSplit+0x5a6:
fffff806`54242cb6 334ff8 xor ecx,dword ptr [rdi-8] ds:ffffffff`fffffff8=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff806543d1ae9 to fffff806543bfcc0

STACK_TEXT:
ffffdf87`e896f828 fffff806`543d1ae9 : 00000000`0000000a 00000000`ffff8087 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffdf87`e896f830 fffff806`543cde2b : ffffbc86`c6e4bcd0 ffff808f`f7093080 ffff808f`f19c44c0 fffff806`542394bd : nt!KiBugCheckDispatch+0x69
ffffdf87`e896f970 fffff806`54242cb6 : ffffdf87`e896fb79 00000000`00000196 ffff8081`15c6ffe0 ffff808f`f0010280 : nt!KiPageFault+0x46b
ffffdf87`e896fb00 fffff806`54242619 : 0000002b`0000002b ffff8081`15c6ffe0 00000000`00000050 00000000`00000000 : nt!RtlpHpVsChunkSplit+0x5a6
ffffdf87`e896fbd0 fffff806`542323b8 : bc86c6e4`0000016b 00000000`00001690 ffff808f`00001690 ffff808f`f0010000 : nt!RtlpHpVsContextAllocateInternal+0x3c9
ffffdf87`e896fc40 fffff806`5456d06d : ffffdf87`00000200 00000000`00000000 00000000`00000000 00000000`00001688 : nt!ExAllocateHeapPool+0x418
ffffdf87`e896fd80 fffff806`63889395 : ffff808f`fe676c20 ffffdf87`e8970b80 ffffdf87`e8970900 fffff806`00000000 : nt!ExAllocatePoolWithTag+0x5d
ffffdf87`e896fdd0 fffff806`63990267 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!operator new+0x31
ffffdf87`e896fe00 fffff806`6398fe67 : ffffbc86`d314bde0 ffffdf87`e8970900 ffffdf87`e8970900 ffffbc86`d314bde0 : dxgkrnl!DXGCONTEXT::SubmitCommand+0x247
ffffdf87`e89705d0 fffff806`6399063a : 00000000`00000020 ffff808f`f19c4080 ffffbc86`e800bb60 0000000a`bc67de30 : dxgkrnl!DxgkSubmitCommandInternal+0x557
ffffdf87`e8970ac0 fffff806`543d1518 : ffff808f`f19c4080 0000000a`bc67e1c0 00000000`00000000 00000000`000002f8 : dxgkrnl!DxgkSubmitCommand+0x5a
ffffdf87`e8970b00 00007ffa`d86c5a44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000000a`bc67dd68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`d86c5a44


THREAD_SHA1_HASH_MOD_FUNC: 81f75f71ab48725f96de65617a87edce405efc25

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ad7655c5b92bf230b0af1a58fbe1aeee764badca

THREAD_SHA1_HASH_MOD: 6e63506211a7a887b05383b5f9eb13e5982898ba

FOLLOWUP_IP:
dxgkrnl!operator new+31
fffff806`63889395 4883c428 add rsp,28h

FAULT_INSTR_CODE: 28c48348

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: dxgkrnl!operator new+31

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3a1abc64

IMAGE_VERSION: 10.0.18362.295

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 31

FAILURE_BUCKET_ID: AV_dxgkrnl!operator_new

BUCKET_ID: AV_dxgkrnl!operator_new

PRIMARY_PROBLEM_CLASS: AV_dxgkrnl!operator_new

TARGET_TIME: 2019-08-15T05:18:44.000Z

OSBUILD: 18362

OSSERVICEPACK: 295

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: 1998-05-30 14:12:57

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME: 6c7d

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_dxgkrnl!operator_new

FAILURE_ID_HASH: {c60f340f-4f53-1790-5405-773a900f1a75}

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

2: kd> lmvm dxgkrnl
Browse full module list
start end module name
fffff806`63870000 fffff806`63be3000 dxgkrnl (pdb symbols) C:\ProgramData\Dbg\sym\dxgkrnl.pdb\8847E32CB6004EFC4975E3A30AD1F8971\dxgkrnl.pdb
Loaded symbol image file: dxgkrnl.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\dxgkrnl.sys\3A1ABC64373000\dxgkrnl.sys
Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
Image name: dxgkrnl.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 3A1ABC64 (This is a reproducible build file hash, not a timestamp)
CheckSum: 0037B98B
ImageSize: 00373000
File version: 10.0.18362.295
Product version: 10.0.18362.295
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgkrnl.sys
OriginalFilename: dxgkrnl.sys
ProductVersion: 10.0.18362.295
FileVersion: 10.0.18362.295 (WinBuild.160101.0800)
FileDescription: DirectX Graphics Kernel
LegalCopyright: © Microsoft Corporation. All rights reserved.

:)

 

How to fix blue screen stopcode

Hi Willma,

If you are experiencing blue screen errors in your computer, we suggest that you refer to this

article for the step-by-step guide on how to fix blue screen errors.

Let us know if you need further assistance.

 

blue screen issue


after monthes of running system it was fine then on windows 7 it blue screened after looking it over myself and getting advice from local pc shop they suggest upgrading os will fix the issue so I upgraded to win 8.1 and along followed the blue screens now again upgrading after more advice I'm on win 10 and the bluescreens followed as a bad pool error rebooting I have included the requested report please help as spending the $150 the local pc shop wants is my next step

 

Blue Screen

Hi,





Blue screens could be caused by problems with your computer’s hardware or with its driver. Still, we
would like to know more about the issue. Please clarify the following:

• Did you get a STOP code?
• Did you install any hardware or driver recently?

For basic troubleshooting steps to resolve blue screen errors, we suggest checking out this
article and simply follow the steps.



Feel free to contact us if you need further help.