Windows 8 and 8.1 Forums


Daily BSOD: 0x133, MsMpEng.exe SINGLE_DPC_TIMEOUT_EXCEEDED

  1. #21


    Posts : 18
    Windows 8.1


    Results from DISM:

    Code:
    C:\WINDOWS\system32>Dism /Online /Cleanup-Image /ScanHealth
    
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    
    Image Version: 6.3.9600.17031
    
    
    [==========================100.0%==========================]
    The component store is repairable.
    The operation completed successfully.
    Code:
    C:\WINDOWS\system32>Dism /Online /Cleanup-Image /CheckHealth
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    
    Image Version: 6.3.9600.17031
    
    
    The component store is repairable.
    The operation completed successfully.
    Code:
    C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth
    
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    
    Image Version: 6.3.9600.17031
    
    
    [==========================100.0%==========================]
    
    
    Error: 0x800f0906
    
    
    The source files could not be downloaded.
    Use the "source" option to specify the location of the files that are required t
    o restore the feature. For more information on specifying a source location, see
     http://go.microsoft.com/fwlink/?LinkId=243077.
    
    
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    Contents of C:\WINDOWS\Logs\DISM\dism.log:
    Code:
    [2396] Caller did not request sparse mount
    [2396] Mounting new image.
    Wim:         [\\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim]
    Image Index: [1]
    Mount Path:  [C:\WINDOWS\TEMP\154c5749-fc6a-4d8a-a02e-f4656759468a]
    [2396] Wimserv process started for guid 1e40bae4-4ab1-40b6-8c19-5fcef8d35174.  Id is 2524
    [2524] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
    [2524] Mounted image at C:\WINDOWS\TEMP\154c5749-fc6a-4d8a-a02e-f4656759468a.
    [2396] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.
    [2396] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
    [2396] [0xc142011c] WIMGetMountedImageHandle:(2568)
    [2396] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.
    [2396] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
    [2396] [0xc142011c] WIMGetMountedImageHandle:(2568)
    [2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
    [2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
    [2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
    [2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
    [2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
    [2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
    [2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim
    [2524] Received unmount request for image with guid 1e40bae4-4ab1-40b6-8c19-5fcef8d35174.
    [2524] Unmount for image at C:\WINDOWS\TEMP\154c5749-fc6a-4d8a-a02e-f4656759468a complete.
    [THOUSANDS OF WHAT LOOK LIKE CHINESE CHARACTERS (UTF-8 conversion from binary?)]
    〲㐱ㄭⴲ㌱ㄠ㨷㔵〺ⰲ䤠普††††††††䐠卉⁍†䥐㵄㌲㘹吠䑉㈽〴‴敔灭牯牡汩⁹敳瑴湩⁧桴⁥捳慲 [truncated]
    [2232] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
    [2232] [0xc142011c] WIMGetMountedImageHandle:(2568)
    [THOUSANDS MORE OF ODD CHARACTERS]
    〲㐱ㄭⴲ㐱〠㨳㐲㈺ⰹ䤠普††††††††䐠卉⁍†䥄䵓圠䵉倠潲楶敤㩲倠䑉㈽㌲′䥔㵄㌴㘹嬠 [truncated]
    It looks like that error, 0x800f0906, has something to do with .NET 3.5. I am going to reinstall .NET 3.5 and re-run the tool.

    As a point of note, this person had the same problem (exact same log issue I'm seeing) here: .NET framework 3.5 asennus ei onnistu - Microsoft Community
    English Translation: https://translate.google.com/transla...8-a5c8e0fea052

    I have rebooted, ran through reinstalling .NET 3.5, and now running SFC.EXE /SCANNOW and the other Dsim utilities again. I have also scheduled `chkdsk c: /r` to be run on my next boot. As a point of note, I have run SFC utility with /verifyonly before and it said everything was verified and correct. Reference post earlier: Daily BSOD: 0x133, MsMpEng.exe SINGLE_DPC_TIMEOUT_EXCEEDED

    I am also running the command `Dism /Online /Cleanup-image /StartComponentCleanup` from the reference material above that said fixed their problem.

    Code:
    C:\WINDOWS\system32>SFC.EXE /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.
    Code:
    C:\WINDOWS\system32>Dism /Online /Cleanup-Image /CheckHealth
    
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    
    Image Version: 6.3.9600.17031
    
    
    The component store is repairable.
    The operation completed successfully.
    Code:
    C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth
    
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    
    Image Version: 6.3.9600.17031
    
    
    [==========================100.0%==========================]
    
    
    Error: 0x800f0906
    
    
    The source files could not be downloaded.
    Use the "source" option to specify the location of the files that are required t
    o restore the feature. For more information on specifying a source location, see
     http://go.microsoft.com/fwlink/?LinkId=243077.
    
    
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    Code:
    C:\WINDOWS\system32>Dism /Online /Cleanup-image /StartComponentCleanup
    
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    
    Image Version: 6.3.9600.17031
    
    
    [==========================100.0%==========================]
    
    
    Error: 0x800f0831
    
    
    DISM failed. No operation was performed.
    For more information, review the log file.
    
    
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    Code:
    C:\WINDOWS\system32>Dism /Online /Cleanup-Image /ScanHealth
    
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    
    Image Version: 6.3.9600.17031
    
    
    [==========================100.0%==========================]
    The component store is repairable.
    The operation completed successfully.
    Looks like we might have found an issue!

    Anyone have ideas on how to fix this?
    Reference material I've read over:
    .NET Framework 3.5 0x800F0906 then 0x800f081f - Microsoft Community
    [SOLVED] Error when running DISM /Online /Cleanup-Image /RestoreHealth - error 0x800f0906 - Sysnative Forums

    Attached is the dism.log file from C:\Windows\Logs\DISM
    Here is an external download for the larger (23mb) CBS logs and cab files: http://slickplaid.net/files/CBS.zip

    I am going to reboot, run `CHKDSK c: /scannow` on reboot and report back. If anyone has any ideas, let me know.

      My System SpecsSystem Spec

  2. #22


    Posts : 18
    Windows 8.1


    Log from chkdsk:

    Code:
    Checking file system on C:
    The type of the file system is NTFS.
    
    
    A disk check has been scheduled.
    Windows will now check the disk.                         
    
    
    Stage 1: Examining basic file system structure ...
    Cleaning up instance tags for file 0x856eb.
      662272 file records processed.                                                         File verification completed.
      4309 large file records processed.                                      0 bad file records processed.                                      
    Stage 2: Examining file name linkage ...
      910530 index entries processed.                                                        Index verification completed.
      0 unindexed files scanned.                                           0 unindexed files recovered.                                       
    Stage 3: Examining security descriptors ...
    Cleaning up 1056 unused index entries from index $SII of file 0x9.
    Cleaning up 1056 unused index entries from index $SDH of file 0x9.
    Cleaning up 1056 unused security descriptors.
    Security descriptor verification completed.
      124130 data files processed.                                            CHKDSK is verifying Usn Journal...
    Usn Journal verification completed.
    
    
    Stage 4: Looking for bad clusters in user file data ...
      662256 files processed.                                                                File data verification completed.
    
    
    Stage 5: Looking for bad, free clusters ...
      89980176 free clusters processed.                                                        Free space verification is complete.
    CHKDSK discovered free space marked as allocated in the volume bitmap.
    
    
    Windows has made corrections to the file system.
    No further action is required.
    
    
     499746815 KB total disk space.
     138807348 KB in 532903 files.
        273340 KB in 124131 indexes.
             0 KB in bad sectors.
        745419 KB in use by the system.
         65536 KB occupied by the log file.
     359920708 KB available on disk.
    
    
          4096 bytes in each allocation unit.
     124936703 total allocation units on disk.
      89980177 allocation units available on disk.
    
    
    Internal Info:
    00 1b 0a 00 c6 90 09 00 cc ac 10 00 00 00 00 00  ................
    25 02 00 00 56 00 00 00 00 00 00 00 00 00 00 00  %...V...........
    
    
    Windows has finished checking your disk.
    Please wait while your computer restarts.
      My System SpecsSystem Spec

  3. #23


    Posts : 18
    Windows 8.1


    After all reboots, I ran SFC.EXE /SCANNOW one last time for fun:

    Code:
    C:\WINDOWS\system32>SFC.EXE /SCANNOW
    
    
    Beginning system scan.  This process will take some time.
    
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    
    Windows Resource Protection found corrupt files and successfully repaired
    them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.
    Interesting... Here is the CBS.log parts from that: Attachment 57891

    Note that I uninstalled Hyper-V in that reboot.

    Code:
    C:\WINDOWS\system32>Dism /Online /Cleanup-Image /CheckHealth
    
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    
    Image Version: 6.3.9600.17031
    
    
    The component store is repairable.
    The operation completed successfully.
    Code:
    C:\WINDOWS\system32>Dism /Online /Cleanup-Image /ScanHealth
    
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    
    Image Version: 6.3.9600.17031
    
    
    [==========================100.0%==========================]
    The component store is repairable.
    The operation completed successfully.
    Code:
    C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth
    
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    
    Image Version: 6.3.9600.17031
    
    
    [==========================100.0%==========================]
    
    
    Error: 0x800f0906
    
    
    The source files could not be downloaded.
    Use the "source" option to specify the location of the files that are required t
    o restore the feature. For more information on specifying a source location, see
     http://go.microsoft.com/fwlink/?LinkId=243077.
    
    
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    Code:
    C:\WINDOWS\system32>Dism /Online /Cleanup-image /StartComponentCleanup
    
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    
    Image Version: 6.3.9600.17031
    
    
    [==========================100.0%==========================]
    
    
    Error: 0x800f0831
    
    
    DISM failed. No operation was performed.
    For more information, review the log file.
    
    
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    @blueelvis For your reference:
    Code:
    5: kd> lmvm usbport
    start             end                 module name
    fffff801`1929d000 fffff801`1930c000   USBPORT    (deferred)             
        Image path: \SystemRoot\System32\drivers\USBPORT.SYS
        Image name: USBPORT.SYS
        Timestamp:        Sat May 31 01:30:25 2014 (53897701)
        CheckSum:         000790F5
        ImageSize:        0006F000
        File version:     6.3.9600.17195
        Product version:  6.3.9600.17195
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        2.0 Dll
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoftฎ Windowsฎ Operating System
        InternalName:     usbport.sys
        OriginalFilename: usbport.sys
        ProductVersion:   6.3.9600.17195
        FileVersion:      6.3.9600.17195 (winblue_gdr.140530-1506)
        FileDescription:  USB 1.1 & 2.0 Port Driver
        LegalCopyright:   ฉ Microsoft Corporation. All rights reserved.
      My System SpecsSystem Spec

  4. #24


    Posts : 5,139
    Win8.1Pro - Finally!!!


    I've read through all the attached logs and researched some of the error codes.
    All of them seem to point to a non-fatal OS corruption (in one case the SxS directories weren't properly enumerated)

    What media did you use to load this copy of Windows, and where did you get the files/iso's from?

    In most cases like this, I'd next recommend a Refresh of the OS - to see if that can fix it.
    If not,then I'd suggest a Reset (but in this case I'd suggest a reinstall from different installation media).

    EDIT: But this is sort of "throwing the baby out with the bath water". We're fixing errors that you'd never know about unless you ran our commands, then you're wiping out the OS (and all your stuff) because of that.

    I'd suggest that we see if the BSOD problem has stopped BEFORE Refreshing/Resetting the system.
    Good luck!
      My System SpecsSystem Spec

  5. #25


    Posts : 18
    Windows 8.1


    Quote Originally Posted by usasma View Post
    I've read through all the attached logs and researched some of the error codes.
    All of them seem to point to a non-fatal OS corruption (in one case the SxS directories weren't properly enumerated)
    Interesting. I took a lot of care installing this time and saw no errors. It's incredibly odd how Windows fails so gracefully without any errors, and yet so much could be wrong with my installation.

    Quote Originally Posted by usasma View Post
    What media did you use to load this copy of Windows, and where did you get the files/iso's from?
    I used Microsoft's own image creation tool to write it to a SanDisk Extreme USB 3.0 64gb drive.

    Quote Originally Posted by usasma View Post
    In most cases like this, I'd next recommend a Refresh of the OS - to see if that can fix it.
    If not,then I'd suggest a Reset (but in this case I'd suggest a reinstall from different installation media).

    EDIT: But this is sort of "throwing the baby out with the bath water". We're fixing errors that you'd never know about unless you ran our commands, then you're wiping out the OS (and all your stuff) because of that.

    I'd suggest that we see if the BSOD problem has stopped BEFORE Refreshing/Resetting the system.
    Good luck!
    Just a quick question on terminology so I know what I'm getting in to:

    Refresh vs. Reset, what is the difference? I accidentally did one of the two of those once and 1/2 or more of my programs missing, and a ton of problems resulted from that when I had to work that same day. Needless to say, I've moved to a much more modular setup now that can be synced rather than installed to be ready to work at any location or computer.

    Give me a weekend and I can reinstall if needed. Just know that is exactly what I did about 2-5 months ago (time files!) to fix this BSoD problem, and yet it still is persisting. It was using a completely different CD Key (I hate Window's licensing, was going to force me to install Win7, upgrade to Win8, so instead I bought a new key) and this was the first time I've used Microsoft's USB image to install (different media than the original install).

    As a note: The CEntrance people gave me a beta driver which I've installed as of last night.
      My System SpecsSystem Spec

  6. #26


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Slickplaid ^_^,

    A Refresh of the Windows Operating System means that your personal files would be kept but certain things like Apps would be removed. Settings are also reset.

    A Reset of the Windows Operating System means that nothing would be stored on the system and Windows would be installed from scratch.

    Let us know how it goes ^_^

    -Pranav
      My System SpecsSystem Spec

  7. #27


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Windows is an incredibly robust, fault-tolerant OS that will keep on running long after you expect it to fail.

    From what you've related here, I don't think that there's a significant problem with the OS at this point.
    And, you've done the refresh and the reinstall - yet the problem still persists.

    You may want to plan for a Refresh and a Reset in the near future - but you're still testing the other things that we and the CEntrance people have suggested, so I'd hold off for now.

    Where did you get the ISO file that you used to create the USB installation drive?
    You've used different keys to install - have you used a different ISO file to install (on the times that you reinstalled to try and fix the BSOD issue)?
    The point here is trying to rule out the installation media/process as being to blame.

    Where did you get this DISM command? Have you done any work on the WinSxS folder?
    Dism /Online /Cleanup-image /StartComponentCleanup
    Another thing that I noted was that the chkdsk tool made corrections to the file system.
    Try running it again and see if the tool makes further corrections. If it does, then we can suspect that something is corrupting the file system - and then can work on fixing that.
      My System SpecsSystem Spec

  8. #28


    Posts : 18
    Windows 8.1


    Quote Originally Posted by usasma View Post
    You may want to plan for a Refresh and a Reset in the near future - but you're still testing the other things that we and the CEntrance people have suggested, so I'd hold off for now.
    Sounds good. Sometimes there can be a week or so that goes by without any issues and then constant, almost daily (or even multiple times per day) BSoDs. This most recent stint has been BSoD free for about 4 days.

    Quote Originally Posted by usasma View Post
    Where did you get the ISO file that you used to create the USB installation drive?
    You've used different keys to install - have you used a different ISO file to install (on the times that you reinstalled to try and fix the BSOD issue)?
    The point here is trying to rule out the installation media/process as being to blame.
    The ISO was downloaded direct from Microsoft after purchasing the CD-Key online through their online store. I used the Microsoft "Media Creation Tool" tool.

    Create installation media for Windows 8.1 - Windows Help

    Quote Originally Posted by usasma View Post
    Where did you get this DISM command? Have you done any work on the WinSxS folder?
    I got it from a technet article. I do not recall the exact link.
    I have not done anything directly to the WinSxS folder, nor have I read any information on that.

    Quote Originally Posted by usasma View Post
    Another thing that I noted was that the chkdsk tool made corrections to the file system.
    Try running it again and see if the tool makes further corrections. If it does, then we can suspect that something is corrupting the file system - and then can work on fixing that.
    I will run it tonight and report back.
      My System SpecsSystem Spec

  9. #29


    Posts : 18
    Windows 8.1


    Here is the chkdsk output from yesterday:

    Code:
    Checking file system on C:
    The type of the file system is NTFS.
    
    
    A disk check has been scheduled.
    Windows will now check the disk.                         
    
    
    Stage 1: Examining basic file system structure ...
      662272 file records processed.                                                         File verification completed.
      4286 large file records processed.                                      0 bad file records processed.                                      
    Stage 2: Examining file name linkage ...
      917250 index entries processed.                                                        Index verification completed.
      0 unindexed files scanned.                                           0 unindexed files recovered.                                       
    Stage 3: Examining security descriptors ...
    Cleaning up 47 unused index entries from index $SII of file 0x9.
    Cleaning up 47 unused index entries from index $SDH of file 0x9.
    Cleaning up 47 unused security descriptors.
    Security descriptor verification completed.
      127490 data files processed.                                            CHKDSK is verifying Usn Journal...
      38999920 USN bytes processed.                                                            Usn Journal verification completed.
    
    
    Stage 4: Looking for bad clusters in user file data ...
      662256 files processed.                                                                File data verification completed.
    
    
    Stage 5: Looking for bad, free clusters ...
      83558906 free clusters processed.                                                        Free space verification is complete.
    
    
    Windows has scanned the file system and found no problems.
    No further action is required.
    
    
     499746815 KB total disk space.
     164451452 KB in 537622 files.
        275916 KB in 127491 indexes.
             0 KB in bad sectors.
        783823 KB in use by the system.
         65536 KB occupied by the log file.
     334235624 KB available on disk.
    
    
          4096 bytes in each allocation unit.
     124936703 total allocation units on disk.
      83558906 allocation units available on disk.
    
    
    Internal Info:
    00 1b 0a 00 55 b0 09 00 c5 e0 10 00 00 00 00 00  ....U...........
    2c 02 00 00 56 00 00 00 00 00 00 00 00 00 00 00  ,...V...........
    
    
    Windows has finished checking your disk.
    Please wait while your computer restarts.
    Edit: If I run a reset this coming weekend, would that be good to do? Obviously it would hinder any diagnostics we might find in the future, but I'm worried if the Windows setup files are corrupted or messed up some how, would a reset just put the corrupted files back and we're back at square one?

    I guess my questiion is: Should I reinstall using a fresh download or attempt a reset? Which is recommended?

    What is my next course of action moving forward to see if we can't mitigate a reset/reinstall?
      My System SpecsSystem Spec

  10. #30


    Posts : 18
    Windows 8.1


    Reference to my post in the Windows Activation subforum:

    Windows Update Issues, possibly missing updates, BSoD

    I will report back with any interesting information they might be able to gleam from my issue.

    Also, there was a single BSoD over the weekend, but it was while I was away and before I had turned off VirtualBox or any of the other suggestions listed so far. I then turned off VirtualBox and unplugged all USB devices (except for mouse and keyboard) and no BSoD occurred during that time.

    Link to my debug output posted in the other thread: https://www.eightforums.com/attachmen...17-02-2015.zip

    I'm hoping I can catch a BSoD when I have things disabled, but since this is my work computer, it's difficult to have those things uninstalled or unplugged when I need to actually get work done.

    Thanks!
      My System SpecsSystem Spec

Page 3 of 4 FirstFirst 1234 LastLast
Daily BSOD: 0x133, MsMpEng.exe SINGLE_DPC_TIMEOUT_EXCEEDED
Related Threads
Solved BSOD DPC_WATCHDOG 0x133 in BSOD Crashes and Debugging
Hi i have this bsod but can't understand why.. i can stay ok for 1 week.. and today i had 3 bsod in 20min... it is totally random. Pls help me :)
Hey guys, At some stage last night my PC must have restarted as I saw the vanilla error message in the morning. It's a new machine, no GPU installed at the moment and very little drivers. Downloaded WinDbg and had a quick look but I'm new to all the drivers so not really sure on what is the...
More than one BSOD daily. in BSOD Crashes and Debugging
I keep having a few BSOD daily, I can't pin point what it is. My recent one was PAGE_FAULT_IN_NONPAGED_AREA. Here is the SF Diag: http://db.tt/6dbdS7jg EDIT: If you don't trust dropbox, I added a attachment! Any help would be appreciated. Thanks!
Daily BSOD in hall.dll 0x133 in BSOD Crashes and Debugging
Hi everyone, I am experiencing regular BSODS, at least 1 a day. They are occurring randomly, not necessarily under stress. I'm a newbie so I have no idea what is wrong. When it bsods, I get DPC_WATCHDOG_VIOLATION. According to bsodviewer the error is in hal.dll. I am running Windows 8 64. ...
Windows 8 Bsod 0x133 in BSOD Crashes and Debugging
Hello Can someone help me with this Bsod Error? Pc freeze for some minutes and then appear Windows 8 error page with this error: dpc_watchdog_violation Thank you
BSOD error 0x133 in BSOD Crashes and Debugging
I've been receiving seemingly random BSOD's with Windows 8. I've tried doing a completely clean install of it, but still have the same issue. Thanks in advance.
BSOD in hall.dll 0x133 in BSOD Crashes and Debugging
Hi, on my Windows 8 x64 System I have daily crashes in hal.dll. I can't find a reason for this. The crashes happens mainly not under workload ? The other crash in the zip 0x21c happens after a corrupt system device. I restored Windows 8 with the new restore feature. I have attached Windos...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook