Multiple BSOD issues and freezing

[ZucriyAmsuna]

Windows 10 Home 64-bit

Unique BSOD codes listed below:
[ul]
[li]0x0000003b SYSTEM_SERVICE_EXCEPTION[/li][li]0x0000007f UNEXPECTED_KERNEL_MODE_TRAP[/li][li]0x00000124[/li][li]0x00000133[/li][li]0x0000000a IRQL_NOT_LESS_OR_EQUAL[/li][/ul]
The system also occasionally freezes without any error logs, minidumps, or anything otherwise that could be useful in the Event Viewer.

The freezing and various Blue Screens occur randomly. Sometimes they are in games, sometimes when watching YouTube videos, and sometimes when doing nothing at all. They have occurred many times over the lifetime of the PC (about 16 months).

Example games where BSODs happened:

• Cyberpunk 2077
• Overwatch
• Valorant
• StarCraft II

All drivers appear to be updated. Some were reinstalled. The GPU driver was a new clean install before the latest BSOD.

All cable plugs and hardware has been reseated.

The RAM has been replaced to no avail (in response to 0x0000007f).

Running Windows Memory Diagnostic and Memtest86 on both RAM modules individually and together yielded no negative results after ten hours each.

Nothing is overclocked.

Minidumps and other useful files can be found here: PC #2 – Google Drive

I think I’ve tried just about everything besides the mind-numbing and annoying process of reinstalling Windows.

[phillpower2]

Information POSTING INSTRUCTIONS - Please read before posting in this section

[COLOR=rgb(226, 80, 65)]If the computer is a desktop, 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.[/COLOR]

[ZucriyAmsuna]

Speccy Snapshot: http://speccy.piriform.com/results/G...AfA7G1rgNWITVF

There is no brand or model name; it was put together by a company known as CyberPowerPC. I missed the warranty deadline before I began complaining to them about the BSOD issues.

Thank you in advance for your time in assisting me with this issue.

[phillpower2]

You need to take off the side of the case and get the information for us, you have a high end GPU, multiple storage devices and a second screen hooked up so we 100% need to know the PSU information.

You have not attached the required Sysnative file, no worries though I am only interested in having any dmp files, use the method below to get them to us.

1. Copy any dmp files from C:\Windows\Minidump onto the desktop.
2. Select all of them, right-click on one, and click on Send To> New Compressed (zipped) Folder.
3. Upload the zip folder using the Attach button, bottom left of the dialogue input box

[ZucriyAmsuna]

Required Sysnative file? I see nothing about that in the posting instructions, but you can find all SysnativeBSODCollectionApp files, including the minidumps, in the Google Drive link. Regardless, I attached the minidumps to this message. Apparently, 3 MB is too large to attach to these messages, so I split them into three .zip files.

As for the PSU, it was listed as “800 Watts - Standard 80 Plus Gold Certified Power Supply” at CyberPowerPC. It is embedded at the bottom of the case. If necessary, I can get you more info when I return home (if I can figure out how to get the bottom of the case open). From what I’ve read, it is possible it will have a false label–or no label at all–since it is a standard CyberPowerPC PSU.

[phillpower2]

The site owner must have changed things then, his prerogative, as said no matter the dmps is all I need.

Can you put only the most recent crash dmps in the one folder for us, it makes reading them in the correct order so much easier, dmps more than a couple of days old are of no use either I`m afraid.

we 100% need to know the PSU information.

Not all PSUs are made equal and some are so bad as to be dangerous, system builders like CyberPowerPC are renowned for using el cheapo PSUs and your freezing PC is typical behaviour of overheating which includes an overheating PSU.

[COLOR=rgb(44, 130, 201)]Edit to add: Three dmps were of any use, one was a driver verifier created crash, mshidkmdf.sys what it is and how to resolve it here another crash was related to Razer software so there is a good chance that you have KB or mouse driver conflict going on, check in Device Manager for any yellow " or red Xs, be sure to check the hidden devices as well, third crash was generic.[/COLOR]

[ZucriyAmsuna]

Sure. I separated the minidumps in the Google Drive folder and attached the most recent ones, including a new one from about an hour ago, which is the one I’ve been trying to focus on this week since we seem to be able to recreate it by playing Cyberpunk 2077 anywhere between five minutes and three hours. (0x0000007f)

I also attached a picture of the PSU info. I don’t think the PSU is overheating unless it is faulty. This PC has a twin built the exact same way in the same room with the same conditions, and this twin has significantly fewer problems with it. However, considering the freezes, it is now at the top of the potential replacement list.

[phillpower2]

Please see the edit in my reply #6.

As was suspected your have a cheap PSU that can be found on Tier C • Recommended for cheap mid/low-end systems here your system is far from mid/low range and so needs the protection of a Gold efficiency Corsair, EVGA or Seasonic, allowing for the extra drives and monitor 750W or above as a minimum.

The PSU only the cause of the freezing imo and the BSOD driver related.

NB: Would recommend that you enable XMP in the BIOS, its running slow at 2666MHz atm.

[COLOR=rgb(44, 130, 201)]Your previous post has been hidden.[/COLOR]

[ZucriyAmsuna]

I did reply regarding your edit, but the post is now missing for some reason. EDIT: I now see that the post was hidden.

In short, I reinstalled the Razer software and driver, and the only questionable thing in the Device Manager was the Intel Bluetooth driver with a yellow exclamation mark despite being up-to-date:
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)

{Operation Failed}
The requested operation was unsuccessful.

Bluetooth is disabled anyway.

[phillpower2]

All we can do now then is wait and see.

Did you check the Hidden Devices option in Device Manager as well, you will quite often find keyboards and mice there.

Have you enabled XMP in the BIOS.

Some additional PSU info Which power supply do you need?

[ZucriyAmsuna]

I did check the hidden devices; nothing seemed out of the ordinary.

I just enabled XMP; I was unaware that existed before.

I’ll look into a new PSU and see what happens.

Do you have any tips on how to identify which driver is responsible?

Thank you again for your time. If I still have issues after the new power supply, should I reply here or create a new thread?

[phillpower2]

As said all we can do is wait and see if you get any further BSOD, don`t try and force the issue by enabling Driver Verifier, leave as is and any further crashes zip it/the dmp/s up using our method and attach them to a reply

Regarding the PSU, as mentioned, I don`t think the two issues are related, freezing tends to be hardware related whereas BSOD can be both down to bad RAM or memory slots causing BSOD, there is nothing suggesting any RAM issues so keep this thread software related.

You are welcome btw

[ZucriyAmsuna]

Here’s an interesting new error. Again, it was triggered by playing Cyberpunk 2077.

[phillpower2]

dxgmms2.sys was the culprit, this to do with video drivers and is commonly something that is taken care of by Windows updates, see info here

I would leave as is at this time as Cyberpunk 2077 causing issues is nothing new as it has been problematic since day one and has once again caused people issues with its latest patch, info here

[Bruce]

@ZucriyAmsuna - any news?