Getting multiple different BSOD crashes tried MANY things

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 10
       #1

    Getting multiple different BSOD crashes tried MANY things


    Hello, I am having issues with my pc. When I use it, I get the blue screen of death with stop codes saying page_fault_in_nonpaged_area (i get this one the most), irql_not_less_or_equal, and unexpected_kernal_mode_trap, KMODE_EXCEPTION_NOT_HANDLED, and more. I have reseated my gpu, and my 3 ram sticks. I have tried using only 1 of each of the ram sticks. I have reset my pc and kept my files. I have tried having no paging file. I have done chkdsk on my pc and it did find corrupted things and fixed it but the issue still persists. I have contacted Microsoft support and they're very slow on responding. They told me to contact NVIDIA support and they can't figure out how to fix my issue either. I have installed the latest drivers for my motherboard and graphics card. I dont know what that is. I have made sure that all my drivers are up to date and I am on the latest windows update. My windows version number is 19041.450. The files provided are the files given to me from V2 Log collector.
    Getting multiple different BSOD crashes tried MANY things Attached Files
      My Computer


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

    Did you recently increase your RAM? You have mismatched RAM, two 4GB DIMMs and one 8GB DIMM.

    You've had 81 recorded BSODs:

    12 Unique Bug Check codes: 01e 050 03b 0d1 0d3 007 018 07f 666 004 05a 000

    P1: 0X0000001E 08/26/2020 01:12 AM P1: 0X0000001E 08/26/2020 01:11 AM
    P1: 0X00000050 08/25/2020 11:18 PM P1: 0X00000050 08/25/2020 11:17 PM
    P1: 0X00000050 08/25/2020 10:38 PM P1: 0X00000050 08/25/2020 09:47 PM
    P1: 0X00000050 08/25/2020 09:23 PM P1: 0X00000050 08/25/2020 09:23 PM
    P1: 0X00000050 08/25/2020 09:12 PM P1: 0X00000050 08/25/2020 09:12 PM
    P1: 0X0000003B 08/25/2020 08:30 PM P1: 0X0000003B 08/25/2020 08:28 PM
    P1: 0X0000003B 08/25/2020 08:28 PM P1: 0X00000050 08/25/2020 08:12 PM
    P1: 0X00000050 08/25/2020 08:12 PM P1: 0X0000001E 08/25/2020 06:27 AM
    P1: 0X0000001E 08/25/2020 06:01 AM P1: 0X0000003B 08/25/2020 05:24 AM
    P1: 0X0000003B 08/25/2020 05:22 AM P1: 0X0000003B 08/25/2020 05:22 AM
    P1: 0X0000003B 08/25/2020 03:42 AM P1: 0X0000003B 08/25/2020 03:03 AM
    P1: 0X00000050 08/25/2020 12:23 AM P1: 0X00000050 08/25/2020 12:22 AM
    P1: 0X00000050 08/24/2020 11:51 PM P1: 0X00000050 08/24/2020 11:51 PM
    P1: 0X00000050 08/24/2020 11:26 PM P1: 0X00000050 08/24/2020 11:25 PM
    P1: 0X00000050 08/24/2020 11:09 PM P1: 0X00000050 08/24/2020 11:09 PM
    P1: 0X000000D1 08/24/2020 09:26 PM P1: 0X000000D1 08/24/2020 09:26 PM
    P1: 0X00000050 08/24/2020 06:55 PM P1: 0X000000D3 08/24/2020 06:55 PM
    P1: 0X00000050 08/24/2020 06:55 PM P1: 0X000000D3 08/24/2020 06:54 PM
    P1: 0X000000D3 08/24/2020 06:10 PM P1: 0X000000D3 08/24/2020 06:10 PM
    P1: 0X00000050 08/24/2020 06:00 PM P1: 0X00000050 08/24/2020 02:57 PM
    P1: 0X00000050 08/24/2020 02:57 PM P1: 0X00000050 08/24/2020 02:57 PM
    P1: 0X000000D1 08/24/2020 08:32 AM P1: 0X00000050 08/24/2020 03:10 AM
    P1: 0X00000050 08/24/2020 03:09 AM P1: 0X00000018 08/24/2020 02:39 AM
    P1: 0X00000018 08/24/2020 02:39 AM P1: 0X0000007F 08/24/2020 02:20 AM
    P1: 0X0000007F 08/24/2020 02:20 AM P1: 0X00000050 08/24/2020 02:00 AM
    P1: 0X00000050 08/24/2020 02:00 AM P1: 0X00000050 08/24/2020 12:54 AM
    P1: 0X00000050 08/24/2020 12:54 AM P1: 0X0000003B 08/24/2020 12:25 AM
    P1: 0X0000003B 08/24/2020 12:22 AM P1: 0X0000003B 08/24/2020 12:22 AM
    P1: 0X00000050 08/23/2020 11:45 PM P1: 0X00000050 08/23/2020 11:43 PM
    P1: 0X00000050 08/23/2020 09:41 PM P1: 0X00000050 08/23/2020 09:41 PM
    P1: 0X00000050 08/23/2020 08:43 PM P1: 0X00000050 08/23/2020 08:43 PM
    P1: 0X00000050 08/23/2020 06:48 PM P1: 0X00000050 08/23/2020 06:48 PM
    P1: 0X00000050 08/23/2020 10:07 AM P1: 0X00000050 08/23/2020 10:04 AM
    P1: 0X00000050 08/23/2020 10:04 AM P1: 0X0000003B 08/23/2020 08:53 AM
    P1: 0X0000003B 08/23/2020 08:52 AM P1: 0X00000050 08/23/2020 07:14 AM
    P1: 0X00000050 08/23/2020 07:13 AM P1: 0X00000050 08/23/2020 06:16 AM
    P1: 0X00000050 08/23/2020 06:15 AM P1: 0X00000050 08/23/2020 01:56 AM
    P1: 0X00000050 08/23/2020 01:55 AM P1: 0X00000050 08/23/2020 12:09 AM
    P1: 0X00000050 08/22/2020 10:52 PM P1: 0X00000050 08/22/2020 10:50 PM
    P1: 0X00000050 08/22/2020 10:50 PM P1: 0X0000003B 08/22/2020 09:11 AM
    P1: 0X0000003B 08/22/2020 09:11 AM

    Remove either the 8GB DIMM or the two 4GB DIMMs and run that way for awhile and see if you still get BSODs or not.

    Dumps were not very interesting and I didn't see anything useful int he event logs either.
      My Computers


  3. Posts : 7
    Windows 10
    Thread Starter
       #3

    recently I threw away an 8gb ram stick due to it dying. I tried all 3 of the ram sticks all alone already and the problem still persisted
      My Computer


  4. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #4

    How long did you run with each one installed? Did you get a BSOD with each one installed or no BSOD with each one installed?
      My Computers


  5. Posts : 7
    Windows 10
    Thread Starter
       #5

    I dont really remember how long, it's pretty random. I got a BSOD with each one individually. I am willing to try again if needed, it is possible I mixed two up because they look exactly the same.
      My Computer


  6. Posts : 41,475
    windows 10 professional version 1607 build 14393.969 64 bit
       #6

    The V2 log collector didn't collect dxdiag.
    Please run each V2 and DM > upload results directly into this thread:
    BSOD - Posting Instructions


    1) Run HD Tune (free version) (all drives)
    HD Tune website
    Post images into the thread for results on these tabs:
    a) Health
    b) Benchmark
    c) Full error scan

    2) Run Sea Tools for Windows
    long generic test
    Post an image of the test result into the thread
    SeaTools for Windows |
    Seagate

    How to use SeaTools for Windows | Seagate Support US

    3) Open administrative command prompt and type or copy and paste:
    chkdsk /b /v
    This may take hours to run so plan to run overnight.
    Run on all drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: changing the drive letter to the applicable drive.

    C:\Windows\system32>chkdsk /b /v
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot


    4) Use the information in this link to find the chkdsk report in the event viewer.
    Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
    Read Chkdsk Log in Event Viewer in Windows 10



    Code:
    Event[4598]:
      Log Name: System
      Source: disk
      Date: 2020-08-25T17:07:44.7420000Z
      Event ID: 7
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-GM2RQ7M
      Description: 
    The device, \Device\Harddisk1\DR1, has a bad block.

    Code:
    Model	Hitachi HUA723020ALA641
    Code:
    Model	TOSHIBA DT01ACA100 ATA Device
      My Computer


  7. Posts : 7
    Windows 10
    Thread Starter
       #7

    I cannot do the last three steps because they take too long and my computer BSOD's every time.

    Images:
    Getting multiple different BSOD crashes tried MANY things-cdrive.pngGetting multiple different BSOD crashes tried MANY things-cdrive2.pngGetting multiple different BSOD crashes tried MANY things-cdrive3.png
    Getting multiple different BSOD crashes tried MANY things-ddrive.pngGetting multiple different BSOD crashes tried MANY things-ddrive2.pngGetting multiple different BSOD crashes tried MANY things-ddrive3.png
    All of the rows in the health tab said ok.

    New crash dmp files.
    Dump files.
      My Computer


  8. Posts : 41,475
    windows 10 professional version 1607 build 14393.969 64 bit
       #8

    1) Run tuneup.bat
    Batch files for use in BSOD debugging


    2) Find a flash drive that you can format (> or = 8 GB).

    3) Create a bootable Windows 10 iso 2004:

    https://www.microsoft.com/en-us/soft...load/windows10
    Download Windows 10 ISO File
    Create Bootable USB Flash Drive to Install Windows 10

    4) Open command prompt at boot:
    Open Command Prompt at Boot in Windows 10

    5) type:
    diskpart
    lis dis
    lis vol
    exit

    chkdsk /b /r W:
    (change W: to each vol drive letter displayed)
    (plan to run overnight)


    6) Find another flash drive.
    SeaTools | Seagate Support US
    7) Create Sea Tools bootable > run long generic test


    Code:
    ------------------------
    Disk & DVD/CD-ROM Drives
    ------------------------
          Drive: C:
     Free Space: 474.3 GB
    Total Space: 953.2 GB
    File System: NTFS
          Model: TOSHIBA DT01ACA100 ATA Device
    
          Drive: D:
     Free Space: 0.5 GB
    Total Space: 0.5 GB
    File System: NTFS
          Model: Hitachi HUA723020ALA641
    
          Drive: E:
     Free Space: 1807.7 GB
    Total Space: 1907.2 GB
    File System: NTFS
          Model: Hitachi HUA723020ALA641
      My Computer


  9. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #9

    All the recent crashes you are getting seem to be from Driver Verifier. Why is this running? I suggest you turn it off.

    Type Verifier /reset in a command prompt.window.

    If you have any trouble doing this refer to this tutorial: Enable and Disable Driver Verifier in Windows 10

    In addition to the above you have a number of really old drivers running from the ASRock set of utilities. I would be inclined to remove all these as some have been associated with BSOD events in the past.
      My Computers


  10. Posts : 7
    Windows 10
    Thread Starter
       #10

    philc43 said:
    All the recent crashes you are getting seem to be from Driver Verifier. Why is this running? I suggest you turn it off.

    Type Verifier /reset in a command prompt.window.

    If you have any trouble doing this refer to this tutorial: Enable and Disable Driver Verifier in Windows 10

    In addition to the above you have a number of really old drivers running from the ASRock set of utilities. I would be inclined to remove all these as some have been associated with BSOD events in the past.
    I just downloaded driver verifier yesterdau to get the latest drivers. I'll just uninstall it. Also how would I locate and remove the old ASRock drivers?
      My Computer


 

  Related Discussions
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 06:44.
Find Us




Windows 10 Forums