Share via

Different BSODs occuring

Anonymous
2024-02-01T20:11:54+00:00

Hello,

The below mentioned BSODs, and probably a few more with similar wording occur in my newly built system. Most times the occur during startup, shutting down the system, opening browser (Chrome) doing windows updates sometimes. So different cases. First I suspected bad RAM but I have swapped it out to a fresh kit and the problem still occurs. I can game for hours under demanding loads but the BSODs happen at the before mentioned times never during gaming sessions. I suspect some driver to be the culprit but I am kinda stuck here. I have updated the BIOS and ran sfc scannow so far and can safely say it is not thermal issues. The system performs above average in all tests of 3DMark.

PFN_LIST_CORRUPT

KERNEL_SECURITY_CHECK_FAILURE

DRIVER_IRQL_NOT_LESS_OR_EQUAL

PAGE_FAULT_IN_NON_PAGED_AREA

Here is a OneDrive link with the latest 3 minidumps aswell as a save of the msinfo32 https://1drv.ms/f/s!AlPxVbjYWNU9gQyQH4ZVROcXcVjM?e=MwWDW3

Best Regards

Kerem

Windows for home | Windows 11 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

6 answers

Sort by: Most helpful
  1. Anonymous
    2024-02-03T13:31:59+00:00

    In the normal boot environment the Dism tool only caused bluescreens.

    I ran it in safe mode afterwards and this worked, then I reinstalled the newest AMD chipset drivers.

    This did not solve the problem, I will now upload the newest dump files as usual.

    Now trying the solution of Taylor Keays

    Was this answer helpful?

    0 comments No comments
  2. VARADHARAJAN K 9,691 Reputation points Volunteer Moderator
    2024-02-02T17:11:02+00:00

    Bsod caused due to these files ntkrnlmp.exe Ntfs.sys and amdppm.sys

    Reinstall the AMD chipset driver.

    After restoring health by using dism

    Dism /Online /Cleanup-Image /RestoreHealth

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-02-02T13:03:37+00:00

    It seems you might have a potentially corrupted system Image,
    You could be facing some hardware issues, such as RAM, Hard Disk, or motherboard.

    I would suggest checking your BIOS settings for any misplaced configuration,
    Could you tell me what your specs are for your pc?

    another advice :

    maybe a DISM tool repair

    To run the DISM tool,
    hit WIN + R
    type cmd and press control + shift + enter ( this will prompt you to enter administrator )

    Enter these three commands sequentially and one by one

    Dism /Online /Cleanup-Image /CheckHealth

    Dism /Online /Cleanup-Image /ScanHealth

    Dism /Online /Cleanup-Image /RestoreHealth

    let these commands run and wait until they execute.

    I would also suggest Verifying the correct channel of previewers and downloading the correct ISO
    and maybe doing a clean install

    best of luck

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-02-02T12:25:50+00:00

    Hello Lyla,

    I have now ran the Memory Diagnostic Tool - There were no errors.

    I ran chkdsk /f - it did not find any errors

    I have checked if all drivers are the latest version.

    Meanwhile I had another few Bluescreens, I have uploaded all new dumps to the OneDrive Link above.

    The error DPC_WATCHDOG_VIOLATION occured

    Also, Windows updates 2024-01 Windows 11 version 23H2 have failed to install multiple times. The installation does not end in a bluescreen but it fails.

    Best Regards

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-02-02T09:40:51+00:00

    Hello Kerem_TK,

    Welcome to the Microsoft community!  

                    Based on the information you provided, I understand that you have done the BIOS update and run the repair function of

    sfc scannow. According to the log information you provided, among the valid information I got are:

                                    1. PAGE_FAULT_IN_NONPAGED_AREA (50), this error is usually caused by accessing        invalid system memory or memory that has already been freed.

                                    2. rtwlane602.sys is a wireless card driver.

                                    3. fileinfo.sys is a driver related error.

    Here are some steps to troubleshoot:

    Check the memory:

                    1.Tap Windows+R, type MdSched and tap Enter to open the Memory Diagnostic Tool.

                    2.Tap Reboot Now and check for problems

                    3.Follow the prompts to check, wait for it to complete and check the report to see if there is any problem detected.

    Check the hard disk:

                    Search for cmd and run it in administrator mode

                    Type chkdsk c: /f

                    Wait for the check to complete and see if the problem is checked and fixed.

                    Disclaimer: Run chkdsk to check the file system and file system metadata of the volume for logical and physical errors. To avoid causing unnecessary trouble, please follow the above steps step by step and do not interrupt or cancel during the run, and make backups of important data.

    Update drivers:

     It is recommended to update all hardware drivers to ensure that they are the latest version.




    Perform a clean boot:

    Reboot the device after execution to check if the problem is resolved:

    I recommend trying a clean boot****which starts Windows with a minimal set of drivers and startup programs. It can be used to determine whether a background service or program is interfering or causing a problem. 

    These steps of "clean boot" might look complicated at first glance. However, to avoid any trouble for you, please follow them in order and step-by-step. 

    Disclaimer : A *“*clean boot” starts Windows with a minimal set of drivers and startup programs. It helps to determine whether a background service is interfering with your game or program and to isolate the cause of a problem.   

    These steps of "clean boot" might look complicated at first glance. However, to avoid any trouble for you, please follow them in order and step-by step so that it will help you get back on track. 

    I hope the above information can help you. If my understanding is wrong, please point it out so that I can assist you better.



    Best regards,

    Lyla Liu | Microsoft community support expert from MSFT

    Was this answer helpful?

    0 comments No comments