Random 0x133 BSODs Solved

Page 1 of 2 12 LastLast
  1.    1 Week Ago #1

    Random 0x133 BSODs


    My PC has started crashing almost every day with a 0x133 BSOD. Sometimes it happens when browsing the internet, sometimes when I'm not even using the computer. Sometimes the computer runs happily for several days in a row, sometimes it crashes within minutes of resuming from sleep or hibernation. It started happening a couple of weeks ago, but I haven't made any major hardware or software changes. Right before the crash, the system becomes completely unresponsive for a minute or two, before the BSOD.

    Windows is up-to-date, as are all drivers I can think of. There's nothing suspicious in event logs before the crash. BlueScreenView.exe shows slightly different details each time (parameters, caused by driver, etc).
    Last edited by Indrek; 6 Days Ago at 15:02.
      My ComputerSystem Spec


  2. Posts : 22,640
    windows 10 professional version 1607 build 14393.969 64 bit
       1 Week Ago #2

    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
      My ComputerSystem Spec

  3.    1 Week Ago #3

    Thanks for the quick reply! All steps completed, I'm attaching the results. I'm not overclocking any components.

    SFC/DISM/chkdsk output:


    Microsoft Windows [Version 10.0.17763.195]
    (c) 2018 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1

    Image Version: 10.0.17763.195

    [===========================99.9%========================= ] The restore operation completed successfully.
    The operation completed successfully.

    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.
    Volume label is Windows.

    Stage 1: Examining basic file system structure ...
    895744 file records processed.
    File verification completed.
    7809 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    89613 reparse records processed.
    999438 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    89613 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    51848 data files processed.
    CHKDSK is verifying Usn Journal...
    35106472 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    419839999 KB total disk space.
    274294088 KB in 285955 files.
    207204 KB in 51849 indexes.
    0 KB in bad sectors.
    1016647 KB in use by the system.
    65536 KB occupied by the log file.
    144322060 KB available on disk.

    4096 bytes in each allocation unit.
    104959999 total allocation units on disk.
    36080515 allocation units available on disk.

    C:\WINDOWS\system32>
    Attached Thumbnails Attached Thumbnails HDTune-Scan.png   HDTune-Health.png   HDTune-Benchmark.png  
    Last edited by Indrek; 6 Days Ago at 15:03.
      My ComputerSystem Spec

  4. philc43's Avatar
    Posts : 3,823
    64bit Win 10 Pro ver 1809 Build 17763.253 and W10 Insider Build 18312
       1 Week Ago #4

    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.
      My ComputersSystem Spec

  5.    1 Week Ago #5

    philc43 said: View Post
    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.
      My ComputerSystem Spec


  6. Posts : 22,640
    windows 10 professional version 1607 build 14393.969 64 bit
       1 Week Ago #6

    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
      My ComputerSystem Spec

  7.    1 Week Ago #7

    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.
      My ComputerSystem Spec


  8. Posts : 22,640
    windows 10 professional version 1607 build 14393.969 64 bit
       1 Week Ago #8

    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.
      My ComputerSystem Spec

  9.    1 Week Ago #9

    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.
      My ComputerSystem Spec


  10. Posts : 22,640
    windows 10 professional version 1607 build 14393.969 64 bit
       1 Week Ago #10

    Okay.
      My ComputerSystem Spec


 
Page 1 of 2 12 LastLast

Related Threads
Random BSODs in BSOD Crashes and Debugging
Hello, i was hoping somebody could help me with some issues i've been having, this is the second BSOD i have had in a while, they both seem to come at random, what doesn't change however is the error code; DPC Watchdog Violation. From what i can...
Hi, I would really appreciate it if anyone could shed any light on this. The PC was originally Windows 7 and I upgraded to Windows 10 last year. The crashes seem to be random, sometimes when it's sitting idle, sometimes whilst I'm working. ...
Random BSODs on new PC in BSOD Crashes and Debugging
Hi, i'm getting random BSOD erros, on a new computer. I already ran the memtest 86, no erros, and i can't seem to solve the problem. Here is the dump files...
Random bsods in BSOD Crashes and Debugging
Recently i started having random bsods...tried reseting windows and deleting and reinstalling video drivers and still nothing...i attached minidump files...pls help
Random BSODs in BSOD Crashes and Debugging
Hi folks! I installed Win 10 on my home server and it keeps crashing all the time with random BSODs (with a bunch of different error messages). Before that, it was running fine on Win Home Server 2011. I tried a bunch of driver combinations...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:00.
Find Us