Windows 10: BSOD often Mainly playing Minecraft, even after factory reset.

Discus and support BSOD often Mainly playing Minecraft, even after factory reset. in Windows 10 BSOD Crashes and Debugging to solve the problem; The logs indicated that it was 821 MB before zipping. See if you can post it using one drive or drop box. Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Ikanopit, Feb 7, 2018.

  1. zbook New Member

    BSOD often Mainly playing Minecraft, even after factory reset.


    The logs indicated that it was 821 MB before zipping.
    See if you can post it using one drive or drop box.
     
    zbook, Feb 9, 2018
    #16
  2. Ikanopit Win User
    Ikanopit, Feb 9, 2018
    #17
  3. zbook New Member
    zbook, Feb 9, 2018
    #18
  4. Ikanopit Win User

    BSOD often Mainly playing Minecraft, even after factory reset.

    I have done as you suggested and have installed new NVIDIA drivers.
    it was all going ok and then had a series of BSOD.
    Please see attached log files.
     
    Ikanopit, Feb 9, 2018
    #19
  5. zbook New Member
    The bugchecks were 19.
    The BAD_POOL_HEADER bug check has a value of 0x00000019. This indicates that a pool header is corrupt.
    The debugging did not display a definitive driver.

    There is a Windows tool that is used to find misbehaving drivers.
    Windows driver verifier will stimulate drivers so that the misbehaving drivers cause BSOD.
    The BSOD dump files are then debugged to find the misbehaving driver(s).
    The tool repetitively produces BSOD until all of the misbehaving drivers are fixed or until the tool is turned off.

    Before using the tool perform the following steps:
    1) backup all files to another drive or to the cloud
    2) make a backup image using Macrium
    Macrium Software | Your Image is Everything
    3) make a brand new restore point
    4) learn the 3 methods to turn off the tool

    After each BSOD you will turn off the tool and return to the desktop. On the desktop you will then uninstall the misbehaving driver and restart the tool to find the next misbehaving driver. New drivers can be uninstalled as soon as they are uninstalled or they all can be installed at the end once there are no longer any BSOD. The end result should be the same.

    The tool is used for 48 hours. After the last BSOD it is used for an additional 36 hours. While using the tool there can be problems with sluggishness and or boot problems. If these problems are significant the customized tests can be modified.

    All methods that you will use to turn off the tool are in the Windows advanced troubleshooting menu.
    a) startup options (not startup repair) > click restart > select #6 safe mode with command prompt > type:
    verifier /reset
    b) command prompt > Administrator: X:\Windows\System32\cmd.exe > X:\sources> type:
    verifier /bootmode resetonbootfail
    c) system restore
    The methods to turn off Windows driver verifier should be used in the above order and advanced on the menu only if the prior method fails. System restore often leads to a loss of the dump file and little progress is made in the troubleshooting.

    Use the information in this link for the customized test settings:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    Use the information in this link for turning off Windows driver verifier:
    Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

    After each BSOD post a new zip into the thread:
    Windows 10 Help Forums
     
    zbook, Feb 10, 2018
    #20
  6. Ikanopit Win User
    Todays first BSOD attached. For some reason version 2 is not working for me now ?
     
    Ikanopit, Feb 10, 2018
    #21
  7. zbook New Member
    While using windows driver verifier there were additional BSODs.
    Debugging displayed a misbehaving hardware driver.

    Update: netwsw00.sys
    Netwsw00.sys Tue Feb 05 13:00:21 2013 (511156C5)
    Updating a driver: Updating a driver. - Microsoft Community

    Netwsw00.sys Intel® Wireless WiFi Link Adapter Intel® Support


    Code: Name [00000001] Intel(R) Centrino(R) Wireless-N 130 Driver Adapter Type Ethernet 802.3Product Type Intel(R) Centrino(R) Wireless-N 130 DriverInstalled YesPNP Device ID PCI\VEN_8086&DEV_0896&SUBSYS_50058086&REV_34\DCA971FFFF8497F700Last Reset 11/02/2018 07:35Index 1Service Name NETwNs64IP Address 192.168.1.141, fe80::f942:bdfa:41c5:a88bIP Subnet 255.255.255.0, 64Default IP Gateway 192.168.1.1DHCP Enabled YesDHCP Server 192.168.1.1DHCP Lease Expires 03/01/1970 00:00DHCP Lease Obtained 01/01/1970 00:00MAC Address ‪DC:A9:71:84:97:F7‬Memory Address 0xF6200000-0xF6201FFFIRQ Channel IRQ 4294967288Driver c:\windows\system32\drivers\netwsw00.sys (15.4.1.1, 10.99 MB (11,518,976 bytes), 29/09/2017 13:40)[/quote] Code: 11/02/2018 07:30 Windows Error Reporting Fault bucket 0xc4_2000_VRF_Netwsw00!prvMemInitializeLookasideEntry, type 0 Event Name: BlueScreen Response: Not available Cab Id: cb1a22dd-decb-489a-b7bf-821e77b793a6 Problem signature: P1: c4 P2: 2000 P3: fffff80b11342cfb P4: 0 P5: 48746e49 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021118-4609-01.dmp \\?\C:\Windows\TEMP\WER-9500-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3817.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3846.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3856.tmp.txt \\?\C:\Windows\Temp\WER41DC.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_d03279618b50e0f45c1d59e71421b18530b19ef_00000000_cab_0ce918a3 Analysis symbol: Rechecking for solution: 0 Report Id: f4dcdc43-68ce-4572-a216-885035528b6c Report Status: 268435456 Hashed bucket:[/quote]
     
    zbook, Feb 10, 2018
    #22
  8. philc43 Win User

    BSOD often Mainly playing Minecraft, even after factory reset.

    Don't leave Driver Verifier running for more than 48h as originally instructed in my post #6.

    After updating the drivers which were identified make sure Driver Verifier is OFF and run your system for a while to make sure that there are no further BSOD events.
     
    philc43, Feb 11, 2018
    #23
  9. Ikanopit Win User
    I ran it for 48 hours. After updating the NVIDIA drivers it all seemed fine. Then had another BSOD today with something about Hardware fault.
    I have included the zip of the faults.
    Thanks Again
     
    Ikanopit, Feb 12, 2018
    #24
  10. zbook New Member
    The latest BSOD mini dump displayed 12B.
    The FAULTY_HARDWARE_CORRUPTED_PAGE bug check has a value of 0x0000012B. This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.

    There was no definitive misbehaving driver debugging the bugcheck.
    The event logs, Windows error reporting, and Kernel events reported problems related to the Nvidia GPU.

    1) Open file explorer > this PC > C: > in the right upper corner search for: c:\windows\memory.dmp > zip > post link into the thread

    2) For any new BSOD please use this version of the log collector: log collector v2-beta08.zip

    Code: Event[4516]: Log Name: System Source: Display Date: 2018-02-13T04:03:46.030 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-SGMTCI2 Description: Display driver nvlddmkm stopped responding and has successfully recovered.Event[4517]: Log Name: System Source: Display Date: 2018-02-13T04:03:47.037 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-SGMTCI2 Description: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote] Code: 13/02/2018 19:06 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 12b P2: ffffffffc00002c4 P3: dea P4: 303b250 P5: ffff9f80d1175000 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021318-8046-01.dmp \\?\C:\Windows\TEMP\WER-12593-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40D1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40F1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4101.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_12b_5c7c5913948e6ac6fae7b5622f9c2175d2c70_00000000_cab_03144100 Analysis symbol: Rechecking for solution: 0 Report Id: 36543bb1-9540-49f2-8483-4d0bcaf04bbf Report Status: 4 Hashed bucket:[/quote] Code: 13/02/2018 07:46 Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Fermi_DmaCopy0, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 12a1cb81-8b32-4d8f-93ec-4f8185b489b6 Problem signature: P1: 141 P2: ffffdd0360ed64a0 P3: fffff80e4264bd90 P4: 0 P5: 4 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20180213-0403.dmp \\?\C:\Windows\TEMP\WER-28439656-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24FD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24FD.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER251D.tmp.txt \\?\C:\Windows\Temp\WER47D8.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_fba673f5982559e6c61ec8aca176e198c7c7632f_00000000_cab_1f1e4b23 Analysis symbol: Rechecking for solution: 0 Report Id: c0f208c2-6ff4-43aa-82b5-564a6e606e55 Report Status: 268435456 Hashed bucket:[/quote] Code: 13/02/2018 07:46 Windows Error Reporting Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 141 P2: ffffdd0360ed64a0 P3: fffff80e4264bd90 P4: 0 P5: 4 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20180213-0403.dmp \\?\C:\Windows\TEMP\WER-28439656-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24FD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24FD.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER251D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_fba673f5982559e6c61ec8aca176e198c7c7632f_00000000_cab_00c2252c Analysis symbol: Rechecking for solution: 0 Report Id: c0f208c2-6ff4-43aa-82b5-564a6e606e55 Report Status: 4 Hashed bucket:[/quote]
     
    zbook, Feb 12, 2018
    #25
  11. Ikanopit Win User
    Ikanopit, Feb 12, 2018
    #26
  12. zbook New Member
    The BSOD mini and memory dump file debugging displayed misbehaving Nvidia GPU drivers.
    This is a recurrent problem with the Nvidia GPU drivers.
    nvlddmkm.sys Tue Jan 23 16:24:56 2018 (5A67B638)
    23.21.13.9077



    Perform the following steps:
    1) Disable Windows updates of non-Microsoft drivers
    Enable or Disable Driver Updates in Windows Update in Windows 10 | Windows 10 Tutorials
    2) Uninstall Nvidia drivers using DDU
    Display Driver Uninstaller Download version 17.0.8.2https://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html
    3) Re-install Nvidia drivers using the MSI website:
    Support For GT780DX(GT780DXR) | Laptops - The best gaming laptop provider | MSI Global

    Title
    Nvidia GeForce GTX 570M /560M


    Version
    9.18.13.546

    Release Date
    2012-08-23

    File Size
    242.53 MB



    Code: Name NVIDIA GeForce GTX 570MPNP Device ID PCI\VEN_10DE&DEV_1210&SUBSYS_10BD1462&REV_A1\4&1F708751&0&0008 Adapter Type GeForce GTX 570M, NVIDIA compatible Adapter Description NVIDIA GeForce GTX 570M Adapter RAM 1.50 GB (1,610,612,736 bytes) Installed Drivers C:\Windows\System32\DriverStore\FileRepository\nvmii.inf_amd64_d63c476addc6a325\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmii.inf_amd64_d63c476addc6a325\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmii.inf_amd64_d63c476addc6a325\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmii.inf_amd64_d63c476addc6a325\nvldumdx.dll Driver Version 23.21.13.9077 INF File oem2.inf (Section002 section) Color Planes Not Available Color Table Entries 4294967296 Resolution 1920 x 1080 x 60 hertz Bits/Pixel 32 Memory Address 0xF4000000-0xF60FFFFF Memory Address 0xE0000000-0xEBFFFFFF Memory Address 0xE8000000-0xEBFFFFFF I/O Port 0x0000E000-0x0000EFFF IRQ Channel IRQ 16 I/O Port 0x000003B0-0x000003BB I/O Port 0x000003C0-0x000003DF Memory Address 0xA0000-0xBFFFF Driver c:\windows\system32\driverstore\filerepository\nvmii.inf_amd64_d63c476addc6a325\nvlddmkm.sys (23.21.13.9077, 16.68 MB (17,493,824 bytes), 13/02/2018 20:09)[/quote]
    Code: 13/02/2018 19:06 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 12b P2: ffffffffc00002c4 P3: dea P4: 303b250 P5: ffff9f80d1175000 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021318-8046-01.dmp \\?\C:\Windows\TEMP\WER-12593-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40D1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40F1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4101.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_12b_5c7c5913948e6ac6fae7b5622f9c2175d2c70_00000000_cab_03144100 Analysis symbol: Rechecking for solution: 0 Report Id: 36543bb1-9540-49f2-8483-4d0bcaf04bbf Report Status: 4 Hashed bucket:09/02/2018 18:01 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff8017b806370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020918-8625-01.dmp \\?\C:\Windows\TEMP\WER-13312-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A28.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A57.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A67.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_24a451998c395dd67f089757e6fe897166fb7_00000000_cab_02f44a76 Analysis symbol: Rechecking for solution: 0 Report Id: 9d761c53-5bfe-453e-9344-2da738f79888 Report Status: 4 Hashed bucket: 10/02/2018 09:22 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 139 P2: 3 P3: ffffc98d53724e50 P4: ffffc98d53724da8 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021018-9250-01.dmp \\?\C:\Windows\TEMP\WER-13875-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55C1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55F0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5610.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_a4ec483987d6606e30ab4ae2bed5746e1d67b0e5_00000000_cab_0330561e Analysis symbol: Rechecking for solution: 0 Report Id: 8dd0c6cf-27b8-48e3-b60d-e0563a3512c6 Report Status: 4 Hashed bucket: 10/02/2018 18:45 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 19 P2: 20 P3: ffff81077f432ed0 P4: ffff81077f432f00 P5: 5030225 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021018-8578-01.dmp \\?\C:\Windows\TEMP\WER-11968-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4045.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4074.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4084.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_19_dabcbad841973c476738dd45ee8bbdd0ed4829b9_00000000_cab_03084083 Analysis symbol: Rechecking for solution: 0 Report Id: e58d3cdf-6ee1-4ca2-b70a-5fe1769a2d79 Report Status: 4 Hashed bucket: 10/02/2018 18:34 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 19 P2: 20 P3: ffffc084e6304ed0 P4: ffffc084e6304f00 P5: 4030019 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021018-9218-01.dmp \\?\C:\Windows\TEMP\WER-12390-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40D1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40F1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4101.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_19_88c79e56aa9389a6a24dd69813a7e542fc5de_00000000_cab_03104100 Analysis symbol: Rechecking for solution: 0 Report Id: baefbe42-03d0-4813-8134-0739fbc11fb9 Report Status: 4 Hashed bucket: 10/02/2018 19:04 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1a P2: 403 P3: ffffd48003dc0ed0 P4: 800000024365c967 P5: ffffd4df43ea4108 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021018-8609-01.dmp \\?\C:\Windows\TEMP\WER-11093-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3AB7.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3AD6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3AE7.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_21da4c7dd922c427a9fef88fb0ec5ed2648d4fd_00000000_cab_030c3ae6 Analysis symbol: Rechecking for solution: 0 Report Id: b913762b-bafe-451d-91c7-d8b69ba4f548 Report Status: 4 Hashed bucket: 10/02/2018 20:25 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 4e P2: 99 P3: 1f30c6 P4: 2 P5: a0001f0001f30c7 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021018-7390-01.dmp \\?\C:\Windows\TEMP\WER-10953-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B05.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B34.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B44.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_4e_b4d29dc05a26831d9baf36809eeccb0306a2ef7_00000000_cab_02d83b43 Analysis symbol: Rechecking for solution: 0 Report Id: 82fb59c4-abfc-42f0-9251-618c2801cd47 Report Status: 4 Hashed bucket: 09/02/2018 16:53 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: a P2: 0 P3: 2 P4: 0 P5: fffff800450ac273 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020918-7812-01.dmp \\?\C:\Windows\TEMP\WER-13656-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4CE7.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D06.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D27.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_5ec5cab4f3c7f3d0c1da57b53a15b1f1e6d8dd7_00000000_cab_03284d35 Analysis symbol: Rechecking for solution: 0 Report Id: 35f4063a-191e-4519-8613-4c11fb812ffd Report Status: 4 Hashed bucket: 11/02/2018 11:20 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c4 P2: 2000 P3: fffff806b5e02cfb P4: 0 P5: 48746e49 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021118-5140-01.dmp \\?\C:\Windows\TEMP\WER-7359-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E05.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_ba5fcbb89ace6e22278a51eaa7b8bd33cbc9f15_00000000_cab_02a02e05 Analysis symbol: Rechecking for solution: 0 Report Id: 6a384484-989d-41b7-9f87-89214a6badfd Report Status: 4 Hashed bucket: 11/02/2018 07:25 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c4 P2: 2000 P3: fffff80b11342cfb P4: 0 P5: 48746e49 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021118-4609-01.dmp \\?\C:\Windows\TEMP\WER-9500-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3817.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3846.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3856.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_d03279618b50e0f45c1d59e71421b18530b19ef_00000000_cab_02b03855 Analysis symbol: Rechecking for solution: 0 Report Id: f4dcdc43-68ce-4572-a216-885035528b6c Report Status: 4 Hashed bucket: 11/02/2018 11:31 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c4 P2: 2000 P3: fffff80fd4b72cfb P4: 0 P5: 48746e49 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021118-4765-01.dmp \\?\C:\Windows\TEMP\WER-9656-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3894.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38C3.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38D3.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_c223319324538941357788396de97ec7620dce4_00000000_cab_02ac38d2 Analysis symbol: Rechecking for solution: 0 Report Id: fb264a6f-a1ff-49a0-bc49-294d3a9030e7 Report Status: 4 Hashed bucket: 13/02/2018 20:35 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c5 P2: 8 P3: 2 P4: 0 P5: fffff803f26b4892 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021318-8343-01.dmp \\?\C:\Windows\TEMP\WER-13000-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4556.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4584.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45B4.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c5_cd3658dcfb4f124a44237c96fba8883b193_00000000_cab_031845b3 Analysis symbol: Rechecking for solution: 0 Report Id: cf54ee0a-5897-4c02-8a03-bda3029aec70 Report Status: 4 Hashed bucket: 10/02/2018 09:07 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ef P2: ffff9b083be75580 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021018-9828-01.dmp \\?\C:\Windows\TEMP\WER-13890-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B51.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B80.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4BA0.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ef_c57b981de58ab88b5859573bb17a8bc457409b_00000000_cab_03284b9f Analysis symbol: Rechecking for solution: 0 Report Id: f44d215e-01bf-40c0-9496-57ebca3bd707 Report Status: 4 Hashed bucket:[/quote]
    Code: 13/02/2018 19:06 Windows Error Reporting Fault bucket 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError, type 0 Event Name: BlueScreen Response: Not available Cab Id: 330217e6-fac2-4528-ada7-20266b9230a4 Problem signature: P1: 12b P2: ffffffffc00002c4 P3: dea P4: 303b250 P5: ffff9f80d1175000 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021318-8046-01.dmp \\?\C:\Windows\TEMP\WER-12593-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40D1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40F1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4101.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_12b_5c7c5913948e6ac6fae7b5622f9c2175d2c70_00000000_cab_18ac81a3 Analysis symbol: Rechecking for solution: 0 Report Id: 36543bb1-9540-49f2-8483-4d0bcaf04bbf Report Status: 268435456 Hashed bucket:09/02/2018 18:07 Windows Error Reporting Fault bucket 0x133_VRF_ISR_MBfilt64!unknown_function, type 0 Event Name: BlueScreen Response: Not available Cab Id: 0cb5c7f7-b572-4fea-abcb-5ee3b7f40bd4 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff8017b806370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020918-8625-01.dmp \\?\C:\Windows\TEMP\WER-13312-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A28.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A57.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A67.tmp.txt \\?\C:\Windows\Temp\WER88A9.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_24a451998c395dd67f089757e6fe897166fb7_00000000_cab_1321f344 Analysis symbol: Rechecking for solution: 0 Report Id: 9d761c53-5bfe-453e-9344-2da738f79888 Report Status: 268435456 Hashed bucket: 10/02/2018 09:23 Windows Error Reporting Fault bucket 0x139_VRF_3_CORRUPT_LIST_ENTRY_nt!ExAllocatePoolWithTag, type 0 Event Name: BlueScreen Response: Not available Cab Id: 63e25b65-b9be-4c49-b1bb-c21345df4ea9 Problem signature: P1: 139 P2: 3 P3: ffffc98d53724e50 P4: ffffc98d53724da8 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021018-9250-01.dmp \\?\C:\Windows\TEMP\WER-13875-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55C1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55F0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5610.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_a4ec483987d6606e30ab4ae2bed5746e1d67b0e5_00000000_cab_0f38c795 Analysis symbol: Rechecking for solution: 0 Report Id: 8dd0c6cf-27b8-48e3-b60d-e0563a3512c6 Report Status: 268435456 Hashed bucket: 10/02/2018 19:01 Windows Error Reporting Fault bucket 0x19_20_nt!IopDeleteFile, type 0 Event Name: BlueScreen Response: Not available Cab Id: a5a7322d-0298-4f3d-9859-a44d509e3f54 Problem signature: P1: 19 P2: 20 P3: ffff81077f432ed0 P4: ffff81077f432f00 P5: 5030225 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021018-8578-01.dmp \\?\C:\Windows\TEMP\WER-11968-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4045.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4074.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4084.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_19_dabcbad841973c476738dd45ee8bbdd0ed4829b9_00000000_cab_00ff4f30 Analysis symbol: Rechecking for solution: 0 Report Id: e58d3cdf-6ee1-4ca2-b70a-5fe1769a2d79 Report Status: 268435456 Hashed bucket: 10/02/2018 19:01 Windows Error Reporting Fault bucket 0x19_20_nt!ObpFreeObject, type 0 Event Name: BlueScreen Response: Not available Cab Id: 90c54bd4-c190-4ccd-849f-bafe56da4b08 Problem signature: P1: 19 P2: 20 P3: ffffc084e6304ed0 P4: ffffc084e6304f00 P5: 4030019 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021018-9218-01.dmp \\?\C:\Windows\TEMP\WER-12390-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40D1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40F1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4101.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_19_88c79e56aa9389a6a24dd69813a7e542fc5de_00000000_cab_00ff2169 Analysis symbol: Rechecking for solution: 0 Report Id: baefbe42-03d0-4813-8134-0739fbc11fb9 Report Status: 268435456 Hashed bucket: 10/02/2018 19:04 Windows Error Reporting Fault bucket 0x1a_403_nt!MiDeletePteRun, type 0 Event Name: BlueScreen Response: Not available Cab Id: b3f1f687-822a-4cf8-8b10-4dac6cd85cda Problem signature: P1: 1a P2: 403 P3: ffffd48003dc0ed0 P4: 800000024365c967 P5: ffffd4df43ea4108 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021018-8609-01.dmp \\?\C:\Windows\TEMP\WER-11093-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3AB7.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3AD6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3AE7.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_21da4c7dd922c427a9fef88fb0ec5ed2648d4fd_00000000_cab_17686a62 Analysis symbol: Rechecking for solution: 0 Report Id: b913762b-bafe-451d-91c7-d8b69ba4f548 Report Status: 268435456 Hashed bucket: 10/02/2018 20:25 Windows Error Reporting Fault bucket 0x4E_99_nt!MiDeletePteRun, type 0 Event Name: BlueScreen Response: Not available Cab Id: 3ab3f5d5-ab34-45f1-9ea7-da10675de13c Problem signature: P1: 4e P2: 99 P3: 1f30c6 P4: 2 P5: a0001f0001f30c7 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021018-7390-01.dmp \\?\C:\Windows\TEMP\WER-10953-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B05.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B34.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B44.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_4e_b4d29dc05a26831d9baf36809eeccb0306a2ef7_00000000_cab_17406447 Analysis symbol: Rechecking for solution: 0 Report Id: 82fb59c4-abfc-42f0-9251-618c2801cd47 Report Status: 268435456 Hashed bucket: 10/02/2018 20:03 Windows Error Reporting Fault bucket 0xc2_7_NVRM_nvlddmkm!CMemoryAllocator::freeMemoryWithTag, type 0 Event Name: BlueScreen Response: Not available Cab Id: d75a7e33-d08e-48ca-a0e1-70a26de4391d Problem signature: P1: c2 P2: 7 P3: 0 P4: 0 P5: ffffb9885924b3f0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021018-7578-01.dmp \\?\C:\Windows\TEMP\WER-11734-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E41.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E60.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E71.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c2_2d2d5d4d969692799b0fe8285d81863ed4e36d2_00000000_cab_11905bac Analysis symbol: Rechecking for solution: 0 Report Id: 55db24db-51f4-4327-ab72-09735967fe9f Report Status: 268435456 Hashed bucket: 11/02/2018 11:32 Windows Error Reporting Fault bucket 0xc4_2000_VRF_Netwsw00!prvMemInitializeLookasideEntry, type 0 Event Name: BlueScreen Response: Not available Cab Id: 7f24ac3d-130f-41db-bfba-ee6665c98439 Problem signature: P1: c4 P2: 2000 P3: fffff80fd4b72cfb P4: 0 P5: 48746e49 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021118-4765-01.dmp \\?\C:\Windows\TEMP\WER-9656-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3894.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38C3.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38D3.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_c223319324538941357788396de97ec7620dce4_00000000_cab_1130b9ca Analysis symbol: Rechecking for solution: 0 Report Id: fb264a6f-a1ff-49a0-bc49-294d3a9030e7 Report Status: 268435456 Hashed bucket: 11/02/2018 07:30 Windows Error Reporting Fault bucket 0xc4_2000_VRF_Netwsw00!prvMemInitializeLookasideEntry, type 0 Event Name: BlueScreen Response: Not available Cab Id: cb1a22dd-decb-489a-b7bf-821e77b793a6 Problem signature: P1: c4 P2: 2000 P3: fffff80b11342cfb P4: 0 P5: 48746e49 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021118-4609-01.dmp \\?\C:\Windows\TEMP\WER-9500-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3817.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3846.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3856.tmp.txt \\?\C:\Windows\Temp\WER41DC.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_d03279618b50e0f45c1d59e71421b18530b19ef_00000000_cab_0ce918a3 Analysis symbol: Rechecking for solution: 0 Report Id: f4dcdc43-68ce-4572-a216-885035528b6c Report Status: 268435456 Hashed bucket: 11/02/2018 11:32 Windows Error Reporting Fault bucket 0xc4_2000_VRF_Netwsw00!prvMemInitializeLookasideEntry, type 0 Event Name: BlueScreen Response: Not available Cab Id: f91a0c90-7954-48dd-8a6d-ea167ec94cf8 Problem signature: P1: c4 P2: 2000 P3: fffff806b5e02cfb P4: 0 P5: 48746e49 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021118-5140-01.dmp \\?\C:\Windows\TEMP\WER-7359-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E05.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_ba5fcbb89ace6e22278a51eaa7b8bd33cbc9f15_00000000_cab_113091df Analysis symbol: Rechecking for solution: 0 Report Id: 6a384484-989d-41b7-9f87-89214a6badfd Report Status: 268435456 Hashed bucket: 13/02/2018 20:36 Windows Error Reporting Fault bucket 0xC5_2_netio!NetioDereferenceNetBufferListChain, type 0 Event Name: BlueScreen Response: Not available Cab Id: 29fc0108-8829-4c30-9984-32d245c5a461 Problem signature: P1: c5 P2: 8 P3: 2 P4: 0 P5: fffff803f26b4892 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021318-8343-01.dmp \\?\C:\Windows\TEMP\WER-13000-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4556.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4584.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45B4.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c5_cd3658dcfb4f124a44237c96fba8883b193_00000000_cab_1ec07c92 Analysis symbol: Rechecking for solution: 0 Report Id: cf54ee0a-5897-4c02-8a03-bda3029aec70 Report Status: 268435456 Hashed bucket: 10/02/2018 09:22 Windows Error Reporting Fault bucket 0xEF_svchost.exe_VRF_BUGCHECK_CRITICAL_PROCESS_c0000005_mpssvc.dll!FwPlumberDeleteFilters_IMAGE_mpssvc.dll, type 0 Event Name: BlueScreen Response: Not available Cab Id: bb9d1840-ce40-4735-a410-bb6b65504a4e Problem signature: P1: ef P2: ffff9b083be75580 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021018-9828-01.dmp \\?\C:\Windows\TEMP\WER-13890-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B51.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B80.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4BA0.tmp.txt \\?\C:\Windows\Temp\WER4E30.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_c57b981de58ab88b5859573bb17a8bc457409b_00000000_cab_0f385b8d Analysis symbol: Rechecking for solution: 0 Report Id: f44d215e-01bf-40c0-9496-57ebca3bd707 Report Status: 268435456 Hashed bucket:[/quote]
     
    zbook, Feb 13, 2018
    #27
  13. Ikanopit Win User

    BSOD often Mainly playing Minecraft, even after factory reset.

    Hi there sorry for the long delay i have not been in the best of health.
    I have installed the Nvidia drivers as explained above but before and after i had many BSOD for some reason.
    Please find another Zip file with the crash dump files.
    ThanksDESKTOP-SGMTCI2 (2018-03-15 00 33).zip
     
    Ikanopit, Mar 14, 2018
    #28
  14. zbook New Member
    Open files explorer > this PC > C: > in the right upper corner search for: C:\windows\memory.dmp > zip > post a one drive or drop box share link into the thread.
    The file size is approximately 700 MB
     
    zbook, Mar 14, 2018
    #29
  15. Ikanopit Win User
    Ikanopit, Mar 14, 2018
    #30
Thema:

BSOD often Mainly playing Minecraft, even after factory reset.

Loading...
  1. BSOD often Mainly playing Minecraft, even after factory reset. - Similar Threads - BSOD often Mainly

  2. Bsod after factory reset

    in Windows 10 Gaming
    Bsod after factory reset: Hello. I have a laptop. I wanted to sell it so I just did the factory reset and sold it. After the customer took it during the reset process he called me the next day and came back with a bsod. I tried repairing the disks, didn't work. I tried reinstalling windows, but it...
  3. Bsod after factory reset

    in Windows 10 Software and Apps
    Bsod after factory reset: Hello. I have a laptop. I wanted to sell it so I just did the factory reset and sold it. After the customer took it during the reset process he called me the next day and came back with a bsod. I tried repairing the disks, didn't work. I tried reinstalling windows, but it...
  4. Bsod after factory reset

    in Windows 10 Installation and Upgrade
    Bsod after factory reset: Hello. I have a laptop. I wanted to sell it so I just did the factory reset and sold it. After the customer took it during the reset process he called me the next day and came back with a bsod. I tried repairing the disks, didn't work. I tried reinstalling windows, but it...
  5. SYSTEM_SERVICE_EXCEPTION Even After Factory Reset

    in Windows 10 Gaming
    SYSTEM_SERVICE_EXCEPTION Even After Factory Reset: Ever since getting this laptop, I have had a variety BSODs occur at random times ranging from at least once a week to dozens of times a day. Lately, they have all been "System Service Exceptions," but they have previously been a number of stop codes that all seem to point to...
  6. SYSTEM_SERVICE_EXCEPTION Even After Factory Reset

    in Windows 10 Software and Apps
    SYSTEM_SERVICE_EXCEPTION Even After Factory Reset: Ever since getting this laptop, I have had a variety BSODs occur at random times ranging from at least once a week to dozens of times a day. Lately, they have all been "System Service Exceptions," but they have previously been a number of stop codes that all seem to point to...
  7. BSODs after CMOS reset and factory reset

    in Windows 10 Gaming
    BSODs after CMOS reset and factory reset: In May this year I bought a second hand custombuilt pc, and after a few months it started getting BSODs pretty often. I tried tweaking some bios settings, most of the time lowering the dram frequency would fix it for a couple of days but the same problem would come back soon...
  8. Frequent BSODs due to ntoskrnl.exe even after doing a factory reset

    in Windows 10 BSOD Crashes and Debugging
    Frequent BSODs due to ntoskrnl.exe even after doing a factory reset: I am facing frequent BSODs. Looking at the Minidumps I was able to figure out that the issue is due to the ntoskrnl.exe driver. But I couldnt figure out exactly which driver was causing this issue. Extended Memory scan that wenton for 2 days didnt show any errors. After...
  9. No sound with headphones even after Factory resetting

    in Windows 10 Ask Insider
    No sound with headphones even after Factory resetting: So about a while ago I pulled my headphones too hard and a little piece got stock in there but I just took it out. And that was that. A couple weeks later my sound wasn't working with my headphones. The speakers and Bluetooth earbuds were fine. I couldn't figure out what to...
  10. Disk at 100% even after a factory reset

    in Windows 10 BSOD Crashes and Debugging
    Disk at 100% even after a factory reset: So i fully reset my laptop which has windows 10 updated version. Even after resetting it ,the disk is at 100% and there are around 89 background process running which i have no clue about. Hope i could get a solution...