Unexpected kernel mode trap BSOD Windows 10 (Premire Pro) and more

Page 1 of 2 12 LastLast

  1. Posts : 10
    Windows 10
       #1

    Unexpected kernel mode trap BSOD Windows 10 (Premire Pro) and more


    Hi,

    I keep having problems with my win 10 on several fronts recently:
    1. The main one is when using Premire but I suspect that these issues are not from PP itself (can't be sure of course) but from something else in the system, I get different BSODs and crashes of the software itself (one of them is Unexpected kernel mode trap BSOD but there are others like Page fault in nonpaged area bsod and others). I tried many things and been trying my luck with Microsoft forums - so far with no resolution.

    I fully reinstalled my Nvidia drivers using DDU on safe mode (using the latest studio drivers on my RX 4700), all MB drivers should be up to date although with MSI boards there is no simple way I know of to remove the drives and re-install them (if you know how to do this let me know).

    There are two other issues - one minor and one very annoying as well which might or (possibly) might not be related:
    2. Windows seems to be fully updated BUT I am stuck with 0x80070643 error - its been months and MS still doesn't seem to have a fix which does not involve massing up with partitions (trying to do this resulted in more errors which might have made things even worse for my installation - and yes I did SFC and DISM many time with no luck).

    3. The other very annoying issue started fairly reently (I don't know when or how exactly). But it seems that I can't connect any new USB devices to the computer (to any USB port) and only existing ones are recognized in the device manager. Maybe something to do with USB driver recogniztion - I really don't know. I tried all sorts of things and most of them just got the situation worse so I had to get back to a restore point several times. This also does not allow me to run memtest86 to make sure my RAM is fine as the thumb drive I try to use for that is not working in the bios (each time I choose the drive after boot it does not runmemtest86 which is super strange, plus my normal mouse stopped working in the bios but still works in Windows - again I have no idea what is going on here).

    This is a primary high end work desktop PC and editing video is my job so every day (actually hour) that I can't edit is crucial so any suggestions would be most welcome.

    Potentially usefuly info:

    Here is a link to my minidumps - there are 5 just from recent BSODs - I also added a system info file in an NFO format if that helps.

    Dropbox - Minidupms - Simplify your life

    Thanks in advance,

    Id
      My Computer


  2. Posts : 1,594
    win10 home
       #2

    Restore the bios to default settings.
    In Powershell [admin ] run the following in the given sequence and format---
    dism /online /cleanup-image /restorehealth
    When finished then run ---
    sfc /scannow and run it until a clean report is given.
    In the Search box,start typing ==-reliability --- to gain access to Reliability History
    Check the entries connected to the crashes,which should be red-flagged and the ---view tech details --- will give the problem name.Are there different problems or just the one constantly occurring ?
      My Computer


  3. Posts : 10
    Windows 10
    Thread Starter
       #3

    Hi,
    Thanks for the suggestions.

    1. I am pretty reluctant to restore the bios settings - I am using a 13900 which as you know makes a lot of heat and the default settings of most MB including mine do not limit the power draw so it gets super hot and draws a ton of power for very minimal gain in power but I did restrict the power (I did this a year ago when I got the machine I don't even remember what I changed but that was a long time ago and the PC worked fine for months so it doesn't seem to be related unless a bios update changed some stuff - I did update the bios a while back but I am not sure if this is the time the problems started.

    2. I did the restorehealth and sfc - I have done them before (using CMD not PowerShell but it should be the same I think) - no errors or issues were found.

    3. There are many crashes on the reliability page - not all of them have the same parameters but they don't tell me much - maybe they can help you or somebody else figure this one out:

    Problem signature
    Problem Event Name: BlueScreen
    Code: 3b
    Parameter 1: c0000005
    Parameter 2: fffff8041a4d9f44
    Parameter 3: ffffe5814e05a920
    Parameter 4: 0
    OS version: 10_0_19045
    Service Pack: 0_0
    Product: 256_1
    OS Version: 10.0.19045.2.0.0.256.48
    Locale ID: 1037

    Problem signature
    Problem Event Name: BlueScreen
    Code: 139
    Parameter 1: 3
    Parameter 2: ffffc2014ac37560
    Parameter 3: ffffc2014ac374b8
    Parameter 4: 0
    OS version: 10_0_19045
    Service Pack: 0_0
    Product: 256_1
    OS Version: 10.0.19045.2.0.0.256.48
    Locale ID: 1037


    Problem signature
    Problem Event Name: BlueScreen
    Code: 139
    Parameter 1: 3
    Parameter 2: ffffd4826990f590
    Parameter 3: ffffd4826990f4e8
    Parameter 4: 0
    OS version: 10_0_19045
    Service Pack: 0_0
    Product: 256_1
    OS Version: 10.0.19045.2.0.0.256.48
    Locale ID: 1037


    Problem signature
    Problem Event Name: BlueScreen
    Code: 50
    Parameter 1: ffffb687c8389720
    Parameter 2: 11
    Parameter 3: ffffb687c8389720
    Parameter 4: 2
    OS version: 10_0_19045
    Service Pack: 0_0
    Product: 256_1
    OS Version: 10.0.19045.2.0.0.256.48
    Locale ID: 1037


    Problem signature
    Problem Event Name: BlueScreen
    Code: 7f
    Parameter 1: 8
    Parameter 2: ffffe381a6368e70
    Parameter 3: 0
    Parameter 4: fffff80133e3f76d
    OS version: 10_0_19045
    Service Pack: 0_0
    Product: 256_1
    OS Version: 10.0.19045.2.0.0.256.48
    Locale ID: 1037

    4. My USBs still don't seem to accept any "new" devices - even older devices that were connected and I try to reconnect them now do not work. Interestingly my Thunderbolt USB-C ports do work (I just tried a card reader and it worked on the TB port but not on any of the USB ports - this whole thing is quite horrible...

    Id
      My Computer


  4. Posts : 1,594
    win10 home
       #4

    In paragraph 3, you say the mouse works in Windows but not in the bios.This suggests the mouse is fine but the bios is not, which is why the suggestion to reset the bios to default and see if the mouse is recognized.
    To leave the problem unresolved could be to potentially lead to other problems.
    The ---Blue screen ---errors are most likely a video card problem,either seating or drivers or both.
    In the Search box,type in ---dxdiag ---and check the pages.The Display page will give the current driver version and the Input page will give the mouse status.
      My Computer


  5. Posts : 10
    Windows 10
    Thread Starter
       #5

    Hi,
    My regular wireless mouse doesn't work in bios but when I connect an older wired mouse it does - very strange.
    Again my USBs seem to have lots of issues.
    What specific info should I look for on the dxdiag tool? (it states no problems found on all pages)
      My Computer


  6. Posts : 113
    Windows 10
       #6

    Have you tried using your wired mouse in Windows? What does Device Manager tell about your USB ports? I also suggest USBDeviceTreeViewer and/or USBDeview, which can show details about what happens when you attach a not accepted USB device.
      My Computer


  7. Posts : 10
    Windows 10
    Thread Starter
       #7

    Thanks JLArranz,
    I installed USBDeviceTreeViewer - I don't know much about this complex software but trying to connect a number of devices (thumb drives a new Logitech camera that was not connected to this computer before) I get:
    Status : 0x01802400 (DN_HAS_PROBLEM, DN_DISABLEABLE, DN_NT_ENUMERATOR, DN_NT_DRIVER)
    Problem Code : 28 (CM_PROB_FAILED_INSTALL)

    What other info do you need from the software and what can I do about this - it seems to happen with almost anything I connect to and USB (not to the Thunderbolt I think) inputs on my computer (an old wired mouse did seem to work not sure if this means anything).
      My Computer


  8. Posts : 113
    Windows 10
       #8

    I haven't seen those errors before, but I've been looking for them in the net now and it seems that you don't have drivers for your motherboard USB. If so I would expect that Device Manager shows devices with problems, does it? But it's also possible that your mobo USB hw is in bad condition, or that your wireless mouse or other device is causing general USB problems. I say the latter for the problems you're having in the BIOS, that does not depend on the Windows drivers.

    Does your USB stick with memtest work in other computers? I'm more afraid about your wireless mouse, I would quarantine it (not use it in any computer) until you know for sure what's happening. Motherboards have voltage regulators for USB and they can break for using devices in bad state (this was common years ago, but possibly motherboard makers have invented things to avoid it; bear in mind that USB plugs and sockets have live voltage -5V- and it can do short-circuits, a common result is that mobo USB breaks).

    Fyi, if the problem or part of it is that USB sw drivers are in bad state for your maneuvers with them or for other reasons, the solution would be reinstalling the motherboard drivers. Depending on how they're made, it would be possible reinstalling them over what you have now, using an option to repair them from Control Panel -> Programs and Features, or uninstalling them before reinstalling.

    One of my motherboards has drivers for the following devices:

    - Audio
    - Chipset
    - LAN
    - RAID/AHCI
    - USB 3.0 (this motherboard has two USB systems, USB2 should be included in the chipset drivers as it's inside the SB950 Southbridge, and USB3 is provided by an additional VIA chipset with its own drivers connected to the PCI express bus).
      My Computer


  9. Posts : 10
    Windows 10
    Thread Starter
       #9

    Hi,
    Again thank you.
    I use the MEG Z790 ACE from MSI.
    I update all the drivers using the MSI Center app.
    Honestly, I still find it extremely strange that in 2024 we still have to deal with drivers at all (MS should have figured out a way to work with hardware manufacturers forcing them to be approved by MS and install automatically when the hardware is connected to the computer and I can think of several ways of doing this but that is for another discussion).

    I can download and re-install the chipset driver for my MB again from the MSI site:
    MSI MEG Z790 ACE, E-ATX - Intel 13th/12th Gen - 24+1+2 Phases, DDR5, PCIe 5.0, 2.5G LAN, Wi-Fi 6E
    Or I can download, remove the existing one, and install (not sure which is better since these are basically the first drivers that you should install on a PC and I am not sure how well the PC will work when they are not installed)...

    Id

    - - - Updated - - -

    OK so I removed the Intel chipset sriver.
    Restarted and installed a new one from the MSI site.
    Tried different USB devices - nothing.
    Checked the MSI Center app - it had another chipset update (how could the MSI Center have newer drivers compared to the site I don't know).
    Updated and restarted still nothing.
    I tried all sorts of USB devices - for example a Sandisk 500GB SSD is not recognized and this is the info the USB software shows:

    +++++++++++++++++ Device Information ++++++++++++++++++
    Device Description : WD SCSI Enclosure Device
    Device Path : \\?\SCSI#Enclosure&Ven_WD&Prod_SES_Device#7&1f81e38&0&000001#{1790c9ec-47d5-4df3-b5af-9adf3cf23e48} (GUID_DEVINTERFACE_SES)
    Kernel Name : \Device\000000fb
    Device ID : SCSI\ENCLOSURE&VEN_WD&PROD_SES_DEVICE\7&1F81E38&0&000001
    Hardware IDs : SCSI\EnclosureWD______SES_Device______0___ SCSI\EnclosureWD______SES_Device______ SCSI\EnclosureWD______ SCSI\WD______SES_Device______0 WD______SES_Device______0 ScsiEnclosure
    Driver KeyName : {8496e87e-c0a1-4102-9d8d-bd9a9b8b07a9}\0000
    Driver Inf : C:\Windows\inf\oem44.inf
    Legacy BusType : Internal
    Class : WDC_SAM
    Class GUID : {8496e87e-c0a1-4102-9d8d-bd9a9b8b07a9}
    Enumerator : SCSI
    Location Info : Bus Number 0, Target Id 0, LUN 1
    Address : 0
    Manufacturer Info : Western Digital Technologies
    Capabilities : 0xC0 (RawDeviceOK, SurpriseRemovalOK)
    Status : 0x0180200A (DN_DRIVER_LOADED, DN_STARTED, DN_DISABLEABLE, DN_NT_ENUMERATOR, DN_NT_DRIVER)
    Problem Code : 0

    Windows can't find the driver for it and of course, it is ridiculous to even try to find drivers per device where Windows should have the drivers for most "normal" USB devices such as USBs.

    Any other ideas at this point?
      My Computer


  10. Posts : 113
    Windows 10
       #10

    Do you know what "Device Manager" is? I think you're filtering all my questions about what does Device Manager show. I'd guess that you've fixed the lack of drivers problem or at least the Device Manager code 28 problem (Code 28 "The drivers for this device are not installed" https://support.microsoft.com/en-us/...a-6bca0456324e ), because you've now a code 0 what should mean that the device doesn't have problems related to what Device Manager does. So consider 99% sure that you have USB drivers now. If you want to be 100% sure, go to Device Manager.

    With "all sorts of USB devices" are you meaning all sorts of SSDs and HDDs connected through the same enclosure?

    You could have a physical hw problem that I'm now able to describe more precisely than when I wrote this:

    Does your USB stick with memtest work in other computers? I'm more afraid about your wireless mouse, I would quarantine it (not use it in any computer) until you know for sure what's happening. Motherboards have voltage regulators for USB and they can break for using devices in bad state (this was common years ago, but possibly motherboard makers have invented things to avoid it; bear in mind that USB plugs and sockets have live voltage -5V- and it can do short-circuits, a common result is that mobo USB breaks).

    Add the enclosure to the list of suspects to "quarantine".

    As for the bold part, I've managed to learn that some, many or all modern USB systems have shortcircuit protection. In a thread about a similar problem, one user said something like "you might have a short [shortcircuit] and the motherboard is disabling USB". This would be automatic and could not be reversed by any software until (I suppose) the system is shut down. How many USB devices do you have? Any of them could be doing the short. Your ancient wired mouse seems to be in good condition. A short is physically dangerous for the hw despite the protections. Or do you think that good enough drivers could work around it? I would agree that if the hw can detect the condition and shut down the USB system, the sw might warn the user about it. The perfect place for it would be the Device Manager.
      My Computer


 

  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:20.
Find Us




Windows 10 Forums