Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Register a free account to unlock additional features at BleepingComputer.com

Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Latest News: NSA shares zero-trust guidance to limit adversaries on the network

Featured Deal: Enjoy quick, compatible data transfers with this $59.99 portable SSD

Latest Buyer's Guide: Hotspot Shield VPN review

BSOD while playing COD

Started by ProPotato , Feb 20 2024 11:06 AM

Please log in to reply

7 replies to this topic

#1 ProPotato

Members
3 posts
OFFLINE

Local time:10:56 PM

Posted 20 February 2024 - 11:06 AM

I keep getting BSOD while playing COD. About every other game, the game crashes and I have to scan and repair before it will launch again. On top of that, I keep getting BDOS on some of those game crashes. My pc is roughly 5 years old with a Ryzen 7 3800, GeForce RTX 2060, 1000W gold EVGA PS, 64x running windows 10.

Windbg showed this:

Microsoft ® Windows Debugger Version 10.0.22621.2428 AMD64

Loading Dump File [C:\Windows\Minidump\021924-9171-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 19041 MP (16 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff800`72a00000 PsLoadedModuleList = 0xfffff800`7362a770

Debug session time: Mon Feb 19 15:33:17.616 2024 (UTC - 6:00)

System Uptime: 0 days 21:38:05.248

Loading Kernel Symbols

...............................................................

................................................................

.............................................................

Loading User Symbols

Loading unloaded module list

.............................

For analysis of this file, run !analyze -v

1: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

MEMORY_MANAGEMENT (1a)

# Any other values for parameter 1 must be individually examined.

Arguments:

Arg1: 0000000000061948, The subtype of the BugCheck.

Arg2: 00000004007c213f

Arg3: 0000000000000001

Arg4: 00000004007c213f

Debugging Details:

------------------

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec

Value: 2780

Key : Analysis.DebugAnalysisManager

Value: Create

Key : Analysis.Elapsed.mSec

Value: 6651

Key : Analysis.Init.CPU.mSec

Value: 3155

Key : Analysis.Init.Elapsed.mSec

Value: 34625

Key : Analysis.Memory.CommitPeak.Mb

Value: 89

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: 021924-9171-01.dmp

BUGCHECK_CODE: 1a

BUGCHECK_P1: 61948

BUGCHECK_P2: 4007c213f

BUGCHECK_P3: 1

BUGCHECK_P4: 4007c213f

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: chrome.exe

STACK_TEXT:

ffff8a09`c3a67bd8 fffff800`72e60c6e : 00000000`0000001a 00000000`00061948 00000004`007c213f 00000000`00000001 : nt!KeBugCheckEx

ffff8a09`c3a67be0 fffff800`72c95b50 : 00000000`00134b02 00000000`00000001 00000000`00000001 00000000`00000000 : nt!MiDereferenceIoPages+0x178176

ffff8a09`c3a67c70 fffff800`72c8ea3e : 00000000`00000000 ffff8a09`c3a68380 ffff8dbf`fedabc40 ffff8a09`c3a682d0 : nt!MiDeletePteRun+0x13b0

ffff8a09`c3a67e80 fffff800`72c23bdd : 00000000`00000000 ffffe102`92e9b740 ffff8a09`c3a682d0 ffff8dbf`fedabc38 : nt!MiDeleteVaTail+0x6e

ffff8a09`c3a67eb0 fffff800`72c237fb : ffff8dc6`00000000 ffffe102`92e9b740 ffff8a09`00000000 ffff8a09`c3a68320 : nt!MiWalkPageTablesRecursively+0xc6d

ffff8a09`c3a67f50 fffff800`72c237fb : ffff8dc6`e36fffb0 ffffe102`92e9b740 ffff8a09`00000001 ffff8a09`c3a68330 : nt!MiWalkPageTablesRecursively+0x88b

ffff8a09`c3a67ff0 fffff800`72c237fb : ffff8dc6`e36ff000 ffffe102`92e9b740 ffff8a09`00000002 ffff8a09`c3a68340 : nt!MiWalkPageTablesRecursively+0x88b

ffff8a09`c3a68090 fffff800`72c207fb : 00000000`00000000 ffffe102`92e9b740 00000000`00000003 ffff8a09`c3a68350 : nt!MiWalkPageTablesRecursively+0x88b

ffff8a09`c3a68130 fffff800`72c8a051 : ffff8a09`c3a682d0 ffffe102`00000000 ffff8dbf`00000002 00000000`00000000 : nt!MiWalkPageTables+0x36b

ffff8a09`c3a68230 fffff800`72c33920 : 00000000`00000001 ffff8a09`00000000 ffffe102`92e9b590 ffffe101`faa72080 : nt!MiDeletePagablePteRange+0x4f1

ffff8a09`c3a68540 fffff800`73090059 : ffffe101`fb995ea0 00000000`00000000 ffffe102`00000000 ffffe101`00000000 : nt!MiDeleteVad+0x360

ffff8a09`c3a68650 fffff800`7305d758 : ffffe101`fb995ea0 ffffe101`ff2d6d60 ffffe101`faa72080 00000000`00000000 : nt!MiUnmapVad+0x49

ffff8a09`c3a68680 fffff800`7305bbcf : 00000000`00000000 00000000`00000000 ffffe101`fb995ea0 ffffe102`92e9b0c0 : nt!MiCleanVad+0x30

ffff8a09`c3a686b0 fffff800`730858e8 : ffffffff`00000000 ffffffff`ffffffff 00000000`00000001 ffffe102`92e9b0c0 : nt!MmCleanProcessAddressSpace+0x137

ffff8a09`c3a68730 fffff800`7308d45e : ffffe102`92e9b0c0 ffffb58d`b76188f0 ffff8a09`c3a68959 00000000`00000000 : nt!PspRundownSingleProcess+0x20c

ffff8a09`c3a687c0 fffff800`73107748 : ffffe101`00000000 fffff800`72c40801 00000001`0000000a 000000ff`37765000 : nt!PspExitThread+0x5f6

ffff8a09`c3a688c0 fffff800`72cc874d : 000012e8`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x38

ffff8a09`c3a68900 fffff800`72e02b20 : 00000000`00000000 ffff8a09`c3a689c0 ffff8a09`c3a68b00 00007ffd`b4004de0 : nt!KiDeliverApc+0x60d

ffff8a09`c3a689c0 fffff800`72e111df : ffffe101`faa72080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInitiateUserApc+0x70

ffff8a09`c3a68b00 00007ffd`b562d064 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f

000000ff`3c7ff4d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`b562d064

SYMBOL_NAME: nt!MiDereferenceIoPages+178176

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.4046

STACK_COMMAND: .cxr; .ecxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 178176

FAILURE_BUCKET_ID: 0x1a_61948_nt!MiDereferenceIoPages

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {16899f95-043e-78ea-0aba-e664d76c4fc5}

Followup: MachineOwner

---------

0x61948 In the process of decrementing the reference counts for an I/O space region, the region's accounting node couldn't be found. Typically, this error means that the argument range was never locked or that it's already been unlocked. Parameter 2 is the base I/O frame. Parameter 3 is the number of pages in the region. Parameter 4 is the specific I/O frame for which a node couldn't be found.

Back to top"> Back to top

BC AdBot (Login to Remove)

BleepingComputer.com
Register to remove ads

#2 PhillPower2

BC Advisor
3,494 posts
OFFLINE

Gender:Male
Local time:04:56 AM

Posted 20 February 2024 - 12:25 PM

See the below and then post the requested info in this thread.

Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 & Vista

If the computer is a desktop can you post the brand and model name or number of the power supply (PSU).

Download then run Speccy (free) and post the resultant url for us, details here, this will provide us with information about your computer hardware + any software that you have installed that may explain the present issue/s.

To publish a Speccy profile to the Web:

In Speccy, click File, and then click Publish Snapshot.
In the Publish Snapshot dialog box, click Yes to enable Speccy to proceed.
Speccy publishes the profile and displays a second Publish Snapshot. You can open the URL in your default browser, copy it to the clipboard, or close the dialog box.

PSU guidance - 10 stripe - Johnny Lucky - PC Mech - PSU Review Database PSU Lemon List Which power supply do you need?

Due to differing time zones not all of us can always be around at the same time and on occasion there may be a delay between replies.

Please note that I do not respond to members who have previously abandoned - not concluded their earlier topics, the assistance here at BC is 100% free, please use this service and not abuse it, knowing the outcome good or bad is valuable information that we all may learn something from.

Back to top"> Back to top

#3 ProPotato

Topic Starter

Members
3 posts
OFFLINE

Local time:10:56 PM

Posted 20 February 2024 - 01:08 PM

My PSU is an EVGA 1000 GT

http://speccy.piriform.com/results/RiNWL7yXePrbvcSOojlWvU4

Back to top"> Back to top

#4 PhillPower2

BC Advisor
3,494 posts
OFFLINE

Gender:Male
Local time:04:56 AM

Posted 20 February 2024 - 02:50 PM

No crash dmps have been attached.

First thing noted was the lack of any system drivers having been installed, see my canned info below for as to why this is important.

Once Windows has been clean installed you must then install first the MBs chipset drivers then the storage/SATA drivers and third the graphics drivers, the drivers can either come from a disk provided by the motherboard manufacturer ** or downloaded from their site and saved to a flash drive etc, this is a must and Windows should not be allowed to check for updates before it has been done as more often than not Windows installs the wrong drivers or in the incorrect order and this can cause all sorts of problems.

The reason why this procedure is so important, the chipset is what enables the MB to be able to communicate with all the hardware + they are the first drivers that Windows looks for on boot.

Good PSU but you having different spec monitors will cause issues.

PSU guidance - 10 stripe - Johnny Lucky - PC Mech - PSU Review Database PSU Lemon List Which power supply do you need?

Due to differing time zones not all of us can always be around at the same time and on occasion there may be a delay between replies.

Please note that I do not respond to members who have previously abandoned - not concluded their earlier topics, the assistance here at BC is 100% free, please use this service and not abuse it, knowing the outcome good or bad is valuable information that we all may learn something from.

Back to top"> Back to top

#5 ProPotato

Topic Starter

Members
3 posts
OFFLINE

Local time:10:56 PM

Posted 20 February 2024 - 03:52 PM

So my understanding, is I need to do a clean windows install first, then the chipset drivers and others listed?

Back to top"> Back to top

#6 Pkshadow

BC Advisor
12,306 posts
OFFLINE

Gender:Not Telling
Location:On the Brow of the Hill, West Coast, Canada
Local time:08:56 PM

Posted 20 February 2024 - 05:12 PM

Hi, I would also update your Bios as you are running : Version: H.40 Date: 11/6/2019 which does not exist.

It is not on your Motherboard Support Page. Must be running another boards BIOS. As there is a H3 and a H5 but no H4.

Current Version is : HJ Date : 2023-10-19 https://www.msi.com/Motherboard/X470-GAMING-PLUS-MAX/support

So in answer to a Clean install it Would be YES. See video How to on the Support Page. Your Drivers are there also. Lots of reboots.

" mosquitoes really wake up everyday and choose violence " — dalia (@_dalia7)
www.cnn.com/2020/07/23/health/mosquitoes-attraction-humans-future-wellness-scn/index.html

I-7 ASUS ROG Rampage II Extreme / ASUS TUF Gaming F17 / I-7 4770K ASUS ROG Maximus VI Extreme

Back to top"> Back to top

#7 ubuysa

BSOD Kernel Dump Expert
500 posts
OFFLINE

Gender:Male
Location:Crete, Greece
Local time:06:56 AM

Posted 21 February 2024 - 03:02 AM

I'd really want to see the dump and other troubleshooting files from the BSOD Posting Instructions. However, from that one dump I would suggest that you test your RAM before you do anything else...

Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.