Windows 10: Reboot from Bughceck - 0x00000133

Discus and support Reboot from Bughceck - 0x00000133 in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello TenForums Community, I have a system that was working well on Windows 7 that I upgraded to Windows 10. It is an older system, however it... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Malitz, Nov 16, 2017.

  1. Malitz Win User

    Reboot from Bughceck - 0x00000133


    Hello TenForums Community,

    I have a system that was working well on Windows 7 that I upgraded to Windows 10. It is an older system, however it passed all the upgrade prerequisites. Since the upgrade, it now BSODs randomly, and I can see from the eventvwr that the causes is this bugcheck:

    0x00000133 (0x0000000000000000, 0x0000000000000501, 0x0000000000000500, 0xfffff80086c75348

    I have attached the output from the diagnostic tool.

    Thank you for looking at my thread and I appreciate any feedback.

    :)
     
    Malitz, Nov 16, 2017
    #1
  2. dyer1234 Win User

    Crashes After Windows 10 Upgrade

    The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP
     
    dyer1234, Nov 16, 2017
    #2
  3. The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff803d9ffa348, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP

    Prior crash due to the following:

    The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000000, 0x0000000000000501, 0x0000000000000500, 0xfffff802245e7348). A dump was saved in: C:\WINDOWS\MEMORY.DMP
     
    Mike Schmidt, Nov 16, 2017
    #3
  4. Ztruker Win User

    Reboot from Bughceck - 0x00000133

    The 11/16 9:16AM dump indicates a problem with nvstor.sys.
    BugCheck 133, {0, 501, 500, fffff8025f46c348}
    *** WARNING: Unable to verify timestamp for nvstor.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : nvstor.sys ( nvstor+4a85 )
    Driver Description: nVidia Storage Drivers
    Driver Update Site: Download Drivers | NVIDIA

    The one currently installed is fairly old: Mon Apr 21 14:34:03 2014 I don't see anything newer available so not sure what you can do to resolve this problem as the driver is for devices on the Biostar motherboard.

    If this is for RAID, are you using a RAID setup? If so you may have to give it up. Here are some possibilities:

    switch from raid to sata in bios setup
     
    Ztruker, Nov 17, 2017
    #4
  5. Malitz Win User
    Hi Ztrucker,

    Thanks for the response. My system is not using a RAID configuration. The system has a storage controller (Silicon Image) attached to it, but that controller is obviously not using the Nvidia driver. Since my main storage device (SSD) is connected directly to the motherboard (which is using the Nvidia driver), I am going to try plugging the SSD into the storage controller and see if that helps.

    By the way ...

    I ran Windows Update, since there apparently were updates pending since March, and Windows seems to have done a significant version jump to v1709. I'm not sure what version it was at before, but during the update, I received several messages about a version upgrade required, several reboots, etc --- so I suppose it wasn't a trivial update. I'm hoping that this change has helped. Here's what I noticed since the update:

    From Device Manager, I can see that the driver is dated 2017-01-06 and a version of 10.6.0.24 :


    Reboot from Bughceck - 0x00000133 [​IMG]


    However, if I look at the driver details, the nvstor.sys is still at version 10.6.0.23:


    Reboot from Bughceck - 0x00000133 [​IMG]


    I ran the diagnostic tool again and looked at the driver file, and the nvstor.sys still shows as not having been updated since 2014, so it doesn't seem as though anything has changed.

    Is there any way to check if the driver version changed recently?

    Also, I check eventvwr for anything related to that Nvidia driver, and only found 3 events, all from today.


    Reboot from Bughceck - 0x00000133 [​IMG]


    ... not sure how that's possible, if that driver has been in use for over a year now.

    Any thoughts?
     
    Malitz, Nov 17, 2017
    #5
  6. Ztruker Win User
    Don't know why there are not more entries in Event Viewer.

    How is you r BIOS setup? RAID or SATA/AHCI?
     
    Ztruker, Nov 17, 2017
    #6
  7. Malitz Win User
    SATA/AHCI.

    I tried plugging the bootable drive into the Silicon RAID controller that is already in the system, but the system refuses to boot from that controller --- not sure why.

    I am considering buying a new SATA controller and trying to boot from there. Does that make sense? Would that circumvent the use of that nvstor.sys driver?
     
    Malitz, Nov 18, 2017
    #7
  8. Ztruker Win User

    Reboot from Bughceck - 0x00000133

    You could try uninstalling the Nvidia nForce driver then reinstall it and since you are not using RAID, select not to install the IDE component. I believe that will resolve the problem.
     
    Ztruker, Nov 19, 2017
    #8
  9. Malitz Win User
    Just FYI, the problem disappeared after running Windows Update. *shrug*
     
    Malitz, Dec 3, 2017
    #9
Thema:

Reboot from Bughceck - 0x00000133

Loading...
  1. Reboot from Bughceck - 0x00000133 - Similar Threads - Reboot Bughceck 0x00000133

  2. BSOD From hal.dll bug code 0x00000133

    in Windows 10 BSOD Crashes and Debugging
    BSOD From hal.dll bug code 0x00000133: Hi, Im kinda in a rock and a hard place here. My pc started bsod'ing randomly one night and I dont know what caused it other then this. 101019-13281-01.dmp 10/10/2019 9:10:30 AM 0x00000133 00000000`00000001 00000000`00001e00 fffff803`56172350 00000000`00000000 hal.dll...
  3. The computer has rebooted from a bugcheck SOS

    in Windows 10 Support
    The computer has rebooted from a bugcheck SOS: Hello! I have a Hetzner Dedicated server and the last month the server restart without any reason! I report to thems and they change me server with my old drivers but again i get the restart with this errors: - The computer has rebooted from a bugcheck. The bugcheck was:...
  4. radom BSOD (0x00000133)

    in Windows 10 BSOD Crashes and Debugging
    radom BSOD (0x00000133): 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8037b58a350, 0x0000000000000000) is the bugcheck error code. Strange thing is my system is stable and this if the first instance I've ever encountered this issue on this system. Ran BlueScreenView by Nirsoft and it...
  5. DPC_WATCHDOG_VIOLATION 0x00000133

    in Windows 10 BSOD Crashes and Debugging
    DPC_WATCHDOG_VIOLATION 0x00000133: My computer blue screens while some games are running in full screen mode. I tried installing different drivers for the video card, using both the newest driver and multiple old versions. It keeps showing a bsod. Any help is greatly appreciated! Here is a link to the dump...
  6. DPC_WATCHDOG_VIOLATION 0x00000133

    in Windows 10 BSOD Crashes and Debugging
    DPC_WATCHDOG_VIOLATION 0x00000133: My computer consistently blue screens with a DPC_WATCHDOG_VIOLATION with a bug check code of 0x00000133. I am not sure what to do, I have tried updating the driver for the hard drive, and I have even completely formatted the hard drive and reinstalled Windows and have the...
  7. Windows 10 Freeze/Random Reboots - Bug Check Code 0x00000133

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 Freeze/Random Reboots - Bug Check Code 0x00000133: Hello, I'm quite stumped on what to do next so I'd like to ask your help for the following problem. Ever since setting up my PC in February, I've been getting random crashes and freezes and I can't get to the bottom of it. Almost always (when there's a .dmp created) the bug...
  8. The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133...

    in Windows 10 Installation and Upgrade
    The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133...: Have not installed new sw in many months. Have not installed new hw in over a year. PC is generating blue screen every couple of days for last 2 weeks. Do not see a correlation with any program I am running. Sometimes, like today, just browsing. Event view shows The...
  9. Blue Screen with the bugcheck 0x00000133

    in Windows 10 BSOD Crashes and Debugging
    Blue Screen with the bugcheck 0x00000133: From last month, when I opened Rstudio, or update a software called Fiji, my computer would have a blue screen with stop codes: dpc watchdog violation or irql_not_less_or_equal. Then I checked event viewer, there was an error in windows logs: The computer has rebooted from...
  10. Silent BSOD: bugcheck was: 0x00000133

    in Windows 10 BSOD Crashes and Debugging
    Silent BSOD: bugcheck was: 0x00000133: Computer freezed twice today, ran 4 weeks without issue. No new software or drivers installed. Screen froze and then computer restart without BSOD message. Event log message: bugcheck was: 0x00000133 (0x0000000000000000, 0x0000000000000501, 0x0000000000000500,...
Tags: