regular bluescreen

Discussion in 'UDOO BOLT' started by GerbenT, May 3, 2019.

  1. GerbenT

    GerbenT UDOOer

    Joined:
    Apr 17, 2019
    Messages:
    24
    Likes Received:
    7
    windows version 10.0.17763.475 (1809)
    Did use Linux for a while, not that long, dont remember similar problems.
    I have also posted the driver version I'm using somewhere

    Does Linux have blue screen errors ?
     
  2. evaloverde

    evaloverde Administrator Staff Member

    Joined:
    Apr 29, 2019
    Messages:
    189
    Likes Received:
    53
    A possible solution to the issue is...
    - install all the windows update from "check for updates"
    - uninstall the AMD video driver with "AMDCleanupUtility"
    - install again the latest AMD driver for the v1000 processor

    Try this and let me know if it works

    PS. At the moment there have been no issues using Linux OS
     
  3. GerbenT

    GerbenT UDOOer

    Joined:
    Apr 17, 2019
    Messages:
    24
    Likes Received:
    7
    what does your bluescreen error say ? ( error message in the left bottom corner )
     
  4. GerbenT

    GerbenT UDOOer

    Joined:
    Apr 17, 2019
    Messages:
    24
    Likes Received:
    7
    Hi Evaloverde,
    did the update, no updates ..
    the cleanup utility is here now https://www.amd.com/en/support/kb/faq/gpu-601
    installed the latest drivers.

    Radeon Settings Version - 2019.0214.2111.38149
    Driver Packaging Version - 18.50.23.01-190214a-339558C-AES
    Provider - Advanced Micro Devices, Inc.
    2D Driver Version - 8.1.1.1634
    Direct3D® Version - 9.14.10.01377
    OpenGL® Version - 25.20.15000.13547
    OpenCL™ Version - 25.20.15023.1001
    AMD Audio Driver Version - 10.0.1.7
    Vulkan™ Driver Version - 2.0.68
    Vulkan™ API Version - 1.1.96

    and we'll see.

    Funny thing is that you can't see on the website if there are new drivers, I've used file 18.50.190214a-339558c-aes (latest I can download) , then the driver does an update over the internet and jumped to version 18.50.23.01 .. So it is possible I've been using that for a while now ...

    I'll see what happens when I install ubuntu 19.04 on the onboard emmc.
     
    evaloverde likes this.
  5. evaloverde

    evaloverde Administrator Staff Member

    Joined:
    Apr 29, 2019
    Messages:
    189
    Likes Received:
    53
    Let me know how things progress
     
  6. GerbenT

    GerbenT UDOOer

    Joined:
    Apr 17, 2019
    Messages:
    24
    Likes Received:
    7
    Hi , that did not seem to help , sttll can't leave the pc alone and come back to a working box. Also found myself a new bluescreen error today. How is the testing going , can you reproduce the error ?

    Installing ubuntu 19.04 onto the internal eMMC does not seem to work out of the box, so yeah ... will need to look through the forum to see how that works.
     

    Attached Files:

  7. evaloverde

    evaloverde Administrator Staff Member

    Joined:
    Apr 29, 2019
    Messages:
    189
    Likes Received:
    53
    Hello, have you installed Windows on the EMMc?
    Can you try to open up the event viewer and look for errors and warnings before the issue happens?
    We posted a guide on the Ubuntu issue, as it's a known issue. It's here

    Again, let me know how things progress
     
  8. GerbenT

    GerbenT UDOOer

    Joined:
    Apr 17, 2019
    Messages:
    24
    Likes Received:
    7
    So it was a while, but found some time ... by now we have windows 1903 so I installed that, for this windows version there is an whole new amd driver ... 19h1 ... This install has not had any bluescreens and does not come up with errors after turning the box on again after I've been away from the computer.

    The v18 driver does not auto update or manually update to this version. And they are both on the AMD site and it looks like they are specific for the windows version you are using.

    https://www.amd.com/en/support/embe...rocessors/v-series-v1000-radeon-vega-graphics

    I'm afraid we can't really draw any conclusions because this install is on nvme storage

    I did have some access problems with the emmc on windows but those have also dissapeared

    Going to reinstall the whole box now to do some more tests.
     
    waltervl likes this.
  9. GerbenT

    GerbenT UDOOer

    Joined:
    Apr 17, 2019
    Messages:
    24
    Likes Received:
    7
    So, The bluescreens are gone so far with the newer drivers (still on windows here) But the problems with the eMMC persist. after a couple of minutes of windows use (of the NVME) the active time in task manager goes to 100% and stays there. And the storage is unresponsive. Do I go about making a new topic or keep it here ? ... I would like to know how I can test the eMMC and see if it is defective ? I'm not running a professional shop here but have the feeling it got worse with either this verion of winows (1903) or the new driver that goes with that version of windows.
     
  10. waltervl

    waltervl UDOOer

    Joined:
    Dec 12, 2015
    Messages:
    2,236
    Likes Received:
    561
    I would prefer to make a new topic for your eMMC issue.
     
  11. ej_1090

    ej_1090 UDOOer

    Joined:
    Nov 9, 2019
    Messages:
    5
    Likes Received:
    3
    Any updates on this BSOD issue? Having the same problems here.

    Dump File Begin:
    ==================================================
    Dump File : 111119-6359-01.dmp
    Crash Time : 11/11/2019 6:40:30 PM
    Bug Check String : IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    Bug Check Code : 0x0000004a
    Parameter 1 : 00007ffb`8371c1a4
    Parameter 2 : 00000000`00000002
    Parameter 3 : 00000000`00000000
    Parameter 4 : ffffa70c`83a6fb80
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+1c1220
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 10.0.18362.418 (WinBuild.160101.0800)
    Processor : x64
    Crash Address : ntoskrnl.exe+1c1220
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\111119-6359-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 18362
    Dump File Size : 790,540
    Dump File Time : 11/11/2019 6:41:24 PM
    ==================================================
    Dump File End:

    I will start keeping the dump files for further analysis if necessary.

    System Info: UDOO Bolt V8
    Operating System: Microsoft Windows 10 Professional (x64) Build 18362.418 (1903/May 2019 Update)
    BIOS REV: 1.05 R.C. 8
    System BIOS Version: 5.13
    Embedded Controller Firmware Version: 0.16
    Dell 120W 19V Power Supply

    AMD Catalyst Windows®10 19H1 64-bit Display Driver
    Revision Number: 19.30.01r

    Memory: (x2)
    (DDR4-2400 / PC4-19200)
    G Skill - F4-2400C16-16GRS

    Monitor: (x2) DELL P2217H (using USB hub on both)

    M.2 NVMe SSD:
    Drive Model: HP SSD EX900 250GB

    Network Card: Intel 8265 Tri-Band WiFi (Oak Peak) Network Adapter
    Driver Version: 20.70.13.2
     
  12. chrisr

    chrisr UDOOer

    Joined:
    Nov 1, 2013
    Messages:
    27
    Likes Received:
    8
    I am having exactly the same problem. Bolt v8 with 16GB RAM , 1TB NVME SSD, Windows 10 (latest version 1909), Radeon drivers (latest version 18.50.33.08). All working fine for a couple of hours then bluescreen with Stop code: DRIVER_POWER_STATE-FAILURE. This is making the otherwise excellent Bolt unusable due to it's unreliability. I am not using eMMC at all.

    Do many other people have this problen and how can it be solved?

    Udoo team - are you able to replicate the problem?

    Thanks
     
  13. evaloverde

    evaloverde Administrator Staff Member

    Joined:
    Apr 29, 2019
    Messages:
    189
    Likes Received:
    53
    Hey there,
    the last available driver it's the version 19.30 for Windows 19H1. Even if you're not using the eMMC, try disabling it from the device manager, until the team that's handling the BIOS will find a more definitive solution.

    Let us know if the problem gets solved by using this method.
     
  14. someone_passingby

    someone_passingby UDOOer

    Joined:
    Oct 3, 2019
    Messages:
    24
    Likes Received:
    7
    Hi Eva,

    I had the exact same issue OP is experiencing.
    I can confirm that this definitely worked on my V8.

    Symptoms:

    - BSOD with DRIVER_STATE_FAILURE
    - System shutdown takes very long (roughly 10-15mins)

    How I resolved:

    I was skimming thru Kickstarter comments and accidentally found out someone's advice to "Disable eMMC in Device Manager" whether you use it or not. Eva left an appreciation comment, so I gave it a shot with good omen.

    Result:

    - No more BSOD with DRIVER_STATE_FAILURE (sometimes other BSOD appears, but at least not this one. Still, it's much more stable now)
    - Shutdown process is now normal just like other PCs I have.

    Some extra info:

    - "Only" change was simply disabling eMMC in Device Manager.
    - AMD Chipset 19.10 + Win10 19H1, which never changed.

    Those experiencing lengthy shutdown time, plz give it a shot.
    Thanks Eva for your hard work!
     
    evaloverde and chrisr like this.
  15. chrisr

    chrisr UDOOer

    Joined:
    Nov 1, 2013
    Messages:
    27
    Likes Received:
    8
    Thanks for the replies. Where is the disable eMMC in Windows Device Manager? Looking in mine at the Disk Drives, there is one called "SanDisk DF4032" as well as my M.2 SSD. Sinve I don't have a SanDisk DF4032, is this the eMMC? Would appreciate a reply before I disable the wrong thing! Thank you.
     
  16. chrisr

    chrisr UDOOer

    Joined:
    Nov 1, 2013
    Messages:
    27
    Likes Received:
    8
    Re message above, just checked and I forgot I installed Ubuntu on the eMMC a while ago. Is this why it is not showing in Windows Device Manager? Happy to remove Ubuntu from the eMMC if that helps?
     
  17. someone_passingby

    someone_passingby UDOOer

    Joined:
    Oct 3, 2019
    Messages:
    24
    Likes Received:
    7
    Here you go:

    Capture.PNG

    Code:
    SanDisk DF4032
    is the eMMC soldered to Bolt. Simply right click on it and disable it.
    Hope you enjoy your Bolt!
     
    evaloverde likes this.
  18. someone_passingby

    someone_passingby UDOOer

    Joined:
    Oct 3, 2019
    Messages:
    24
    Likes Received:
    7
    Not sure about this part, but on my side it does appear on Device Manager when Disk Management does not show it.
    Capture.PNG
     
  19. chrisr

    chrisr UDOOer

    Joined:
    Nov 1, 2013
    Messages:
    27
    Likes Received:
    8
    Thanks for your reply. Don't seem to have an option to disable this in Device Manager. See photos for right click and properties - Disable Device is greyed out!

    1.jpg 2.jpg

    It does appear in Disk Manaagement - tried Deleteing it and then formatting it as NTFS in there, calling it eMMC /Dive D and it shows as:
    3.jpg
    Not sure about the 512MB EFI system partition?
    My Windows installation is on a separate SSD (Disk 0 / C).

    Still stuck I am afraid. Thanks.
     
  20. chrisr

    chrisr UDOOer

    Joined:
    Nov 1, 2013
    Messages:
    27
    Likes Received:
    8
    OK - fixed this. My SSD did not have the EFI partition information, only the eMMC which is why I could not disable the eMMC. There is an easy guide to move the EFI partition here https://www.tenforums.com/installation-upgrade/52837-moving-recreating-efi-partition.html It can be done from the administrator command prompt in Windows. Having moved the partition I set up the boot order at startup in the BIOS screen to this and removed the eMMC EFI from the boot options. All rebooted fine and I now had the option to disable the SanDisk DF4032 (eMMC) in Windows Device Manager. Have done this and thge disk has disappeared from Disk Management. So hopefully all now OK - will report back in a few days if the BSOD has gone. Thanks for your help Eva and someone_passingby! Hopefully if anyone else has this problem these posts will be helpful
     
    someone_passingby and evaloverde like this.

Share This Page