Windows 8 and 8.1 Forums


Random BSOD 0x00000133 - New PC

  1. #1


    Posts : 19
    Windows 8.1 Pro

    Random BSOD 0x00000133 - New PC


    Hi there
    We just setup a new Windows 8.1 Pro HP Elitedesk 800G1 Ultra Small Desktop with a Samsung SSD and updated Windows with all the relevant recommended updates.

    The computer was connected up on Friday just gone (15th April 2016). As the computer is in a hearing aid company - the audiology software and related audiology USB equipment was then connected up and installed by a third party vendor. We think the issue might be down to one of the components of the equipment but we need assistance to review the BlueScreen information to help confirm such and rule out other components.

    Any help you can provide is greatly appreciated. Attached is the logs.

    Thanks and Kind Regards
    PCTS

      My System SpecsSystem Spec

  2. #2



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    Hi pcts,


    I'm very sorry for the huge delay, there aren't many in this part of the forum.
    Are you still requiring help? If you do please post back so I'll be notified and respond a.s.a.p.
      My System SpecsSystem Spec

  3. #3


    Hello,

    If you have installed Windows and drivers correctly, it should not create such error. I checked solution for this and it’s not related to any hardware that you connect to system.
    Please see below link which has MS Hotfix for same.

    https://support.microsoft.com/en-us/kb/3029348
      My System SpecsSystem Spec

  4. #4



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    If you have installed Windows and drivers correctly, it should not create such error.
    That is actually incorrect for a part, it is about how the drivers work not if a driver is installed correctly because that is most of the times properly done. (No examples, that would be too complicated.)
      My System SpecsSystem Spec

  5. #5


    Posts : 19
    Windows 8.1 Pro


    Quote Originally Posted by axe0 View Post
    Hi pcts,


    I'm very sorry for the huge delay, there aren't many in this part of the forum.
    Are you still requiring help? If you do please post back so I'll be notified and respond a.s.a.p.

    Hi axe0

    Thanks for your reply. Sorry for my delayed reply - was flat out there with other items for last few days. This issue is still happening. I updated the graphics card drivers to the latest recommended ones by Microsoft but still the same issue.

    Any ideas?

    Thanks
    PCTS
      My System SpecsSystem Spec

  6. #6



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    It seems to be pointing to USB, unfortunately it isn't specific (it likely is, but that part goes above my head).
    There are a few possibilities
    • The USB device drivers,
    • The USB drivers of the ports,
    • The USB device connection,
    • The USB ports.

    To test this -> update all the drivers of the USB devices, remove all USB devices you don't need and switch the other devices from USB port.
    If it cashes, switch again, repeat this step until you have no more crashes or until you've tried all combinations.
    Code:
    0: kd> k
     # Child-SP          RetAddr           Call Site
    00 fffff800`c6930c88 fffff800`c4b90ad4 nt!KeBugCheckEx
    01 fffff800`c6930c90 fffff800`c4a81c41 nt! ?? ::FNODOBFM::`string'+0x1a214
    02 fffff800`c6930d20 fffff800`c51ad7b5 nt!KeClockInterruptNotify+0x91
    03 fffff800`c6930f40 fffff800`c4af6713 hal!HalpTimerClockIpiRoutine+0x15
    04 fffff800`c6930f70 fffff800`c4b6782a nt!KiCallInterruptServiceRoutine+0xa3
    05 fffff800`c6930fb0 fffff800`c4b67c0f nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    06 ffffd000`6899ef90 fffff800`cf410094 nt!KiInterruptDispatchLBControl+0x11f
    07 ffffd000`6899f120 fffff800`cf421ac2 Wdf01000!FxIrpQueue::RemoveNextIrpFromQueue+0x28
    08 ffffd000`6899f150 fffff800`cf4906f3 Wdf01000!FxRequest::GetNextRequest+0x12
    09 ffffd000`6899f180 fffff800`cf48e59c Wdf01000!FxIoQueue::QueueIdle+0x35b
    0a ffffd000`6899f210 fffff800`d155cba7 Wdf01000!imp_WdfIoQueueStopAndPurge+0x90
    0b ffffd000`6899f260 fffff800`d15b775a USBXHCI!Endpoint_UcxEvtEndpointAbort+0x11b
    0c ffffd000`6899f2c0 fffff800`d15b6dfa ucx01000!UcxEndpointStateEntryFunc_Aborting1+0x16
    0d ffffd000`6899f2f0 fffff800`d15b533d ucx01000!StateMachineEngine_EventAdd+0x41a
    0e ffffd000`6899f350 fffff800`d15b4d31 ucx01000!UrbHandler_AbortPipe+0x9d
    0f ffffd000`6899f380 fffff800`d15aae30 ucx01000!Urb_USBPORTStyle_ProcessURB+0x331
    10 ffffd000`6899f3e0 fffff800`cf406d43 ucx01000!RootHub_Pdo_EvtInternalDeviceControlIrpPreprocessCallback+0x448
    11 ffffd000`6899f470 fffff800`cf574c27 Wdf01000!FxDevice::DispatchWithLock+0xb01
    12 ffffd000`6899f550 fffff800`cf572147 ACPI!ACPIIrpDispatchDeviceControl+0x97
    13 ffffd000`6899f580 fffff800`d1af9cae ACPI!ACPIDispatchIrp+0x137
    14 ffffd000`6899f5f0 fffff800`cf406d43 UsbHub3!HUBPDO_EvtDeviceWdmIrpPreprocess+0xdf6
    15 ffffd000`6899f700 fffff800`cf574c27 Wdf01000!FxDevice::DispatchWithLock+0xb01
    16 ffffd000`6899f7e0 fffff800`cf572147 ACPI!ACPIIrpDispatchDeviceControl+0x97
    17 ffffd000`6899f810 fffff800`d2056299 ACPI!ACPIDispatchIrp+0x137
    18 ffffd000`6899f880 fffff800`d2056594 usbccgp!DispatchPdoUrb+0x169
    19 ffffd000`6899f940 fffff800`d2056062 usbccgp!DispatchPdoInternalDeviceControl+0x84
    1a ffffd000`6899f9a0 fffff800`d20a7ad7 usbccgp!USBC_Dispatch+0x162
    1b ffffd000`6899fa40 fffff800`d20a1c89 usbser+0x7ad7
    1c ffffd000`6899faa0 fffff800`d20a1971 usbser+0x1c89
    1d ffffd000`6899faf0 fffff800`d20a15d1 usbser+0x1971
    1e ffffd000`6899fb20 fffff800`c4b3625b usbser+0x15d1
    1f ffffd000`6899fb50 fffff800`c4b1326c nt!PopIrpWorker+0x2df
    20 ffffd000`6899fc00 fffff800`c4b6c9c6 nt!PspSystemThreadStartup+0x58
    21 ffffd000`6899fc60 00000000`00000000 nt!KiStartSystemThread+0x16
      My System SpecsSystem Spec

  7. #7


    Posts : 19
    Windows 8.1 Pro


    Hi axe0

    Thanks for the message and for looking into the logs. I will give that a go. It might take a week or two before I know the result but I will revert once I have tested as much as I can.

    Kind Regards
    PCTS
      My System SpecsSystem Spec

Random BSOD 0x00000133 - New PC
Related Threads
I built this PC around Dec of last year and until June 22nd, I've had 0 issues with the PC. On June 22 I had my first BSOD and since then I've had 3 more that come and go, about a week or 2 after the fact. I looked with bluescreenview and it seems my Nvidia driver is the culprit but on other...
BSoD playing Minecraft, error 0x00000133 in BSOD Crashes and Debugging
Hi guys, im newbie in computers, and i need help .-. Yesterday i was normally playing Minecraft, but today when i join multiplayer game i always get a BSoD (DPC_WATCHDOG_VIOLATION) My laptop is : Acer Aspire E1-571G -Intel Core i7 3612QM 2.1GHz -nVidia GeForce 710M -6GB RAM -1TB HDD
Hello. About a week ago i bought myself a new computer, it's been working nicely so far, played a few different games without any problems, but then today i was looking through my steam library and decided to install Just Cause 2, and within about 10min of playing my computer froze, and after...
Solved BSOD Since Purchase 0x0000009f & 0x00000133 in BSOD Crashes and Debugging
Hey guys I need help. I purchased this laptop a year ago and I had problems with it properly shutting down. I formatted it several times and that temporarily fixed the issue. I never had BSOD screens until now and when I checked the minidumps those improper shut down errors were a result of...
Error 0x00000133 DPC WATCHDOG VIOLATION in BSOD Crashes and Debugging
I recently bought a new monitor, an Acer T232HL. After playing some games, within the first 8 hours of use I got a Blue Screen. I proceeded to get one ever day at night. So far it's happened 3 times (I got the monitor about 3 days ago). I have to note that, it is touchscreen, and it comes with a...
Hi everyone, Since I last updated Windows 8.1, I've been getting a lot of BSOD (DPC_WATCHDOG_VIOLATION) getting out of sleep mode or when booting/rebooting. I examined the cause of the BSOD with BlueScreenView and it seems to be caused by "igdkmd64.sys" (witch is linked to "Intel HD Graphics...
Bsod Windows 8 code 0x00000133 in BSOD Crashes and Debugging
Hello all, im a newbie :P What it is iv just received windows 8 pro 64bit and had it installed for 2 days and since the last 3 hours iv being receiving 2 bsods and i was wondering could someone put me in the right direction on what the problem is? I have put an attachment with the info from a...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook