Random 0x133 BSODs

Hi Indrek

Welcome to the the Ten Forums BSOD forum.

1) The msinfo32 file was not able to be opened.

2) In the left lower corner search type: msinfo32 > allow 15 minutes for it to fully load > save as NFO > zip > post a share link into the thread using one drive, drop box, or google drive

3) Run the DM log collector > post a zip into the thread

4) The misbehaving driver was the Nvidia GPU driver: nvlddmkm.sys

Perform the following steps:

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

6) Make sure that there is no over clocking while troubleshooting.

7) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
8) re-install the Nvidia GPU driver from the Nvidia website
9) make sure that you check the clean install box and if available install the physx driver.

Display Driver Uninstaller Download version 18.0.0.4 (or newer version if available)
Display Driver Uninstaller: How to use - Windows 7 Help Forums
NVIDIA
Download Display Driver Uninstaller - MajorGeeks

10) Upgrade the BIOS: 3606 > 3805
H170M-PLUS Driver & Tools | Motherboards | ASUS Global


11) HD Tune is already installed > run it on all disks > post images into the thread for results on these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan

It would be useful to have you share a link to the kernel memory dump [C:\Windows\memory.dmp] for a better evaluation of the 0x133 bugcheck. Use OneDrive or Dropbox to do this as the file is too large to upload.

philc43 said:

It would be useful to have you share a link to the kernel memory dump [C:\Windows\memory.dmp] for a better evaluation of the 0x133 bugcheck. Use OneDrive or Dropbox to do this as the file is too large to upload.

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

How has the computer stability / instability changed with the new GPU driver?

When Macrium was used were there additional drives that had been used that are no longer connected to the computer?
Where are the backup images saved?
Were they images or clones or both?

The Memory dump was consistent with the mini dump and the misbehaving driver was the Nvidia GPU driver nvlddmkm.sys.

There was a live-kernel-dump.
Please use file explorer to search for the file:

win32k.sys-20190101-1122.dmp

If it is not found using file explorer then download and install Everything to find the file.
voidtools

Then zip and post a share link into the thread using one drive, drop box, or google drive.

Code:

Name                         LastWriteTime       Size (MB)
----                         -------------       ---------
win32k.sys-20190101-1122.dmp 01.01.2019 11:22:37   1027,21

I'll have to give it a few days before I can tell whether stability has improved.

Last I used Macrium was well before the BSODs started. I mostly used it for disk-to-disk cloning; if I made any backups, they were saved to a network drive.

The live kernel dump is here: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

The live kernel dump was debugged.
There were no new misbehaving drivers in the debugging.

Cloning instead of imaging can create a problem called disk signature collision.
As long as you do not have the clones connected during boot the problem should not occur.
At this time it is just reading material to know that it can happen.
How to Fix the Disk Signature Collision Error on Windows - Make Tech Easier
Disk Signature Collision – Fix for Windows XP, Vista, 7, 8, 8.1, 10
The logs had displayed:

Code:

Event[26986]:
  Log Name: System
  Source: Disk
  Date: 2019-01-06T10:42:36.917
  Event ID: 158
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: KRAHV
  Description: 
Disk 2 has the same disk identifiers as one or more disks connected to the system. Go to Microsoft's support website (http://support.microsoft.com) and search for KB2983588 to resolve the issue.

Event[26987]:
  Log Name: System
  Source: Disk
  Date: 2019-01-06T10:42:36.925
  Event ID: 158
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: KRAHV
  Description: 
Disk 3 has the same disk identifiers as one or more disks connected to the system. Go to Microsoft's support website (http://support.microsoft.com) and search for KB2983588 to resolve the issue.

Event[26988]:
  Log Name: System
  Source: Disk
  Date: 2019-01-06T10:42:36.932
  Event ID: 158
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: KRAHV
  Description: 
Disk 4 has the same disk identifiers as one or more disks connected to the system. Go to Microsoft's support website (http://support.microsoft.com) and search for KB2983588 to resolve the issue.

Event[26989]:
  Log Name: System
  Source: Disk
  Date: 2019-01-06T10:42:36.932
  Event ID: 158
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: KRAHV
  Description: 
Disk 5 has the same disk identifiers as one or more disks connected to the system. Go to Microsoft's support website (http://support.microsoft.com) and search for KB2983588 to resolve the issue

If there are no recurrent BSOD over the next few days then you should be set.
If there are recurrent BSOD then they can be troubleshooted.

Any cloning with Macrium was done with disks from other computers, and I don't believe any cloned disks were connected during boot.

Those events I've noticed myself, and they seem to be related to the card reader connected to the PC, which shows up as 5 different empty drives. I've had it for almost 2 years and haven't encountered any problems with it.

Thank you for your help so far. I'll report back in a few days.

Okay.