Results 1 to 10 of 10
  1. #1
    Star Lounger
    Join Date
    Apr 2001
    Location
    Melbourne, Australia
    Posts
    53
    Thanks
    2
    Thanked 1 Time in 1 Post

    Win10 install fails immediately with 'system thread exception not handled' error

    I am trying to install the Win10 preview in an Oracle VM VirtualBox, as described by Fred Langa in http://windowssecrets.com/top-story/...-step-by-step/.

    As soon as the VM boots from the ISO file, it displays the blue 4-pane window, but a few seconds later, fails with the message: ”system thread exception not handled”, after which it reboots. This continues indefinitely.

    I have tried to find references that might be relevant, but the only hit that seemed to be possible referred to an old video card and drivers.

    Does anyone have any thoughts on what might be the problem here, and about possible ways to get past that point?

    Thanks.
    Geoffrey

  2. #2
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,486
    Thanks
    283
    Thanked 574 Times in 478 Posts
    Not sure how this relates within a VM, more details in the linked article:
    STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

  3. #3
    Banned Member
    Join Date
    Mar 2012
    Location
    Calgary
    Posts
    2,522
    Thanks
    0
    Thanked 170 Times in 142 Posts
    Geoffrey,

    Are you running 8.1?

    Cheers,
    Drew
    Attachment 42675

  4. #4
    Banned Member
    Join Date
    Mar 2012
    Location
    Calgary
    Posts
    2,522
    Thanks
    0
    Thanked 170 Times in 142 Posts
    That list of causes covers a lot of ground.

    Cheers,
    Drew
    Attachment 42676

  5. #5
    jwoods
    Guest
    That error can indeed be caused by the graphics card, or outdated drivers.

    You might check to see if your installed card meets the minimum requirements for Windows 10.

    http://windows.microsoft.com/en-us/w...equirements-pc

    If it does, check the vendor's site and see if there are any driver updates for the card.
    Last edited by jwoods; 2015-04-16 at 03:00.

  6. #6
    Star Lounger
    Join Date
    Apr 2001
    Location
    Melbourne, Australia
    Posts
    53
    Thanks
    2
    Thanked 1 Time in 1 Post
    Quote Originally Posted by Drew1903 View Post
    Are you running 8.1?
    Sorry, should have been more explicit. I am running Windows 7 SP1.

  7. #7
    Star Lounger
    Join Date
    Apr 2001
    Location
    Melbourne, Australia
    Posts
    53
    Thanks
    2
    Thanked 1 Time in 1 Post
    Quote Originally Posted by jwoods View Post
    You might check to see if your installed card meets the minimum requirements for Windows 10.
    Yes, I believe it does. I am running a supported video card with DirectX 11 and WDDM. My drivers are up to date.

    But thanks for confirming that this is a possible area of difficulty.

  8. #8
    jwoods
    Guest
    You might also run the Windows 8.1 Upgrade Assistant to see if there are any incompatibilities...

    http://windows.microsoft.com/en-us/w...ows-7-tutorial

    If your system will run 8.1, it will run Windows 10, according to Microsoft.
    Last edited by jwoods; 2015-04-16 at 17:19.

  9. #9
    Star Lounger
    Join Date
    Apr 2001
    Location
    Melbourne, Australia
    Posts
    53
    Thanks
    2
    Thanked 1 Time in 1 Post

    Resolved

    Resolved now.

    Thanks to all who responded. I bit the bullet and purchased a new video controller, upgrading from the old GEForce 220. Once I did that, the problem has been resolved. It seems, therefore, that it was not a driver issue, but a hardware issue.

  10. #10
    Banned Member
    Join Date
    Mar 2012
    Location
    Calgary
    Posts
    2,522
    Thanks
    0
    Thanked 170 Times in 142 Posts
    Glad to hear your good news. This part, "It seems, therefore, that it was not a driver issue, but a hardware issue.", doesn't seem too surprising, @ all.

    Cheers,
    Drew
    Attachment 42732

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •