Windows 10: 0x0000003b BSOD - I'm out of ideas!

Page 3 of 4 FirstFirst 1234 LastLast
  1.    4 Weeks Ago #21

    hdd23 said: View Post
    Dumps added. BSOD again, System Restore resolved.

    Chris
    So a System Restore resolved your issue? If so that's great!

    To note; ASUS AI Suite has been known since Windows 7 to cause some issues that causes BSODs. It gave me issues with BSODs on W10 Pro 1709.
      My ComputerSystem Spec

  2.    4 Weeks Ago #22

    Kyle said: View Post
    So a System Restore resolved your issue? If so that's great!

    To note; ASUS AI Suite has been known since Windows 7 to cause some issues that causes BSODs. It gave me issues with BSODs on W10 Pro 1709.
    I think I may have 2 x issues which is perhaps what has confused me!

    Since uninstalling AI Suite the PC seems stable. However . . . .

    Putting my RAM to 2133MHz (XMP Profile 1) - locked up the PC - so I need to stay at JDEC SPD of 1600MHz for now. Whilst it's a separate issue to this thread of course, I believe that the IMC (Integrated Memory Controller) on my 4930k is not strong enough to drive 64GB (8x8GB) of RAM. That's a separate "overclocking" journey upon which I'm now happier to travel - assuming the software issues have now been resolved.

    I'll still await diagnosis of the last dumps I attached though, please guys. The reason for this is that even after uninstalling the software which seems problematic - the Driver Verifier BSOD is BEFORE entering Windows.

    My understanding is that the PC should get as far as the shell i.e. desktop before that happens. Is that correct?

    Thanks again for providing such an excellent forum, I'm very grateful for the continued input.
      My ComputerSystem Spec


  3. Posts : 13,344
    Windows 10 Pro
       4 Weeks Ago #23

    Sorry for the slight delay, I've been preparing myself for a job application.

    Am I correct when I say some storage devices are connected to Asmedia ports? If not I would be surprised to see some Asmedia drivers back in this IRP (I/O Request Packet, communication method to have contact with other drivers and the OS).
    Code:
    8: kd> !irp ffffc6802cb0c010 1
    Irp is active with 8 stacks 9 is current (= 0xffffc6802cb0c320)
     No Mdl: No System Buffer: Thread ffffc68025df1040:  Irp is completed.  
    Flags = 00000000
    ThreadListEntry.Flink = ffffc6802cb0c030
    ThreadListEntry.Blink = ffffc6802cb0c030
    IoStatus.Status = c00000bb
    IoStatus.Information = 00000000
    RequestorMode = 00000000
    Cancel = 00
    CancelIrql = 0
    ApcEnvironment = 00
    UserIosb = 00000000
    UserEvent = 00000000
    Overlay.AsynchronousParameters.UserApcRoutine = 00000000
    Overlay.AsynchronousParameters.UserApcContext = 00000000
    Overlay.AllocationSize = 00000000 - 00000000
    CancelRoutine = 00000000   
    UserBuffer = 00000000
    &Tail.Overlay.DeviceQueueEntry = ffffc6802cb0c088
    Tail.Overlay.Thread = ffffc68025df1040
    Tail.Overlay.AuxiliaryBuffer = 00000000
    Tail.Overlay.ListEntry.Flink = 00000000
    Tail.Overlay.ListEntry.Blink = 00000000
    Tail.Overlay.CurrentStackLocation = ffffc6802cb0c320
    Tail.Overlay.OriginalFileObject = 00000000
    Tail.Apc = 00000000
    Tail.CompletionKey = 00000000
         cmd  flg cl Device   File     Completion-Context
     [N/A(0), N/A(0)]
                0  2 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 ffffffffc00000bb
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [N/A(0), N/A(0)]
                0 10 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [IRP_MJ_PNP(1b), IRP_MN_START_DEVICE(0)]
                0 12 ffffc6802ca02880 00000000 fffff803439cd010-ffffaf8c7d9c41f0    
    	      *** WARNING: Unable to verify timestamp for asmtxhci.sys
    *** ERROR: Module load completed but symbols could not be loaded for asmtxhci.sys
     \Driver\asmtxhci	nt!ViFilterGenericCompletionRoutine
    			Args: 00000000 00000000 00000000 00000000
     [IRP_MJ_PNP(1b), IRP_MN_START_DEVICE(0)]
                0 10 ffffc6802cb00ae0 00000000 fffff803439cd010-ffffaf8c7d9c45c0    
    	      *** WARNING: Unable to verify timestamp for asmthub3.sys
    *** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys
    *** WARNING: Unable to verify timestamp for ctxusbm.sys
    *** ERROR: Module load completed but symbols could not be loaded for ctxusbm.sys
     \Driver\asmthub3	nt!ViFilterGenericCompletionRoutine
    			Args: 00000000 00000000 00000000 00000000
     [IRP_MJ_PNP(1b), IRP_MN_START_DEVICE(0)]
                0 10 ffffc6802cb049e0 00000000 fffff80343302060-ffffc6802cb88fc0    
    	       \DRIVER\VERIFIER_FILTER	nt!PnpDeviceCompletionRoutine
    			Args: 00000000 00000000 00000000 00000000
    
    Irp Extension present at 0xffffc6802cb0c320:
    I'll still await diagnosis of the last dumps I attached though, please guys. The reason for this is that even after uninstalling the software which seems problematic - the Driver Verifier BSOD is BEFORE entering Windows.

    My understanding is that the PC should get as far as the shell i.e. desktop before that happens. Is that correct?
    No, the boot process exists of various phases.
    Driver verifier is loaded as soon as ntoskrnl is called by Winload which is called after the boot manager is finished. Ntoskrnl has 2 phases of initialization. The first phase loads all BSOD messages, initializes driver verifier, creates some processes and does a few other things. The second phase ensures driver verifier is working and initializes components like the system time and drivers. Then smss.exe loads autochkdsk, registry hives, some dll's and some executables. Then winlogon.exe registers the user and userinit.exe runs the final scripts for both the user and the machine.

    The login screen is 1 of the last steps in the boot process whilst driver verifier and all the drivers are loaded long before that. This is the reason why some users cannot log back in when driver verifier is enabled, some boot drivers are causing trouble in those situations.
      My ComputersSystem Spec

  4.    4 Weeks Ago #24

    Hi. Good luck with the application!

    As I said earlier in the thread, the Asmedia ports have always been problematic. (Struggle to boot ANYTHING non-Windows, CSM or EFI - examples are Ubuntu, Linux Mint and Parted Magic).

    I'm off out for a while but I will try work out which storage devices are connected to which ports to answer to answer your very valid question.

    There are Asmedia SATA ports and Asmedia USB ports but I have a non-Asmedia PCI-e card with USB 3.0 / SATA 6gbps functionality - so may be able to jig around to avoid them altogether. It's a cracking mainboard and have years of fun and learning ahead, I'm sure. R4BE | ROG - Republic of Gamers Global


    My manual linked below if you want to nosey at the ports available

    http://dlcdnet.asus.com/pub/ASUS/mb/...ck_Edition.pdf

    The X79 chipset has "signal timing variations" with PCI-e Rev 3.0 but issues have historically persisted regardless of 1) Forcing Gen 3 on GPU and/or 2) Setting of PCI-e link speed in "BIOS"

    Geforce Gen3 Support On X79 Platform | NVIDIA
      My ComputerSystem Spec

  5.    3 Weeks Ago #25

    I am SO annoyed - I had 2 x BSODs today (after disabling ALL Asmedia stuff in the BIOS)

    BUT looks like W10 1709 has removed them. Brilliant.

    One was nvlddmkm related and one was driver state power failure, I believe.

    My logs are attached from the "dm_log_collector" tool - hope they still have some useful info for you.

    Is it worth trying to undelete the 2 x minidumps?
    0x0000003b BSOD - I'm out of ideas! Attached Files
      My ComputerSystem Spec


  6. Posts : 13,344
    Windows 10 Pro
       3 Weeks Ago #26

    Undelete? Why/how are they deleted?
      My ComputersSystem Spec

  7.    3 Weeks Ago #27

    axe0 said: View Post
    Undelete? Why/how are they deleted?
    Windows 10 must have done this as part of a daily maintenance task. I did not clear myself nor have any utility which clears by itself. I only ever run CCleaner ad hoc :-(

    Others reporting same issues - good example here

    What part of Windows 10 automatically deletes mini dump files?
      My ComputerSystem Spec


  • Posts : 13,344
    Windows 10 Pro
       3 Weeks Ago #28

    Unless there's some task configured with disk cleanup, no minidump gets deleted (exception with the minidump limit of 50).

    To answer your question, it might be possible. Deleting a file only marks the file as 'deleted' so it can be overwritten (which is why deleting 10's of thousands of files goes incredibly fast), if you have a program like Recuva installed you can undo the deleting.

    If you do not have such a program installed, every action involving writing to the disk must be done on a different partition than the Windows partition, e.g. downloading, unpacking a zip, installing, etc., if you don't install it on a different partition the dumps will very likely be overwritten with no chance of a proper recovery.

    Also, don't follow the command posted in the thread you linked. It looks to be a command I used some time ago which has a small issue resulting in not all requested files being collected.
      My ComputersSystem Spec

  •    3 Weeks Ago #29

    Hi, I've attached a list of undeleted files ending in .dmp - tell me if you want them undeleting.

    I've also attached the only file I think might be relevant (but I'm only guessing)
    0x0000003b BSOD - I'm out of ideas! Attached Files
      My ComputerSystem Spec


  • Posts : 13,344
    Windows 10 Pro
       3 Weeks Ago #30

    Files from C:\Windows\Minidump are the ones needed.
      My ComputersSystem Spec


  •  
    Page 3 of 4 FirstFirst 1234 LastLast

    Related Threads
    Hello everyone, I have had multiple BSOD's since reinstalling Win10 x64 last night.. Prior to the last BSOD, I have gone to my motherboard manufacturer site (Asus) and installed the latest drivers. The latest BSOD (after driver updates)...
    BSOD SYSTEM_SERVICE_EXCEPTION 0x0000003b in BSOD Crashes and Debugging
    BSOD happens spontaneously with no visible reason. Windows 10 x64 Home for one language. I hope it wouldn't be a problem that it's a Russian Windows edition. :o I consider the reason of the BSOD is Adguard or Avast, but I'm a bit lack of BSOD...
    BSOD 0x00000050 0x0000003b 0x0000000A in BSOD Crashes and Debugging
    My computer has crashed for some time now and the things I have been doing so far is Swap out my GTX 660 for my old GTX 460. No improvements. Swap out my ram memory with a friend 8GB.No improvements. Installed a clean version of Windows 10. It...
    BSOD Bugcheck 0x0000003b in BSOD Crashes and Debugging
    Hi to all and thank you for creating this forum; I have been recently noticing that my computer sometimes hangs up with a blank screen when the windows 10 login screen is supposed to load. I am forced to press the reset button in order to eventually...
    BSOD playing GTA V error 0x0000003b in BSOD Crashes and Debugging
    I get the blue screen anytime i play gta v, it can happen from a few minutes to a few hours in. I recently had a 8gb stick of vengeance ram go bad idk if this could be causing part of the problem but i wanted to add it. The source of the blue screen...
    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 01:32.
    Find Us