Random BSOD Win 10 Pro x64 x0133 bugcheck


  1. Posts : 90
    Windows 10 Pro x64
       #1

    Random BSOD Win 10 Pro x64 x0133 bugcheck


    I have not been able to tie the bugcheck to any specific activity. It just randomly occurs, and seemingly with increasing frequency.
      My Computers


  2. Posts : 13,950
    Windows 10 Pro X64 21H1 19043.1503
       #2

    Where did you get your copy of Windows 10? It has a VOLUME_MAK sku which is a Multiple Activation Key. This is used by volume license customers to do large deployments of Windows in their organization. It should not have been sold to a home user but since it's activated your okay. Be aware the activation can go away at any time. Also not sure what will happen when you upgrade.

    The dumps don't have any useful information that I can see.

    This is a very old machine with a BIOS Release Date of 11/23/2011.

    There are a lot of very old drivers:

    Code:
    04/22/2014 3:21:41 PM   C:\WINDOWS\system32\drivers\vsmraid.sys
    05/23/2014 4:39:04 PM   C:\WINDOWS\system32\drivers\mvumis.sys
    02/02/2015 4:00:09 AM   C:\WINDOWS\system32\drivers\iaLPSSi_GPIO.sys
    02/24/2015 10:52:07 AM  C:\WINDOWS\system32\drivers\iaLPSSi_I2C.sys
    03/25/2015 3:36:48 PM   C:\WINDOWS\system32\drivers\lsi_sas.sys
    03/04/2015 9:36:29 PM   C:\WINDOWS\system32\drivers\megasas.sys
    04/30/2015 8:55:35 PM   C:\WINDOWS\system32\drivers\amdxata.sys
    04/09/2015 3:12:07 PM   C:\WINDOWS\system32\drivers\arcsas.sys
    04/09/2015 4:49:48 PM   C:\WINDOWS\system32\drivers\ADP80XX.SYS
    05/14/2015 8:14:52 AM   C:\WINDOWS\system32\drivers\amdsata.sys
    05/18/2015 6:28:03 PM   C:\WINDOWS\system32\drivers\3ware.sys
    05/26/2015 11:53:18 PM  C:\WINDOWS\system32\DRIVERS\igdkmd64.sys
    06/16/2015 6:55:05 AM   C:\WINDOWS\system32\drivers\RTKVHD64.sys
    03/14/2016 8:50:11 PM   C:\WINDOWS\system32\drivers\percsas2i.sys
    05/25/2016 3:01:05 AM   C:\WINDOWS\system32\drivers\evbda.sys
    05/25/2016 3:03:08 AM   C:\WINDOWS\system32\drivers\bxvbda.sys
    10/31/2016 10:09:15 PM  C:\WINDOWS\system32\drivers\bcmfn2.sys
    03/16/2017 5:37:54 PM   C:\WINDOWS\system32\drivers\tapwindscribe0901.sy
    05/15/2017 3:53:25 AM   C:\WINDOWS\system32\DRIVERS\ssudbus.sys
    05/15/2017 3:53:31 AM   C:\WINDOWS\system32\DRIVERS\ssudmdm.sys
    07/24/2017 5:46:09 AM   C:\WINDOWS\system32\drivers\MegaSas2i.sys
    08/02/2017 9:29:59 AM   C:\WINDOWS\system32\drivers\lsi_sas2i.sys
    02/07/2018 6:53:36 AM   C:\WINDOWS\system32\drivers\iaStorAVC.sys
    04/17/2018 11:29:21 AM  C:\WINDOWS\system32\drivers\SmartSAMD.sys
    04/17/2018 3:06:22 AM   C:\WINDOWS\system32\drivers\iaLPSS2i_I2C_CNL.sys
    04/17/2018 3:07:03 AM   C:\WINDOWS\system32\drivers\iaLPSS2i_GPIO2_CNL.s
    04/17/2018 5:24:40 AM   C:\WINDOWS\system32\drivers\iaLPSS2i_I2C_BXT_P.s
    04/17/2018 5:25:15 AM   C:\WINDOWS\system32\drivers\iaLPSS2i_GPIO2_BXT_P
    04/19/2018 3:52:58 AM   C:\WINDOWS\system32\drivers\iaLPSS2i_I2C.sys
    04/19/2018 3:53:24 AM   C:\WINDOWS\system32\drivers\iaLPSS2i_GPIO2.sys
    04/25/2018 12:27:32 PM  C:\WINDOWS\system32\drivers\winmad.sys
    04/25/2018 12:28:00 PM  C:\WINDOWS\system32\drivers\winverbs.sys
    04/25/2018 12:28:08 PM  C:\WINDOWS\system32\drivers\ndfltr.sys
    04/25/2018 12:29:09 PM  C:\WINDOWS\system32\drivers\ibbus.sys
    04/25/2018 12:29:43 PM  C:\WINDOWS\system32\drivers\mlx4_bus.sys
    05/16/2018 1:46:02 AM   C:\WINDOWS\system32\drivers\iaLPSS2i_I2C_GLK.sys
    05/16/2018 1:46:36 AM   C:\WINDOWS\system32\drivers\iaLPSS2i_GPIO2_GLK.s
    05/02/2018 5:40:30 AM   C:\WINDOWS\system32\drivers\lsi_sas3i.sys
    05/03/2018 5:57:21 AM   C:\WINDOWS\system32\drivers\ItSas35i.sys
    05/08/2018 9:23:38 AM   C:\WINDOWS\system32\drivers\cht4vx64.sys
    05/08/2018 9:27:04 AM   C:\WINDOWS\system32\drivers\cht4sx64.sys
    06/01/2018 5:47:02 PM   C:\WINDOWS\system32\drivers\percsas3i.sys
    06/11/2018 2:01:06 PM   C:\WINDOWS\system32\drivers\e1i65x64.sys
    06/13/2018 1:25:43 AM   C:\WINDOWS\system32\drivers\amdi2c.sys
    07/23/2018 5:04:39 AM   C:\WINDOWS\system32\drivers\iai2c.sys
    07/23/2018 5:04:46 AM   C:\WINDOWS\system32\drivers\iagpio.sys
    12/06/2018 12:45:11 PM  C:\WINDOWS\system32\drivers\megasas35i.sys
    This looks to be an XP system that was updated to Vista, Windows 7, maybe 8/8.1 and now 10.

    I'd recommend doing a Clean Install of Windows 10 and hope for the best. You should backup your system first so you don't lose any data. That way if the Clean Install doesn't work you can restore the backup image and be right back to where you were when you created it.

    The first thing you need to do is backup your current install. The best way to do this is to use Macrium Reflect Free to make an image backup to an external hard drive. If you don't have an external hard drive now is a good time to get one as regular backup should be a part of your normal process. You can get a 1TB external hard drive for $60 (less if on sale).

    There are other backup programs available but Macrium is the one I use and recommend.


    • Acronis True Image. A full featured backup solution. ...
    • EaseUS ToDo Backup. A flexible solution in the backup arena. ...
    • Paragon Backup & Recovery. Enterprise options for home backup. ...
    • NovaBackup. Does the basics well, but only the basics.
    I don't know what hardware you have that does or does not work with Windows 10 currently.

    Can you open Device Manager, click on View tab then Show hidden devices then do a screen capture and post here please? Should look something like this:

    Attachment 287206

    What I'm looking for are any with yellow or red marks.
      My Computers


  3. Posts : 90
    Windows 10 Pro x64
    Thread Starter
       #3

    Good questions! I built this thing years ago around an Asus P8Z68V-Pro mobo and an i5-2500k cpu back when those were the current state of the art. I went through a couple HDDs as main drives before I got tired of having to reinstall everything from the ground up and have had a 256GB SSD in there for several years... probably more years than I realize. The other drives on the system are HDDs that have been very reliable but are getting pretty old too.

    While the HW is old, it's been very reliable and normally runs 24/7. Until the last several months when these BSODs starting to happen. I initially thought it was Win 10 doing its update thing... but at some point I looked at event viewer and discovered the bug checks.

    I honestly don't remember the upgrade history on this box. It may well have started life in the XP world... but I don't think this box ever saw Vista. IAC, I upgraded at some point to Win 7... then Win 8.1 (which has been my favorite), then took the free upgrade (iirc) from 8.1 to Win 10.

    At some point in the past I've worked in IT and may well have had access to a MAK version and maybe I installed it on this box. I simply can't remember.

    As regards device manager, everything is clean in there. No yellow or red marks. I can post a pic if you like. I have noticed lately that often after a reboot, the network adapter doesn't load properly until I right click a device and tell it to scan for HW changes. Then the yellow triangle goes away and my internet connection loads right up.

    It may simply be time to replace the guts. I have a decent PSU and case, so it may simply be time to put a new mobo, cpu, ram, and a larger SSD. If the OS key is questionable, maybe I should buy a new copy of Win 10 too.

    I have data backups so my main source of pain would be remembering what apps I use and how they were setup, etc. I try to keep the OS and programs on my boot SSD drive (C:\) and my data on my HDD(s) (D:\ and E:\) which are backed up nightly to an external drive.

    I've used Macrium Reflect Free to clone drives when I've moved from HDDs to SSDs.
      My Computers


  4. Posts : 13,950
    Windows 10 Pro X64 21H1 19043.1503
       #4

    Do you use a Microsoft account to login with or a local account? If you use a Microsoft account then the digital license it tied to the account so you may be able to get away with replacing lots of parts, preferably one or two at a time, then do a Repair Install. You may be surprised at the result, a activated Windows 10.

    On the other hand, replacing everything and doing a clean install with the latest Windows 10 Home or Pro (2004 19041) might be the best way to go. You just missed a deal from PC World for a Windows 10 Pro for $39.00. It expired June 31st. I bought one because the price was too good to pass up.

    Sounds like you have exciting time ahead of you , I'm envious.
      My Computers


  5. Posts : 90
    Windows 10 Pro x64
    Thread Starter
       #5

    Ztruker said:
    Do you use a Microsoft account to login with or a local account? If you use a Microsoft account then the digital license it tied to the account so you may be able to get away with replacing lots of parts, preferably one or two at a time, then do a Repair Install. You may be surprised at the result, a activated Windows 10.

    On the other hand, replacing everything and doing a clean install with the latest Windows 10 Home or Pro (2004 19041) might be the best way to go. You just missed a deal from PC World for a Windows 10 Pro for $39.00. It expired June 31st. I bought one because the price was too good to pass up.

    Sounds like you have exciting time ahead of you , I'm envious.
    No, I don't use a MS account to login. And wow! $39 for Win 10 Pro? Hate I missed that!

    I'm getting old enough that I'm tending to prefer simplicity and stuff that just works rather than being a continuous tweaker. Sorta kinda... maybe. Not really looking forward to rebuilding my PC. I'll probably limp along and just use my laptop until I get a wild hair and order a bunch of parts to rebuild. :)
      My Computers


  6. Posts : 90
    Windows 10 Pro x64
    Thread Starter
       #6

    Just a quick update to this thread.

    I've not had any more BSOD crashes. The only things I've done is:
    1) move the desktop computer from upstairs back downstairs to the office (temporarily relocated while doing a renovation)
    2) I stopped running my Unifi controller 24/7.

    #2 strikes me as being the critical factor in the equation. While I like to keep the unifi controller running 24/7 for the data it generates, if not running it stops the BSOD from happening, I'll accept that trade-off.
      My Computers


  7. Posts : 1,867
    Windows 10 Pro 2004 20H1
       #7

    I would check for driver updates for the controller -

    Ubiquiti - Downloads

    If there are, I would manually install the driver.

    Download the drivers from Ubiquiti.

    In Device Manager, right-click on the device and select Properties

    Click on the Driver tab and select Update Driver

    Click Browse my computer for driver software

    Click Let me pick from an available list of drivers on my computer

    Click Have Disk and then Browse to the path where you saved the Ubiquiti drivers.
      My Computer


  8. Posts : 90
    Windows 10 Pro x64
    Thread Starter
       #8

    OldNavyGuy said:
    I would check for driver updates for the controller -

    Ubiquiti - Downloads

    If there are, I would manually install the driver.

    Download the drivers from Ubiquiti.

    In Device Manager, right-click on the device and select Properties

    Click on the Driver tab and select Update Driver

    Click Browse my computer for driver software

    Click Let me pick from an available list of drivers on my computer

    Click Have Disk and then Browse to the path where you saved the Ubiquiti drivers.
    Thanks, but in this case, the Unifi Controller (5.13.32) is simply a software app/program that uses Java. It is not a physical device... so no drivers are involved.

    I notice there's a Java update. I'll install that.
      My Computers


 

  Related Discussions
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 06:18.
Find Us




Windows 10 Forums