BSOD immediately after windows 10 install


  1. SolokVorn
    Posts : 3
    Windows 10
       New #1

    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!
      My Computer
    Quote Quote

  3. Ztruker
    Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       New #2

    Looks like you have a defective hard drive:

    Code:
    Event[12551]:
  Log Name: System
  Source: disk
  Date: 2020-06-05T22:34:26.735
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-S09P8S1
  Description: 
An error was detected on device \Device\Harddisk3\DR41 during a paging operation.

Event[12552]:
  Log Name: System
  Source: disk
  Date: 2020-06-05T22:34:28.526
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-S09P8S1
  Description: 
An error was detected on device \Device\Harddisk3\DR43 during a paging operation.

Event[12553]:
  Log Name: System
  Source: Microsoft-Windows-Ntfs
  Date: 2020-06-05T22:34:28.527
  Event ID: 140
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-S09P8S1
  Description: 
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume49.
(A device which does not exist was specified.)

Event[12554]:
  Log Name: System
  Source: disk
  Date: 2020-06-05T22:34:29.339
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-S09P8S1
  Description: 
An error was detected on device \Device\Harddisk3\DR44 during a paging operation.

Event[12555]:
  Log Name: System
  Source: disk
  Date: 2020-06-05T22:43:14.872
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-S09P8S1
  Description: 
An error was detected on device \Device\Harddisk3\DR51 during a paging operation.

Event[12556]:
  Log Name: System
  Source: disk
  Date: 2020-06-05T22:49:58.944
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-S09P8S1
  Description: 
An error was detected on device \Device\Harddisk3\DR57 during a paging operation.

Event[12557]:
  Log Name: System
  Source: Microsoft-Windows-Ntfs
  Date: 2020-06-05T22:49:58.945
  Event ID: 140
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-S09P8S1
  Description: 
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume63.
(A device which does not exist was specified.)

Event[12558]:
  Log Name: System
  Source: Ntfs
  Date: 2020-06-05T22:50:05.675
  Event ID: 50
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-S09P8S1
  Description: 
{Delayed Write Failed} Windows was unable to save all the data for the file \$Mft. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

Event[12559]:
  Log Name: System
  Source: Application Popup
  Date: 2020-06-05T22:50:05.680
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-S09P8S1
  Description: 
Application popup: Windows - Delayed Write Failed : Exception Processing Message 0xc0000222 Parameters 0x7ffbe1792d58 0x7ffbe1792d58 0x7ffbe1792d58 0x7ffbe1792d58

Event[12560]:
  Log Name: System
  Source: kbdhid
  Date: 2020-06-05T22:56:18.873
  Event ID: 1
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-S09P8S1
  Description: 
The driver has detected that this HID keyboard has bad firmware.  It is issuing redundant report packets.

Event[12561]:
  Log Name: System
  Source: Service Control Manager
  Date: 2020-06-05T23:14:51.438
  Event ID: 7045
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: S-1-5-21-2312749273-1355051714-1760852698-1001
  User Name: DESKTOP-S09P8S1\wesse
  Computer: DESKTOP-S09P8S1
  Description: 
A service was installed in the system.

Service Name:  AMDRyzenMasterDriverV16
Service File Name:  C:\Program Files\AMD\RyzenMaster\bin\AMDRyzenMasterDriver.sys
Service Type:  kernel mode driver
Service Start Type:  auto start
Service Account:  

Event[12562]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2020-06-05T23:22:42.621
  Event ID: 12
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-S09P8S1
  Description: 
The operating system started at system time ?2020?-?06?-?05T21:22:41.500000000Z.
      My Computers
    Quote Quote

  4. SolokVorn
    Posts : 3
    Windows 10
    Thread Starter
       New #3

    Hey !

    Thanks you for the help, how can I found out which of my drives would the problem? I have both an ssd and normal hdd installed. I suspect the ssd since I experienced the same crashes when I unplugged my hdd but from the log you posted, volume F: is probably a usb drive which I remove but I got another bsod while trying to write this reply.

    Can we narrow it down further somehow?
      My Computer
    Quote Quote

  6. Paul Black
    Posts : 18,044
    Win 10 Pro 64-bit v1909 - Build 18363 Custom ISO Install
       New #4

    Hello @SolokVorn,

    As @Ztruker has pointed out it appears that you have a defective HDD!

    SolokVorn said:
    Can we narrow it down further somehow?
    Can you please perform the following [ this checks for ANY Problem Device Errors ] . . .

    [1] Goto this TenForums link => Batch Scripts / Programs.
    [2] Goto the heading Find_ANY_Problem_Devices . . .
    [3] Download and Run the .bat file [ Find_ANY_Problem_Devices.bat ].

    If there are ANY errors it will create a Prob_Devices.txt file on the Desktop!

    [4] Upload the results [ if any! ] => How to Upload and Post Screenshots and Files at Ten Forums.

    I hope this helps!
      My Computer
    Quote Quote

  7. Paul Black
    Posts : 18,044
    Win 10 Pro 64-bit v1909 - Build 18363 Custom ISO Install
       New #5

    Hello @SolokVorn,

    SolokVorn said:
    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.
    Out of interest, what installation media did you use to clean install and where did you get it from!
      My Computer
    Quote Quote

  8. SolokVorn
    Posts : 3
    Windows 10
    Thread Starter
       New #6

    Hey!

    I ran the script and it gave me no problem devices were found.

    Regarding the installation, I actually installed windows 10 twice, the first time I used the install media creator from the windows website giving me version 2004. Since this version of windows seemed to give me problems I retried with windows 1909 which I got from here Direct Download Windows 10 1909 ISO Files (32-Bit / 64-Bit) Officially and put onto a usb using rufus.

    Additionally, my pc seems to run fine in safe mode.

    - - - Updated - - -

    Quick update, i swapped out the ssd for an nvme drive that I was using to run Linux on to tinker with and disconnected all other hard drives. I ran into a blue screen during the account setup process after I installed windows.

    I still keep getting blue screens while using the computer, so I feel the hard drive is not the problem.
      My Computer
    Quote Quote

  9. Ztruker
    Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       New #7

    F: was probably a USB flash drive or external drive. If it has not been connected and you're still getting BSODs then not the cause of the problem.

    Since the problem doesn't occur in Safe Mode, try using Clean Boot to see if you can identify the cause of the BSOD.

    See here: How to Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

    If that doesn't help then it is probably a device driver problem so give Driver Verifier a try:

    Driver Verifier-- tracking down a mis-behaving driver.

    Following the instructions in the above link will check for problems in all non-Microsoft drivers.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

    To check if verifier is active, open a Command Prompt and enter:

    verifier /query

    If not active it will respond with

    No drivers are currently verified.

    If you have questions, see this additional tutorial which may help to clear things up.

    Enable and Disable Driver Verifier in Windows 10
      My Computers
    Quote Quote

 

  Related Discussions
1703 upgrade install had some hiccups for me, so I bit the bullet and did full disk clean install. Deleted all partitions and let Windows installer create them as it wished. Everything goes smoothly, and as soon as its done I check Windows...
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:...
I recently began having issues with Windows 10 (problems with the start menu not opening, the troubleshooter not being able to start, indexing repeatedly turning on and off, etc.), so I decided to do a clean install of Windows. I had some issues...
BSOD immediately after sleep/hibernate
in BSOD Crashes and Debugging

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...
BSOD immediately after waking from sleep
in BSOD Crashes and Debugging

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




Windows 10 Forums