Random Crashes when gaming, new computer.

[Helltech]

I think either my memory is faulty, or one of the ram slots on the motherboard is faulty. I thought I would come here first. I did 4 passes of MemTest86 with no erros and that is why I am confused. I have not gotten a BSOD just a complete crash -> auto restart. It happens very frequently. Within an hour of gaming. When I turn on AMDs versions of XMP (cannot think of the name at this time) the computer takes forever to boot or even get to bios. When I just let it sit at default the ram runs at half the speed it's rated for. These reasons are why I am leaning towards it being memory, however I'm not sure which kit is causing it (because MemTest86 comes back fine) and I only have 3 days before I am out of Amazon's return policy. Every time it happens the dump files say something along the lines of this.

*** WARNING: Check Image - Checksum mismatch - Dump: 0x20f835, File: 0x20f8bd - C:\ProgramData\Dbg\sym\BTHport.sys\5DA12F75203000\BTHport.sys

• A brief description of your problem (but you can also include the steps you tried)

Random crashes -> automatically restart. Happens sometimes immediately after opening a game, or can be a an hour in. Just random. No temperatures seem to be out of whack.

• System Manufacturer?

Self-built.

• Laptop or Desktop?

Desktop

• Exact model number (if laptop, check label on bottom)

N/A

• OS ? (Windows 11, 10, 8.1, 8, 7, Vista)

11

• x86 (32bit) or x64 (64bit)?

64

• Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?

Fresh Windows Copy

• Age of system? (hardware)

3 Weeks

• Age of OS installation?

3 Weeks

• Have you re-installed the OS?

No

• CPU
• RAM (brand, EXACT model, what slots are you using?)
• Video Card
• MotherBoard - (if NOT a laptop)
• Power Supply - brand & wattage (if laptop, skip this one)-

PSU - HX1500I Corsair
RAM - CORSAIR VENGEANCE RGB DDR5 RAM 64GB (2x32GB) 6400MHz CL32 (CMH64GX5M2B6400C32) + CORSAIR VENGEANCE RGB DDR5 RAM 32GB (2x16GB) 6400MHz CL32 (CMH32GX5M2B6400C32)
GPU - EVGA RTX 3090TI FTW3
CPU - AMD 7700
MOBO - ROG STRIX X670E-F GAMING WIFI

• Is driver verifier enabled or disabled?

Not sure

• What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)

Malware Bytes/Windows Defender

• Are you using proxy, vpn, ipfilters or similar software?

No

• Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)

No

• Are you currently under/overclocking? Are there overclocking software installed on your system?

No

 

[SQx]

Greetings,

I am SQx and I will be handling your dumps to help you solve the problem.

Please give me some time to look it over and I will get back to you as soon as possible.

 

[SQx]

Greetings,

1) May I ask you temporary remove Malwarebytes via mbam-clean utility and check if the Bsod will appear again.

2) Could you check the second HDD with Crystal DiskInfo.

An error was detected on device \Device\Harddisk1\DR2 during a paging operation.
The IO operation at logical block address 0x5bf160 for Disk 1 (PDO name: \Device\00000741) was retried.

Download

Crystal DiskInfo and save it to your Desktop.

• Run the installer to install the program.
• When finished, openthe installed program by double clicking on it.
  • Good - There are no problems found, the drive is working properly.
  • Caution - The drive have some problems. (which indicates a drive that you should most likely be thinking about backing up and replacing.)
  • Bad - This usually indicates a drive that’s dead or near death. (! - Back up all important data as soon as possible.)
• Resize the window so that all information is visible.
• Take a screenshot of what you see and post it in your next reply.

 

[Helltech]

Mbam-clean has been ran. Here are my Crystal DIskInfo screen shots. This HDD is not brand new, I bought it like 8 months ago, but this is the first I have I used it (3 weeks ago) so that would be awful if that's the cause.

 

[Helltech]

I did not know I couldn't edit my message after 15 minutes. I did go ahead and use Seagate SMART Calculator (Seagate Error Rate Calculator) because apparently Seagate drives have weird reporting and I'm seeing no errors? I have never used a SeaGate drive before, this is my first. Only ever have used WD, but these are my screenshots for the calculated raw values for "read error rate", "reported uncorrectable error" and "uncorrectable sector count/write error rate"

 

[SQx]

Hello Helltech,

Hope all is well.

1) According to the screenshots, there are no critical errors, which means the hard drives are in the good state.

2) Also please let us know if the BSODs appeared after removing Mbam?

 

[ubuysa]

In addition to the above I think it worthwhile to test your RAM. There are two ways you can do this:

Either....

1. Remove the two 16GB sticks (and ensure that the two 32GB sticks are in the correct slots for a two-stick system) and see how things go for a few days.
2. If you get a BSOD then swap out the two 32GB sticks and run on just the two 16GB sticks for a few days.
3. As long as you run long enough on each pair of RAM sticks this will definitely reveal whether one pair has a bad stick.
4. The advantage of this method is that you can keep working whilst you're testing your RAM, albeit with a potential RAM bottleneck.

Or....

1. 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.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. 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.
4. The major disadvantage of this method is that it will take a long time to test all your RAM and you won't be able to do any work at all until it's finished. Note also, that whilst Memtest86 is very good, no memory tester can find 100% of potential RAM problems.

 

[Helltech]

Hello Helltech,

Hope all is well.

1) According to the screenshots, there are no critical errors, which means the hard drives are in the good state.

2) Also please let us know if the BSODs appeared after removing Mbam?

In addition to the above I think it worthwhile to test your RAM. There are two ways you can do this:

Either....

1. Remove the two 16GB sticks (and ensure that the two 32GB sticks are in the correct slots for a two-stick system) and see how things go for a few days.
2. If you get a BSOD then swap out the two 32GB sticks and run on just the two 16GB sticks for a few days.
3. As long as you run long enough on each pair of RAM sticks this will definitely reveal whether one pair has a bad stick.
4. The advantage of this method is that you can keep working whilst you're testing your RAM, albeit with a potential RAM bottleneck.

Or....

1. 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.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. 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.
4. The major disadvantage of this method is that it will take a long time to test all your RAM and you won't be able to do any work at all until it's finished. Note also, that whilst Memtest86 is very good, no memory tester can find 100% of potential RAM problems.

I did that, it was the first thing I did. After 4 passed it came up with 0 errors. I thought I put that in my main post, but I did not. I originally thought it was faulty ram.
It is still crashing after cleaning Mbam.

 

[SQx]

Greetings,

Please could you provide the new collection app logs according to the instructions.

Also please let me know if the frequency of Bsod occurrence remains the same or less frequently.

 

[ubuysa]

I did that, it was the first thing I did. After 4 passed it came up with 0 errors. I thought I put that in my main post, but I did not. I originally thought it was faulty ram.
It is still crashing after cleaning Mbam.

We recommend two runs of Memtest86 (for 8 iterations) for a proper RAM test, but even that doesn't prove your RAM is good. No RAM tester can do that. The best RAM test will be to remove sticks as I suggested. I really do think it would be wise to try that, it's very important at this stage to be certain that this isn't flaky RAM.

 

[Helltech]

Greetings,

Please could you provide the new collection app logs according to the instructions.

Also please let me know if the frequency of Bsod occurrence remains the same or less frequently.

We recommend two runs of Memtest86 (for 8 iterations) for a proper RAM test, but even that doesn't prove your RAM is good. No RAM tester can do that. The best RAM test will be to remove sticks as I suggested. I really do think it would be wise to try that, it's very important at this stage to be certain that this isn't flaky RAM.

Working on it. The problem is that sometimes it would happen once every 5 minutes or 20, and sometimes it would take 3 hours. So its hard to test these methods, but let me work on it.

 

[Helltech]

Greetings,

Please could you provide the new collection app logs according to the instructions.

Also please let me know if the frequency of Bsod occurrence remains the same or less frequently.

It is much less frequent (making testing single ram sticks much harder when I havn't had time to play games. It only happens when gaming).

Here is my latest files though with two crashes since cleaning malware bites.

 

[ubuysa]

That SysnativeFileCollection upload is exactly the same as your first, all records end on 23rd Feb. You need to run the SysnativeBSODCollectionApp again to generate a new zip file.

You're still getting these sudden restarts then?

 

[SQx]

Greetings,

Please can you zip and attach the "C:\Windows\Minidump\022824-21812-01.dmp" file to your next post.

 

[Helltech]

That SysnativeFileCollection upload is exactly the same as your first, all records end on 23rd Feb. You need to run the SysnativeBSODCollectionApp again to generate a new zip file.

You're still getting these sudden restarts then?

Greetings,

Please can you zip and attach the "C:\Windows\Minidump\022824-21812-01.dmp" file to your next post.

I really don't know what happened I reran the software. However looking in my minidump folder I have a dump from today, and the one from the 23rd, I don't have any others. There were definitely crashes between then. This is the latest one however.

I also have a 5GB dump called "Memory.dmp" which has never happened before, this is the event view message about it.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000001 (0x00007ff86d286e84, 0x0000000000000000, 0x0000000008000000, 0xffff818143b474e0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: c9766ba6-5585-476f-8c15-021d07bddd71.

 

[SQx]

Greetings,

Please could you enable Verifier to find wherever a driver is causing a crash

Please run the following command in the Start menu and follow the instructions:

verifier.exe

Once you will get a Bsod, please disable Verifier in the command prompt:

verifier /reset

Please zip the latest minidump and attach it in you next post.