Frequent Various BSOD crashes

Page 1 of 2 12 LastLast

  1. levolpehh
    Posts : 8
    Windows 10
       New #1

    Frequent Various BSOD crashes


    Hello, for the last 2-3 days out of nowhere the last 2-3 days my computer has been getting a variety of different BSODs. Many of which point to faulty hardware, drivers, or memory problems. I've tried a few things including updating any outdated drivers, and restoring the computer, but it's starting back up again. My build is fairly new, got it about 2 months ago and has worked since then with no problems. I have also tried installing some anti malware stuff to see if maybe that was part of the problem. It's gotten to the point I can't even do a system update or system restore without getting a BSOD before it finishes. Today it ran perfectly fine for about 8-9 hours before dying on me, back to back. It's worked fine again the last hour or so... I've tried narrowing down the causes but I'm so lost at this point cause everything I try doesn't work. So I leave myself in your care. Thank you!

    I'm getting the following Stop Errors:
    Attempted to Write Read Only
    Memory Management
    IRQL Not Less or Equal
    Kmode Exception Not Handled
    IRQL G Zero at System Service
    Bad Pool Header
    Page Fault at Nonpage Area
    PFN List Corrupt (Came up when trying to diagnose through some cmd stuff)

    Computer Specs:
    SSD: SAMSUNG 860 EVO Series 2.5" 500GB SATA III V-NAND 3-bit MLC Internal Solid State Drive (SSD) MZ-76E500B/AM

    GPU: GIGABYTE GeForce GTX 1060 DirectX 12 GV-N1060WF2OC-6GD 6GB 192-Bit GDDR5 PCI Express 3.0 x16 ATX Video Card

    Power Supply: EVGA SuperNOVA 750 G2 220-G2-0750-XR 80+ GOLD 750W

    M/B: ASRock AB350 Pro4 AM4 AMD Promontory B350 SATA 6Gb/s USB 3.1 HDMI ATX AMD Motherboard

    RAM: G.SKILL Ripjaws V Series 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 3200 (PC4 25600) Intel Z170 Platform / Intel X99 Platform Desktop Memory Model F4-3200C16D-16GVKB

    Processor: AMD RYZEN 7 1800X 8-Core 3.6 GHz (4.0 GHz Turbo) Socket AM4 95W YD180XBCAEWOF Desktop Processor
    Last edited by levolpehh; 17 Dec 2018 at 21:10.
      My Computer
    Quote Quote

  3. zbook
    Posts : 41,480
    windows 10 professional version 1607 build 14393.969 64 bit
       New #2

    Hi levolpehh,

    Welcome to the Ten Forums BSOD forum.

    Perform the following steps:

    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /restorehealth
    4) chkdsk /scan
    5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    6) Make sure that there is no over clocking while troubleshooting.

    7) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread.

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

    8) Open Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

    9) There are two log collectors: DM and BETA
    Run the BETA log collector and post a zip into this thread:

    BSOD - Posting Instructions - Windows 10 Forums
    https://www.tenforums.com/attachment...-v2-beta15.zip
    (extract all > open)

    10) Uninstall Malwarebytes using the applicable uninstall tool:
    https://downloads.malwarebytes.com/file/mb_clean

    11) Malwarebytes can be reinstalled one week after the last BSOD

    12) Uninstall and reinstall Nvidia GPU drivers: nvlddmkm.sys

    13) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
    14) re-install the Nvidia GPU driver from the Nvidia website
    15) make sure that you check the clean install box and if available install the physx driver.

    Display Driver Uninstaller Download version 18.0.0.4 (or newer version if available)
    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    NVIDIA
    Download Display Driver Uninstaller - MajorGeeks

    16) The BIOS: Version/Date American Megatrends Inc. P4.60, 2018-01-15
    Upgrade the BIOS: 4.6 > 5.1
    ASRock > AB350 Pro4

    Code:
    2018-12-17 12:11 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 19
P2: e
P3: ffffcf096cb52d60
P4: 1040102
P5: c6aa402bcaa36c94
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121618-7187-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10171-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER324B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER325B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER326A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER327A.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_19_e99b38dec278419b27d2c1d6ae284363e3084d8_00000000_03283279

Analysis symbol: 
Rechecking for solution: 0
Report Id: 84e45eec-b375-4269-b68f-60d234d52e59
Report Status: 4
Hashed bucket: 
Cab Guid: 0
2018-12-16 3:00 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1a
P2: 403
P3: ffffc932cccf3578
P4: 80000002ffcc6867
P5: fff0c932cccf3578
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\121518-5109-01.dmp
\\?\C:\Windows\TEMP\WER-8484-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B84.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B95.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BA3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BB4.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_4c875f7982848b8667fac062aa3179354cb698_00000000_cab_0d04c841

Analysis symbol: 
Rechecking for solution: 0
Report Id: a10cfbd9-d089-4480-ac86-9802232f7e79
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
2018-12-16 9:40 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1a
P2: 403
P3: fffffda548a1e4e0
P4: 8100000052ca9847
P5: fffffda548a1efe0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121618-5859-01.dmp
\\?\C:\WINDOWS\TEMP\WER-8000-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A7B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A7C.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A9A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AAA.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_56746c1ab2781d46157f32ced776162b6c6ade36_00000000_cab_0df5f8bc

Analysis symbol: 
Rechecking for solution: 0
Report Id: 55485fe9-71e8-487c-8860-3906a5d33dc9
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
2018-12-16 9:30 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1a
P2: 403
P3: fffffda548a1e4e0
P4: 8100000052ca9847
P5: fffffda548a1efe0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121618-5859-01.dmp
\\?\C:\WINDOWS\TEMP\WER-8000-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A7B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A7C.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A9A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AAA.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_56746c1ab2781d46157f32ced776162b6c6ade36_00000000_03302aa9

Analysis symbol: 
Rechecking for solution: 0
Report Id: 55485fe9-71e8-487c-8860-3906a5d33dc9
Report Status: 4
Hashed bucket: 
Cab Guid: 0
2018-12-16 9:21 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff8016e43ed67
P4: 0
P5: ffffffffffffffff
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121618-5984-01.dmp
\\?\C:\WINDOWS\TEMP\WER-9390-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3047.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3048.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3066.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3077.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_8df3af6241e82aa78393f858b1c929dc1daea349_00000000_cab_13b430d4

Analysis symbol: 
Rechecking for solution: 0
Report Id: f3ff9c9a-1ab0-4ca2-a2e5-cac91183c94d
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
2018-12-16 9:21 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff8016e43ed67
P4: 0
P5: ffffffffffffffff
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121618-5984-01.dmp
\\?\C:\WINDOWS\TEMP\WER-9390-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3047.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3048.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3066.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3077.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_8df3af6241e82aa78393f858b1c929dc1daea349_00000000_03303076

Analysis symbol: 
Rechecking for solution: 0
Report Id: f3ff9c9a-1ab0-4ca2-a2e5-cac91183c94d
Report Status: 4
Hashed bucket: 
Cab Guid: 0
2018-12-17 12:01 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff8038c649d67
P4: 0
P5: ffffffffffffffff
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121618-6906-01.dmp
\\?\C:\WINDOWS\TEMP\WER-9671-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3057.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3067.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3076.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3086.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_4a485a8698b4b469d1ff2f48c5f34e437d344f4_00000000_cab_13403ab7

Analysis symbol: 
Rechecking for solution: 0
Report Id: 22c4fccb-a8a9-44dd-956b-e923cdf9e50e
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
2018-12-16 11:56 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff8038c649d67
P4: 0
P5: ffffffffffffffff
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121618-6906-01.dmp
\\?\C:\WINDOWS\TEMP\WER-9671-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3057.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3067.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3076.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3086.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_4a485a8698b4b469d1ff2f48c5f34e437d344f4_00000000_03243085

Analysis symbol: 
Rechecking for solution: 0
Report Id: 22c4fccb-a8a9-44dd-956b-e923cdf9e50e
Report Status: 4
Hashed bucket: 
Cab Guid: 0
2018-12-17 11:50 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 4a
P2: 7ffaf9ac4e04
P3: 1
P4: 0
P5: fffff00916b2cb80
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121718-7031-01.dmp
\\?\C:\WINDOWS\TEMP\WER-12093-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55B1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55D1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55F0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5600.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_4a_ebf10aaba7c5a67e036d36c1fcffc45128f65_00000000_cab_1bb45e7b

Analysis symbol: 
Rechecking for solution: 0
Report Id: c95682e1-9662-4924-9cc9-722fe282f8cb
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
2018-12-17 11:49 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 4a
P2: 7ffaf9ac4e04
P3: 1
P4: 0
P5: fffff00916b2cb80
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121718-7031-01.dmp
\\?\C:\WINDOWS\TEMP\WER-12093-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55B1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55D1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55F0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5600.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_4a_ebf10aaba7c5a67e036d36c1fcffc45128f65_00000000_0338560f

Analysis symbol: 
Rechecking for solution: 0
Report Id: c95682e1-9662-4924-9cc9-722fe282f8cb
Report Status: 4
Hashed bucket: 
Cab Guid: 0
2018-12-17 12:06 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 4a
P2: 7fff8d2aaa64
P3: 2
P4: 0
P5: ffffb98ce9b4fb80
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121618-7515-01.dmp
\\?\C:\WINDOWS\TEMP\WER-9984-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER318F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER31A0.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER31AE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER31BF.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_4a_7df4187a7fe27ad4973daad3c26f8f5cfeb443b2_00000000_cab_13c0320c

Analysis symbol: 
Rechecking for solution: 0
Report Id: 9c6f570e-386e-4cbc-8ead-dfa2df840840
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
2018-12-17 12:06 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 4a
P2: 7fff8d2aaa64
P3: 2
P4: 0
P5: ffffb98ce9b4fb80
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121618-7515-01.dmp
\\?\C:\WINDOWS\TEMP\WER-9984-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER318F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER31A0.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER31AE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER31BF.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_4a_7df4187a7fe27ad4973daad3c26f8f5cfeb443b2_00000000_033431be

Analysis symbol: 
Rechecking for solution: 0
Report Id: 9c6f570e-386e-4cbc-8ead-dfa2df840840
Report Status: 4
Hashed bucket: 
Cab Guid: 0
2018-12-18 12:58 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 4e
P2: 99
P3: 235922
P4: 1
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121718-9796-01.dmp
\\?\C:\WINDOWS\TEMP\WER-19953-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5851.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5862.tmp.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_4e_84ebc5492518ca3c94d1283eb514f84c237af0_00000000_cab_0a9c252b

Analysis symbol: 
Rechecking for solution: 0
Report Id: 899a5ed6-554b-4674-b8ba-8e3794c6d167
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
2018-12-18 12:18 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 50
P2: ffff9b0c0e244c14
P3: 0
P4: fffff803aed059a1
P5: 2
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121718-5953-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10843-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER515C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER518C.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER51AA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER51CA.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_dc79be699c7b1b38e754ce453a2225f4cc59d49_00000000_cab_1d1c55e0

Analysis symbol: 
Rechecking for solution: 0
Report Id: b5b1c6c5-be53-4477-a806-36b5c9d39872
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
2018-12-18 12:18 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 50
P2: ffff9b0c0e244c14
P3: 0
P4: fffff803aed059a1
P5: 2
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121718-5953-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10843-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER515C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER518C.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER51AA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER51CA.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_dc79be699c7b1b38e754ce453a2225f4cc59d49_00000000_033451e8

Analysis symbol: 
Rechecking for solution: 0
Report Id: b5b1c6c5-be53-4477-a806-36b5c9d39872
Report Status: 4
Hashed bucket: 
Cab Guid: 0
2018-12-17 12:01 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: be
P2: ffff9282d30e8488
P3: 8a00000004500121
P4: ffffe1048046eee0
P5: a
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121618-6562-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10000-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3410.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3420.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER342F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3440.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_be_c8d5b73add209c3de48a4552375918dd3355357_00000000_cab_134053cd

Analysis symbol: 
Rechecking for solution: 0
Report Id: 13ab0728-3325-453a-b231-93f9c0b43de0
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
2018-12-17 12:01 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: be
P2: ffff9282d30e8488
P3: 8a00000004500121
P4: ffffe1048046eee0
P5: a
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121618-6562-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10000-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3410.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3420.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER342F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3440.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_be_c8d5b73add209c3de48a4552375918dd3355357_00000000_032c344e

Analysis symbol: 
Rechecking for solution: 0
Report Id: 13ab0728-3325-453a-b231-93f9c0b43de0
Report Status: 4
Hashed bucket: 
Cab Guid: 0
    Code:
    Name	NVIDIA GeForce GTX 1060 6GB
PNP Device ID	PCI\VEN_10DE&DEV_1C03&SUBSYS_371A1458&REV_A1\4&1C3D25BB&0&0019
Adapter Type	GeForce GTX 1060 6GB, NVIDIA compatible
Adapter Description	NVIDIA GeForce GTX 1060 6GB
Adapter RAM	(1,048,576) bytes
Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_01c064f3d89f92be\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_01c064f3d89f92be\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_01c064f3d89f92be\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_01c064f3d89f92be\nvldumdx.dll
Driver Version	25.21.14.1735
INF File	oem45.inf (Section108 section)
Color Planes	Not Available
Color Table Entries	4294967296
Resolution	1920 x 1080 x 60 hertz
Bits/Pixel	32
Memory Address	0xF6000000-0xF6FFFFFF
Memory Address	0xE0000000-0xFEC2FFFF
Memory Address	0xF0000000-0xF1FFFFFF
I/O Port	0x0000F000-0x0000F07F
IRQ Channel	IRQ 54
I/O Port	0x000003B0-0x000003DF
I/O Port	0x000003C0-0x000003DF
Memory Address	0xA0000-0xBFFFF
Driver	c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_01c064f3d89f92be\nvlddmkm.sys (25.21.14.1735, 19.48 MB (20,424,640 bytes), 2018-12-15 11:42 PM)
    Code:
    nvlddmkm.sys Mon Dec 10 22:22:03 2018 (5C0F578B)
    Code:
    nvlddmkm     nvlddmkm               nvlddmkm               Kernel        Manual     Running    OK         TRUE        FALSE        10,133,504        7,815,168   0          2018-12-11 1:22:03 AM  C:\WINDOWS\system32\DriverStore\FileRepository\n 36,864
    Last edited by zbook; 17 Dec 2018 at 23:40.
      My Computer
    Quote Quote

  4. levolpehh
    Posts : 8
    Windows 10
    Thread Starter
       New #3

    Microsoft Windows [Version 10.0.17134.471]
    (c) 2018 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.17134.1

    Image Version: 10.0.17134.471

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...
    702464 file records processed.
    File verification completed.
    39578 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    3532 reparse records processed.
    798846 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    3532 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    48192 data files processed.
    CHKDSK is verifying Usn Journal...
    39070952 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    487822335 KB total disk space.
    136167328 KB in 223952 files.
    142464 KB in 48193 indexes.
    0 KB in bad sectors.
    846291 KB in use by the system.
    65536 KB occupied by the log file.
    350666252 KB available on disk.

    4096 bytes in each allocation unit.
    121955583 total allocation units on disk.
    87666563 allocation units available on disk.

    C:\WINDOWS\system32>

    I'll get started on the rest. Just posting this now in case I crash again lol. Thank you very much for your help btw! It's much appreciated.

    --

    Update: I've gotten up to the graphics drivers part. Is step 8 incorporated into steps 9 to 11?
    Last edited by levolpehh; 17 Dec 2018 at 23:15.
      My Computer
    Quote Quote

  6. zbook
    Posts : 41,480
    windows 10 professional version 1607 build 14393.969 64 bit
       New #4

    1) For Ccleaner:
    a) click cleaner > click Windows tab > Microsoft edge should be displayed on top > scroll down to the near the bottom on the windows tab > post an image of system and advanced

    2) For startup and recovery system failure:
    a) uncheck automatically restart
    b) reboot to maintain settings

    3) With automatically restart checked it can be easy to miss BSOD.
    With automatically restart unchecked you should see a BSOD window with bugcheck and : (
    Sometimes you may see a misbehaving driver in the form *.sys
    At the very beginning of a BSOD you may see a % counter.
    If you see the % counter allow it to rise to 100% before rebooting so that there is sufficient time to create the dump file.


    4) The numbering in the prior post was updated.
    8 was the main step and the others were the details.
    Steps 12 - 15 are together.
      My Computer
    Quote Quote

  7. levolpehh
    Posts : 8
    Windows 10
    Thread Starter
       New #5

    Thank you! I'll work on the rest in the morning and update then. As for the automatic restart, on nearly all of those BSOD it never restarted at 100% anyway. It would just sit on that screen indefinitely until I manually forced a restart. For a few it did... but that was pretty rare. I always waited till it reached 100% just in case.
      My Computer
    Quote Quote

  8. zbook
    Posts : 41,480
    windows 10 professional version 1607 build 14393.969 64 bit
       New #6

    For Ccleaner uncheck:

    a) Memory Dumps
    b) Windows log files

    If there are any BSOD after all of the above steps then:
    a) Run the BETA log colletor and post a new zip into the thread
    b) Open file explorer > this PC > C: > in the right upper corner search for C:\windows\memory.dmp > if the file size is < 1.5 GB then zip > post a share link into the thread using one drive, drop box, or google drive
      My Computer
    Quote Quote

  9. levolpehh
    Posts : 8
    Windows 10
    Thread Starter
       New #7

    Alrighty, I've done everything you've listed. I'll make another response here if the crashing continues or in a few days if it resolves. Thank you very much for your help! :)
      My Computer
    Quote Quote

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

    Nice progress.
    You are very welcome.

    There are sometimes problems with unexpected power outages, problems with Windows updates, malware, ransomware, corrupt operating system or registry, failure to boot, etc.

    Consider making a backup image:
    Macrium Software | Your Image is Everything
    Backup and Restore with Macrium Reflect | Tutorials
      My Computer
    Quote Quote

  12. levolpehh
    Posts : 8
    Windows 10
    Thread Starter
       New #9

    Hello, unfortunately got another BSOD it ran perfectly fine for over 24 hours, so got my hopes up. This time I got the PFN List Corrupt error. I've also attached the log.
      My Computer
    Quote Quote

  13. levolpehh
    Posts : 8
    Windows 10
    Thread Starter
       New #10

    Unable to edit post here apparently. Got another crash, System Service Exception, this time.

    Edit: Aand again. Memory Management again this time.
      My Computer
    Quote Quote

 

  Related Discussions
Hello, I built a new computer over christmas with windows 10 and have been randomly getting BSOD's, I messed around the bios (tried to run it without overclock, with manual voltage tinkering different ones up to 1.5V on an i9-10850k...), ran...
Recently for the past 3-4 days all of my games have been crashing at random times while playing them (Rocket League, Fortnite, R.U.S.E), on top of that after updating all of my drivers I have gotten a couple blue screen of deaths instead of the game...
Hey all, I'm getting frequent DPC Watchdog_Violation BSOD crashes and I just cannot figure out why. A bit of background: I bought an ACER Aspirer TC-280 Desktop in March. It ran okay for about a month then it started acting up. I had a ticking...
I have had no problems what so ever with this computer running Win 7 Pro for a very long time (2+ years) and when I moved to Win 10 Pro I get these BSOD Critical_Process_Died crashes while browsing the internet using Fire Fox. After the BSOD it will...
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 09:43.
Find Us




Windows 10 Forums