Windows 10: BSOD immediately after windows 10 install

Discus and support BSOD immediately after windows 10 install in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello all, For the past week I've been fighting with my fresh windows 10 install that I did last sunday trying to figure out why it's blue screening... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by SolokVorn, Jun 5, 2020.

  1. SOLOKVORN
    SolokVorn Win User

    BSOD immediately after windows 10 install


    Hello all,

    For the past week I've been fighting with my fresh windows 10 install that I did last sunday trying to figure out why it's blue screening so much.
    I have seen a wide varity from driver_irql_not_less_than_or_equal, kernel_security_check_failure and a few more that i forgot.

    I hope that by reaching out to the community here I can figure out what's up.

    I ran memtestx86 and it came back with 0 errors.

    The memory, motherboard and cpu in my pc are a few months old, gfx card, harddrives and wifi adapter are older components that I did not upgrade.

    I'm currently on 1909 build 18363.418

    I attached the zip per posting instructions.

    I look forward to your reaction and help!

    :)
     
    SolokVorn, Jun 5, 2020
    #1
  2. EXODUSPRIME1337
    exodusprime1337 Win User

    windows xp installation and dual core am

    could someone please list the steps they follow to install windows with a dual core processor and windows xp service pack to. I'm reletively new to amd dual core and i feel i'm missing a step. All help will be appreciated. thanx
     
    exodusprime1337, Jun 5, 2020
    #2
  3. DELTA6326
    Delta6326 Win User
    Delta6326, Jun 5, 2020
    #3
  4. CK011885
    CK011885 Win User

    BSOD immediately after windows 10 install

    Installing Windows 10 on New PC?

    I'm going to be building a new PC on Christmas and want to install Windows 10 on it. I have Windows 10 on my current PC, which I installed upgrading from 8.1 with the files on a USB. How do I go about installing a clean copy of Windows 10 on this new PC? I think I recall something about installing it once makes Microsoft recognize your hardware, but since this will be a PC I'm not sure what steps I need to take. Do I need to go 8.1 -> 10 or is there a method of going directly to 10?
     
    CK011885, Jun 5, 2020
    #4
Thema:

BSOD immediately after windows 10 install

Loading...

  1. BSOD immediately after windows 10 install - Similar Threads - BSOD immediately install

  2. Windows 10 installer starts and closes immediately

    in Windows 10 Software and Apps
    Windows 10 installer starts and closes immediately: Hi,I am a user of Windows 7 Professional.I wanted to dual boot my PC with Windows 10 Home.I was searching for how to dual boot without USB Drive and also I found a video which was saying that I would find a file named setup.exe from the ISO after extracting...The path is...

  3. Windows 10 freezes immediately after install

    in Windows 10 Ask Insider
    Windows 10 freezes immediately after install: I hate asking for help but I’m stumped. I bought two Dell Precision m2800 i7 laptops. Both came with 256gb ssds. I replaced those with a 500gb and a 1TB ssd and then installed windows 10 pro from a USB stick. Both machines froze immediately after full installation and upon...

  4. Windows 10 Freezing then immediately restarting. No BSOD.

    in Windows 10 Ask Insider
    Windows 10 Freezing then immediately restarting. No BSOD.: This just started recently, maybe a month ago. I just got this PC last Black Friday. It has Windows 10 version 1809 installed. When I'm playing a game it will randomly freeze, my speakers make a buzzing sound for 2-3 seconds, then the PC restarts with no blue screen of death....

  5. BSOD after windows 10 install

    in Windows 10 BSOD Crashes and Debugging
    BSOD after windows 10 install: Specs: Lenovo Y50-70 laptop, intel i7-4710HQ with intel hd 4600, nvidia gtx 860m and 16 GB ddr3 ram. Installed windows 10 and it automatically downloaded all the drivers including intel and nvidia. After 2 reboots the laptop felt slower and things would take ages to open,...

  6. BSOD immediately after booting, System_Thread_Exception_Not_Handled

    in Windows 10 BSOD Crashes and Debugging
    BSOD immediately after booting, System_Thread_Exception_Not_Handled: Hi, So this is the 4th time my PC has crashed because of the same file in the past 2 years. The file that is constantly causing the BSOD is rtsuvc.sys which is the Lenovo EasyCamera driver, ie Webcam driver. Error: System_Thread_Exception_Not_Handled File: rtsuvc.sys...

  7. BSOD immediately after sleep/hibernate V2

    in Windows 10 BSOD Crashes and Debugging
    BSOD immediately after sleep/hibernate V2: This is just a continuation of a previous thread which was marked as too old. See BSOD immediately after sleep/hibernate Had another BSOD immediately after returning from hibernate. I checked the disk again but saw no further errors so I can rule out the disk this time...

  8. BSOD After Windows 10 Install

    in Windows 10 BSOD Crashes and Debugging
    BSOD After Windows 10 Install: Hello... I recently did a clean install of Windows 10. I've gotten a couple of BSOD occurrences. The most recent was a IRQL_NOT_LESS_OR_EQUAL. The previous one was different, but I don't recall the error message. Please let me know what you think. Thank you......

  9. BSOD immediately after waking from sleep

    in Windows 10 BSOD Crashes and Debugging
    BSOD immediately after waking from sleep: Hi All. I'm getting a blue screen advising "ATTEMPTED_WRITE_TO_READONLY_MEMORY" a couple of seconds after my computer wakes from sleep mode. It's not sporadic as it happens every time. I've downloaded the log collector and attached the ZIP file to this post. First time...

  10. BSOD immediately after sleep/hibernate

    in Windows 10 BSOD Crashes and Debugging
    BSOD immediately after sleep/hibernate: I sometimes get a failure from either Corrupt Page or Memory Management after returning from either sleep mode or hibernate. Always caused by ntoskrnl.exe+142940. I wonder if it might be caused by my trying to log in too soon and the different threads running before memory...