Windows 10: BSOD playing the new South Park, error 0x000000c4

Discus and support BSOD playing the new South Park, error 0x000000c4 in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello! I played the new South Park game today and got a bluescreen without any dumpfile, so I decided to run driver verifier properly and a bluescreen... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by edeka3, Oct 17, 2017.

  1. edeka3 Win User

    BSOD playing the new South Park, error 0x000000c4


    Hello! I played the new South Park game today and got a bluescreen without any dumpfile, so I decided to run driver verifier properly and a bluescreen came up (I did hour long testing with driver verifier 2 months ago without crashes). Bluescreenview and Whocrashed relate it to netfilter2.sys, but I don't know what that is and how to solve it.

    I attached the dump zip.

    Would be nice if someone could shed some light on this. I am pretty sure it is not hardware related.


    DESKTOP-MUO4FA8-18_10_2017_194252,99.zip

    :)
     
    edeka3, Oct 17, 2017
    #1

  2. Synaptics TouchPad Delay [Windows 10]

    Thanks a lot, this fixed the issue. Nice South Park reference!
     
    JulioGamiz, Oct 17, 2017
    #2
  3. Random BSODs need help

    update: since last night I've had several BSODs. I would appreciate any help on solving this. Thank you

    The bugchecks:

    0x00000050

    0x0000001a

    0x000000c4

    0x00000019

    0x0000003b
     
    REDNECKPOET-92FBA9C7-B716-4213-A516-5AA32DFCAA2F, Oct 17, 2017
    #3
  4. zbook New Member

    BSOD playing the new South Park, error 0x000000c4

    zbook, Oct 17, 2017
    #4
  5. edeka3 Win User
    edeka3, Oct 17, 2017
    #5
  6. zbook New Member
    There were multiple problems reported in the logs.
    These included: hardware errors, paging files, drivers failing to load, multiple BSOD, problem device, failure to respond, etc.

    Please update the computer specs in the "My Computer" section:
    How To Fill Out Your System Specs
    System Specs - Fill in at Ten Forums:
    System Specs - Fill in at Ten Forums General Tips Tutorials
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums

    Please include: PSU, cooler, case, and peripherals (mouse, keyboard, printer, headset, xbox, etc.) and anything attached to the computer by wired or wireless.

    Uninstall Avast during the troubleshooting.
    Turn on Windows defender.
    Avast Uninstall Utility | Download aswClear for Avast Removal


    Open administrative command prompt and type or copy and paste:
    1) sfc /scannow
    2) dism /online /cleanup-image /restorehealth
    3) 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

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

    5) Sometimes there are problems in the bios that produce bsod.

    6) To ensure that there are no improper bios settings please reset the bios.

    7) Sometimes there can be failure to boot after resetting the bios.

    8) So please make sure your files are backed up.

    9) Please make a backup image with Macrium:

    Macrium Software | Macrium Reflect Free:
    Macrium Software | Your Image is Everything
    Macrium Software | Macrium Reflect Free

    10) And please create a brand new restore point.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computers CMOS to Reset BIOS Settings

    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow

    11) Run memtest86+ version 5.01 for at least 8 passes. Memtest86+ - Advanced Memory Diagnostic Tool
    This may take hours so plan to run it overnight.
    Please make sure you use the Memtest86+ version 5.01 with the link below.
    Memtest86+ - Advanced Memory Diagnostic Tool
    The testing is done not by time but by passes.
    The more passes the better.
    There are a significant number of false negatives if fewer than 8 passes are made.
    A false negative is a pass when there is malfunctioning RAM.
    There is 16 GB of RAM on the computer.
    Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
    Just 1 error is a fail and you can abort testing.
    Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
    Again the more passes the better.
    If both RAM pass when tested 1 at a time after failing when tested together test the next DIMM with 1 RAM module for 8 or more passes. This will help to differentiate malfunctioning RAM from malfunctioning DIMM /Motherboard.
    Memtest86+ - Advanced Memory Diagnostic Tool
    Memtest86+ - Advanced Memory Diagnostic Tool
    Microsoft Community
    Memory problems. - Microsoft Community
    When Memtest86_ version 5.01 has completed 8 or more passes please use a camera or smart phone camera to take a picture and post images into the thread.

    12) Run HDTune on all drives:
    http://www.hdtune.com/to check the health,
    scan for errors, no quick scan but full scan
    run a benchmark.


    It may take some time, but please take the time you need to perform it properly.
    When above is done please make screenshots of the following
    the health,
    the error scan,
    the benchmark incl. following
    transfer rate,
    access time,
    burst rate,
    cpu usage.
    Take Screenshot in Windows 10 General Tips Tutorials




    Code: Event[77]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-06-09T18:55:04.737 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT-AUTORITÄT\SYSTEM Computer: DESKTOP-MUO4FA8 Description: Windows failed fast startup with error status 0xC00000D4.[/quote] Code: Event[525]: Log Name: System Source: Service Control Manager Date: 2017-06-09T19:50:44.322 Event ID: 7000 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-MUO4FA8 Description: The NAL service failed to start due to the following error: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.[/quote] Code: Event[33435]: Log Name: System Source: Microsoft-Windows-Kernel-PnP Date: 2017-10-18T20:59:49.115 Event ID: 219 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT-AUTORITÄT\SYSTEM Computer: DESKTOP-MUO4FA8 Description: The driver \Driver\SIUSBXP failed to load for the device USB\VID_1B1C&PID_0C0A\7289_2.0.[/quote] Code: Event[33102]: Log Name: System Source: Service Control Manager Date: 2017-10-18T20:59:09.370 Event ID: 7001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-MUO4FA8 Description: The mrxsmb service depends on the rdbss service which failed to start because of the following error: A device attached to the system is not functioning.[/quote] Code: Corsair USBXp Driver USB\VID_1B1C&PID_0C0A\7289_2.0 52[/quote] Code: Event[30833]: Log Name: System Source: Microsoft-Windows-StartupRepair Date: 2017-10-18T19:27:37.871 Event ID: 1124 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT-AUTORITÄT\SYSTEM Computer: DESKTOP-MUO4FA8 Description: A recent driver installation or upgrade might have prevented Windows from starting.[/quote] Code: Event[5775]: Log Name: System Source: Display Date: 2017-06-19T15:08:20.525 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-MUO4FA8 Description: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote] Code: Event[24748]: Log Name: System Source: Display Date: 2017-09-24T13:24:00.543 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-MUO4FA8 Description: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote] Code: Event[3735]: Log Name: System Source: Disk Date: 2017-06-16T15:08:57.019 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-MUO4FA8 Description: An error was detected on device \Device\Harddisk5\DR11 during a paging operation.[/quote] Code: Event[2259]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2017-06-11T22:23:00.802 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT-AUTORITÄT\Lokaler Dienst Computer: DESKTOP-MUO4FA8 Description: A corrected hardware error has occurred.Reported by component: Processor CoreError Source: Corrected Machine CheckError Type: Cache Hierarchy ErrorProcessor APIC ID: 2The details view of this entry contains further information.[/quote] Code: Event[8898]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2017-07-05T21:42:00.962 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT-AUTORITÄT\Lokaler Dienst Computer: DESKTOP-MUO4FA8 Description: A corrected hardware error has occurred.Reported by component: Processor CoreError Source: Corrected Machine CheckError Type: Cache Hierarchy ErrorProcessor APIC ID: 2The details view of this entry contains further information.Event[8899]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2017-07-05T22:58:47.065 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT-AUTORITÄT\Lokaler Dienst Computer: DESKTOP-MUO4FA8 Description: A corrected hardware error has occurred.Reported by component: Processor CoreError Source: Corrected Machine CheckError Type: Cache Hierarchy ErrorProcessor APIC ID: 4The details view of this entry contains further information.[/quote] Code: Event[9765]: Log Name: System Source: Service Control Manager Date: 2017-07-06T11:08:02.404 Event ID: 7026 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-MUO4FA8 Description: The following boot-start or system-start driver(s) did not load: AFDAsIOaswbidsdriveraswbidshaswblogaswbunivaswNetSecaswRdraswRvrtaswSnxaswSPaswVmmcdromCSCdamDfscFileCryptGpuEnergyDrvHWiNFO32NetBIOSNetBTnsiproxyPschedrdbsstdxvwififlt[/quote] Code: Event[33109]: Log Name: System Source: Service Control Manager Date: 2017-10-18T20:59:09.448 Event ID: 7026 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-MUO4FA8 Description: The following boot-start or system-start driver(s) did not load: AFDAsIOAsUpIOcdromCSCdamDfscFileCryptGpuEnergyDrvHWiNFO32NetBIOSNetBTnsiproxyPschedrdbsstdxvwififltWdFilter[/quote] AsIO.sys Asus PCProbe Utility Official Support | ASUS Global
    AsUpIO.sys ASUS hardware monitoring software related http://support.asus.com/download/dow...Language=en-us

    HWiNFO64A.SYS HWiNFO32 Kernel Driver HWiNFO - Hardware Information, Analysis and Monitoring Tools
    aswbidsdrivera.sys http://www.freefixer.com/library/fil...s-260204/AVAST Home | Official Avast Support
    aswnet.sys AVAST Firewall Core Driver http://support.avast.com/
    aswRdr.SYS avast! TDI RDR Driver http://support.avast.com/
    aswRvrt.sys Avast! Revert driver
    (Likely a boot driver) http://support.avast.com/
    aswSnx.SYS avast! Virtualization Driver http://support.avast.com/
    aswSP.SYS avast! Self Protection Driver http://support.avast.com/
    aswVmm.sys avast! VM Monitor driver http://support.avast.com/
    netfilter2.sys NetFilter SDK TDI Hook Driver Download - Download NetFilter SDK components

    Support - Contact NetFilter SDK
    Code: 20/07/2017 09:41 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: 133 P2: 0 P3: 501 P4: 500 P5: fffff803407e9348 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\072017-6265-01.dmp \\?\C:\Windows\Temp\WER-6718-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22CA.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22F9.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22FA.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_4a45944f360683c60ccbf581744af247bf1f39_00000000_cab_031022f9 Analysis symbol: Rechecking for solution: 0 Report ID: 5e4bcb61-f2c4-46c3-a3ff-4eb9eb7abd4c Report Status: 4 Hashed bucket:19/06/2017 09:54 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff80121a9e847 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\061917-5484-01.dmp \\?\C:\Windows\Temp\WER-6140-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F5F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F6E.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F7F.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_cc47ff103adc1feba810f2eb71322c4b8dabf8_00000000_cab_03341f7e Analysis symbol: Rechecking for solution: 0 Report ID: 019b3ce3-ff09-4266-81b3-a5a3dcd07ca1 Report Status: 4 Hashed bucket:14/06/2017 21:15 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff8015fdfb0b4 P4: 0 P5: ffffffffffffffff P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\061417-6406-01.dmp \\?\C:\Windows\Temp\WER-7234-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26D1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26F0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26F1.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_84293575ebe3413ad0f19279ba175ace16a01a_00000000_cab_032426f0 Analysis symbol: Rechecking for solution: 0 Report ID: ddf2f959-f2ff-41b8-83e7-389388d152e5 Report Status: 100 Hashed bucket:14/06/2017 21:12 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff8015fdfb0b4 P4: 0 P5: ffffffffffffffff P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\061417-6406-01.dmp \\?\C:\Windows\Temp\WER-7234-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26D1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26F0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26F1.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_84293575ebe3413ad0f19279ba175ace16a01a_00000000_cab_032426f0 Analysis symbol: Rechecking for solution: 0 Report ID: ddf2f959-f2ff-41b8-83e7-389388d152e5 Report Status: 100 Hashed bucket:14/06/2017 21:12 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff8015fdfb0b4 P4: 0 P5: ffffffffffffffff P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\061417-6406-01.dmp \\?\C:\Windows\Temp\WER-7234-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26D1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26F0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26F1.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_84293575ebe3413ad0f19279ba175ace16a01a_00000000_cab_032426f0 Analysis symbol: Rechecking for solution: 0 Report ID: ddf2f959-f2ff-41b8-83e7-389388d152e5 Report Status: 4 Hashed bucket:19/06/2017 16:53 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: 7f P2: 8 P3: ffffbc0020459bf0 P4: 25f57868 P5: fffff803812a8717 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\061917-5250-01.dmp \\?\C:\Windows\Temp\WER-6765-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER200B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER201A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER202B.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_7f_f3f6a2a60557a3b8e845049b6cd28ef96af792_00000000_cab_0334202a Analysis symbol: Rechecking for solution: 0 Report ID: b42675eb-2d1e-426e-b4ad-c05b7f06ba84 Report Status: 4 Hashed bucket:18/10/2017 17:07 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: c4 P2: 2000 P3: fffff801ae7e6978 P4: 0 P5: 51544c46 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\101817-3375-01.dmp \\?\C:\Windows\Temp\WER-5093-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BB5.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_9d49b350442eefff4f115c838be64c4d1d96e12b_00000000_cab_02941bc5 Analysis symbol: Rechecking for solution: 0 Report ID: ed065869-bebc-4805-b4ff-92e2f50a4e6e Report Status: 4 Hashed bucket:05/07/2017 18:27 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: c4 P2: 2000 P3: fffff801e7e631b7 P4: 0 P5: 44505342 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\070517-3312-01.dmp \\?\C:\Windows\Temp\WER-3671-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1349.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_2f454a67fc7361de55881b76fdd1ee7e359c7b_00000000_cab_02e41349 Analysis symbol: Rechecking for solution: 0 Report ID: 865dd62c-27c2-4368-941a-77efff7f0799 Report Status: 4 Hashed bucket:05/07/2017 17:51 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: c4 P2: 2000 P3: fffff8088f1a38c4 P4: 0 P5: 53694558 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\070517-3234-01.dmp \\?\C:\Windows\Temp\WER-3625-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1349.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_78ca6d93d9d93b8ee6586dd4988fb235cbc18c7_00000000_cab_02e81359 Analysis symbol: Rechecking for solution: 0 Report ID: 922a95ba-d314-42c3-9ff9-8020c95375b6 Report Status: 4 Hashed bucket:18/10/2017 17:26 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: c4 P2: 2000 P3: fffff80b8e546978 P4: 0 P5: 51544c46 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\101817-3375-01.dmp \\?\C:\Windows\Temp\WER-5109-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BC5.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_8099af956eaa27d1f13753d2559b3af818b26f_00000000_cab_02941bc5 Analysis symbol: Rechecking for solution: 0 Report ID: 48ef663e-2971-40be-b223-e85bedea7cb0 Report Status: 4 Hashed bucket:18/10/2017 17:49 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: c4 P2: 2004 P3: ffff858750944378 P4: fffff807947301f0 P5: ffffe682015ef028 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\101817-3375-01.dmp \\?\C:\Windows\Temp\WER-5250-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C42.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_4e2a16651cb794d77e4c817b8e0d8a0bdb33ce4_00000000_cab_02941c42 Analysis symbol: Rechecking for solution: 0 Report ID: 8261a7bd-f11e-4703-b0ba-8c22e7f7b325 Report Status: 4 Hashed bucket:05/07/2017 17:31 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: c4 P2: 2004 P3: ffffe08434748d48 P4: fffff803758201f0 P5: ffffd080dc607028 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\070517-2968-01.dmp \\?\C:\Windows\Temp\WER-3312-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1211.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_8ac061287e8ada8c697be9deefede142bdedad3_00000000_cab_02ec1220 Analysis symbol: Rechecking for solution: 0 Report ID: 5f5d5237-e61b-4fda-b27a-fc783716d5d1 Report Status: 4 Hashed bucket:16/06/2017 22:24 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: c4 P2: 2006 P3: ffff898de6d133e8 P4: fffff8074b7c01b0 P5: ffffbe01b2deb638 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\061717-3078-01.dmp \\?\C:\Windows\Temp\WER-3359-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER128E.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_5fa8ac8bf97a941204fd86f8f94b21cf2a4ab_00000000_cab_02f0129d Analysis symbol: Rechecking for solution: 0 Report ID: 9414fc73-9566-4e37-a59f-5cf9bbc1a856 Report Status: 4 Hashed bucket:05/07/2017 16:19 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: fc P2: fffff100003df500 P3: 8a0000046ea009e3 P4: ffffca818877ec80 P5: 3 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\070517-17046-01.dmp \\?\C:\Windows\Temp\WER-17937-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D26.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D35.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D36.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_fc_81c75dc2a9866b45f84d2ca455533935acebb0_00000000_cab_03444d45 Analysis symbol: Rechecking for solution: 0 Report ID: 1cef08d2-205a-48a2-aa6c-6dce280fb0a4 Report Status: 4 Hashed bucket:[/quote] Code: 19/06/2017 09:55 Windows Error Reporting Fault bucket 0x1E_c0000005_R_nt!KiExceptionDispatch, type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 9521d544-d2a0-4a3c-99d6-687a49a973ae Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff80121a9e847 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\061917-5484-01.dmp \\?\C:\Windows\Temp\WER-6140-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F5F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F6E.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F7F.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_cc47ff103adc1feba810f2eb71322c4b8dabf8_00000000_cab_15606fff Analysis symbol: Rechecking for solution: 0 Report ID: 019b3ce3-ff09-4266-81b3-a5a3dcd07ca1 Report Status: 268435456 Hashed bucket:14/06/2017 21:38 Windows Error Reporting Fault bucket 0x1E_c0000005_R_nt!RtlpWalkFrameChain, type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: f0026ef1-7393-4f18-a1d6-4f43b1f84d8e Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff8015fdfb0b4 P4: 0 P5: ffffffffffffffff P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\061417-6406-01.dmp \\?\C:\Windows\Temp\WER-7234-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26D1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26F0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26F1.tmp.txt \\?\C:\Windows\Temp\WER1985.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_84293575ebe3413ad0f19279ba175ace16a01a_00000000_cab_0f45f9f1 Analysis symbol: Rechecking for solution: 0 Report ID: ddf2f959-f2ff-41b8-83e7-389388d152e5 Report Status: 268435556 Hashed bucket:19/06/2017 16:54 Windows Error Reporting Fault bucket 0x7f_8_STACKPTR_ERROR, type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 69b579d0-9179-4a16-bd23-96d689cd39b5 Problem signature: P1: 7f P2: 8 P3: ffffbc0020459bf0 P4: 25f57868 P5: fffff803812a8717 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\061917-5250-01.dmp \\?\C:\Windows\Temp\WER-6765-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER200B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER201A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER202B.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_7f_f3f6a2a60557a3b8e845049b6cd28ef96af792_00000000_cab_14b87d8c Analysis symbol: Rechecking for solution: 0 Report ID: b42675eb-2d1e-426e-b4ad-c05b7f06ba84 Report Status: 268435456 Hashed bucket:05/07/2017 19:04 Windows Error Reporting Fault bucket 0xc4_2000_VRF_iocbios2!unknown_function, type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: f014f9ea-0cdc-4dca-83ea-dd559bbf9f6d Problem signature: P1: c4 P2: 2000 P3: fffff801e7e631b7 P4: 0 P5: 44505342 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\070517-3312-01.dmp \\?\C:\Windows\Temp\WER-3671-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1349.tmp.WERInternalMetadata.xml \\?\C:\Windows\Temp\WER3441.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_2f454a67fc7361de55881b76fdd1ee7e359c7b_00000000_cab_1aa6a710 Analysis symbol: Rechecking for solution: 0 Report ID: 865dd62c-27c2-4368-941a-77efff7f0799 Report Status: 268435456 Hashed bucket:18/10/2017 17:27 Windows Error Reporting Fault bucket 0xc4_2000_VRF_netfilter2!unknown_function, type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 5cbf2e8c-7f44-46f7-8e3b-f7bfc3002f53 Problem signature: P1: c4 P2: 2000 P3: fffff80b8e546978 P4: 0 P5: 51544c46 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\101817-3375-01.dmp \\?\C:\Windows\Temp\WER-5109-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BC5.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_8099af956eaa27d1f13753d2559b3af818b26f_00000000_cab_1714350a Analysis symbol: Rechecking for solution: 0 Report ID: 48ef663e-2971-40be-b223-e85bedea7cb0 Report Status: 268435456 Hashed bucket:18/10/2017 17:12 Windows Error Reporting Fault bucket 0xc4_2000_VRF_netfilter2!unknown_function, type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: a1bae460-d9ce-4a2d-b84a-1ac4eb368db1 Problem signature: P1: c4 P2: 2000 P3: fffff801ae7e6978 P4: 0 P5: 51544c46 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\101817-3375-01.dmp \\?\C:\Windows\Temp\WER-5093-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BB5.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_9d49b350442eefff4f115c838be64c4d1d96e12b_00000000_cab_05dafa35 Analysis symbol: Rechecking for solution: 0 Report ID: ed065869-bebc-4805-b4ff-92e2f50a4e6e Report Status: 268435456 Hashed bucket:05/07/2017 17:59 Windows Error Reporting Fault bucket 0xc4_2000_VRF_SiUSBXp!unknown_function, type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: a9ead390-5ff6-4f98-9e72-e02fd853d62c Problem signature: P1: c4 P2: 2000 P3: fffff8088f1a38c4 P4: 0 P5: 53694558 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\070517-3234-01.dmp \\?\C:\Windows\Temp\WER-3625-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1349.tmp.WERInternalMetadata.xml \\?\C:\Windows\Temp\WER1CE2.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_78ca6d93d9d93b8ee6586dd4988fb235cbc18c7_00000000_cab_2f99e612 Analysis symbol: Rechecking for solution: 0 Report ID: 922a95ba-d314-42c3-9ff9-8020c95375b6 Report Status: 268435456 Hashed bucket:18/10/2017 17:53 Windows Error Reporting Fault bucket 0xc4_2004_VRF_nt!MmLoadSystemImageEx, type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 28e9b020-ce82-481a-866b-aed696622a0b Problem signature: P1: c4 P2: 2004 P3: ffff858750944378 P4: fffff807947301f0 P5: ffffe682015ef028 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\101817-3375-01.dmp \\?\C:\Windows\Temp\WER-5250-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C42.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_4e2a16651cb794d77e4c817b8e0d8a0bdb33ce4_00000000_cab_33370783 Analysis symbol: Rechecking for solution: 0 Report ID: 8261a7bd-f11e-4703-b0ba-8c22e7f7b325 Report Status: 268435456 Hashed bucket:05/07/2017 17:38 Windows Error Reporting Fault bucket 0xc4_2004_VRF_nt!MmLoadSystemImageEx, type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: 5b8cee93-4fdb-4322-ae37-7aed1436538e Problem signature: P1: c4 P2: 2004 P3: ffffe08434748d48 P4: fffff803758201f0 P5: ffffd080dc607028 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\070517-2968-01.dmp \\?\C:\Windows\Temp\WER-3312-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1211.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_8ac061287e8ada8c697be9deefede142bdedad3_00000000_cab_290728e6 Analysis symbol: Rechecking for solution: 0 Report ID: 5f5d5237-e61b-4fda-b27a-fc783716d5d1 Report Status: 268435456 Hashed bucket:16/06/2017 22:31 Windows Error Reporting Fault bucket 0xc4_2006_VRF_nt!MmLoadSystemImageEx, type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: bdd689e7-3b10-4c3d-954e-60c1063fadbd Problem signature: P1: c4 P2: 2006 P3: ffff898de6d133e8 P4: fffff8074b7c01b0 P5: ffffbe01b2deb638 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\061717-3078-01.dmp \\?\C:\Windows\Temp\WER-3359-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER128E.tmp.WERInternalMetadata.xml \\?\C:\Windows\Temp\WER285B.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_5fa8ac8bf97a941204fd86f8f94b21cf2a4ab_00000000_cab_0b2caeca Analysis symbol: Rechecking for solution: 0 Report ID: 9414fc73-9566-4e37-a59f-5cf9bbc1a856 Report Status: 268435456 Hashed bucket:05/07/2017 16:19 Windows Error Reporting Fault bucket 0xFC_aswStm!unknown_function, type 0 Event Name: BlueScreen Response: Nicht verfügbar Cab Id: edcbe23a-c0b5-43fd-ba3f-a8849f73097c Problem signature: P1: fc P2: fffff100003df500 P3: 8a0000046ea009e3 P4: ffffca818877ec80 P5: 3 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\070517-17046-01.dmp \\?\C:\Windows\Temp\WER-17937-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D26.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D35.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D36.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_fc_81c75dc2a9866b45f84d2ca455533935acebb0_00000000_cab_14308be4 Analysis symbol: Rechecking for solution: 0 Report ID: 1cef08d2-205a-48a2-aa6c-6dce280fb0a4 Report Status: 268435456 Hashed bucket:[/quote] Code: 19/06/2017 13:09 Windows Error Reporting Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:11_IMAGE_nvlddmkm.sys_Pascal, type 0 Event Name: LiveKernelEvent Response: Nicht verfügbar Cab Id: 4a9c8179-dffe-49be-a6a1-4234e6a6e6b8 Problem signature: P1: 117 P2: ffffbd039395d4a0 P3: fffff80d3cdffd08 P4: 0 P5: 414 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20170619-1507.dmp \\?\C:\Windows\Temp\WER-350265-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C35.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C37.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C38.tmp.txt \\?\C:\Windows\Temp\WER42D9.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_23f4a3f5713d3a647ff46635c9f811ede911599_00000000_cab_20ce46c0 Analysis symbol: Rechecking for solution: 0 Report ID: c2cbc774-077a-466a-8165-efe8059e04bd Report Status: 268435456 Hashed bucket:31/07/2017 14:33 Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0 Event Name: LiveKernelEvent Response: Nicht verfügbar Cab Id: 06bb6a4b-8f2b-4af0-a644-f6ad23630e8f Problem signature: P1: 141 P2: ffff94050e6144a0 P3: fffff800a24cc908 P4: 0 P5: 2f74 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20170721-1315.dmp \\?\C:\Windows\Temp\WER-824640-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B7A.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B7E.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B8F.tmp.txt \\?\C:\Windows\Temp\WER95E1.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_ab465b8d789c2b4e025bb7e073fb56201dfb98_00000000_cab_20f49a83 Analysis symbol: Rechecking for solution: 0 Report ID: dead3576-dd6d-4fda-aa97-67749c46edec Report Status: 268435456 Hashed bucket:24/09/2017 11:24 Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0 Event Name: LiveKernelEvent Response: Nicht verfügbar Cab Id: 73b82939-d6c2-4f83-a41f-a4e131fb026a Problem signature: P1: 141 P2: ffffb200e58b94a0 P3: fffff8081f63ed6c P4: 0 P5: 34b8 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20170924-1323.dmp \\?\C:\Windows\Temp\WER-4777093-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERED8E.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERED8E.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERED9E.tmp.txt \\?\C:\Windows\Temp\WERA1F.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_502d2adb8edeb0eddc8dc416bd69b1e9b918be8_00000000_cab_20a50d6a Analysis symbol: Rechecking for solution: 0 Report ID: 2e1aa853-7b2f-401a-bb0c-547e2dfbaa99 Report Status: 268435456 Hashed bucket:12/09/2017 20:58 Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D, type 0 Event Name: LiveKernelEvent Response: Nicht verfügbar Cab Id: 85dc08cd-24d6-4607-b959-bb9247988704 Problem signature: P1: 141 P2: ffffe48713f4a4a0 P3: fffff80ab0a3e0bc P4: 0 P5: 454 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20170912-2244.dmp \\?\C:\Windows\Temp\WER-33285640-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERED5B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERED5B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERED6C.tmp.txt \\?\C:\Windows\Temp\WERF30A.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_eac53edff24c88f08c159c939053db28a0a7e762_00000000_cab_3168f6a3 Analysis symbol: Rechecking for solution: 0 Report ID: 792e026a-4636-499e-904c-9f55a668820c Report Status: 268435456 Hashed bucket:[/quote]
    For all tests please post logs and images into the thread.
    For Memtest86+ version 5.01 please use a camera or smart phone camera to take a picture and post an image into the thead.
     
    zbook, Apr 5, 2018
    #6
Thema:

BSOD playing the new South Park, error 0x000000c4

Loading...
  1. BSOD playing the new South Park, error 0x000000c4 - Similar Threads - BSOD playing South

  2. BSOD crashes: The bugcheck was: 0x000000c4 AND The bugcheck was: 0x000000c2

    in Windows 10 Software and Apps
    BSOD crashes: The bugcheck was: 0x000000c4 AND The bugcheck was: 0x000000c2: Hello community members!Since 2 days, I have started getting BSODs out of the blue...excuse the pun. The bugcheck was: 0x000000c2 The bugcheck was: 0x000000c4 I have not overclocked my computernot changed anything recently as was away for 3 weeksran memtest without any...
  3. BSOD crashes: The bugcheck was: 0x000000c4 AND The bugcheck was: 0x000000c2

    in Windows 10 Gaming
    BSOD crashes: The bugcheck was: 0x000000c4 AND The bugcheck was: 0x000000c2: Hello community members!Since 2 days, I have started getting BSODs out of the blue...excuse the pun. The bugcheck was: 0x000000c2 The bugcheck was: 0x000000c4 I have not overclocked my computernot changed anything recently as was away for 3 weeksran memtest without any...
  4. Windows 10 crashing into Blue Screen Error: 0x000000c4

    in Windows 10 Gaming
    Windows 10 crashing into Blue Screen Error: 0x000000c4: Windows 10 crashes into BSOD repeatedly. I have run the DMP file in WinDbg. This is what I got from WinDbgDRIVER_VERIFIER_DETECTED_VIOLATION C4A device driver attempting to corrupt the system has been caught. This isbecause the driver was specified in the registry as being...
  5. Windows 10 crashing into Blue Screen Error: 0x000000c4

    in Windows 10 Gaming
    Windows 10 crashing into Blue Screen Error: 0x000000c4: Windows 10 crashes into BSOD repeatedly. I have run the DMP file in WinDbg. This is what I got from WinDbgDRIVER_VERIFIER_DETECTED_VIOLATION C4A device driver attempting to corrupt the system has been caught. This isbecause the driver was specified in the registry as being...
  6. Windows 10 crashing into Blue Screen Error: 0x000000c4

    in Windows 10 Software and Apps
    Windows 10 crashing into Blue Screen Error: 0x000000c4: Windows 10 crashes into BSOD repeatedly. I have run the DMP file in WinDbg. This is what I got from WinDbgDRIVER_VERIFIER_DETECTED_VIOLATION C4A device driver attempting to corrupt the system has been caught. This isbecause the driver was specified in the registry as being...
  7. Windows 10 crashing into Blue Screen Error: 0x000000c4

    in Windows 10 Drivers and Hardware
    Windows 10 crashing into Blue Screen Error: 0x000000c4: Windows 10 crashes into BSOD repeatedly. I have run the DMP file in WinDbg. This is what I got from WinDbgDRIVER_VERIFIER_DETECTED_VIOLATION C4A device driver attempting to corrupt the system has been caught. This isbecause the driver was specified in the registry as being...
  8. Core Parking

    in Windows 10 BSOD Crashes and Debugging
    Core Parking: My cores are getting parked whenever there is heavy load. Like playing a game or trying to play YouTube videos on browser. I am using a laptop with i5-5200u. Everything just starts to stutter when 1 of the 2 cores gets blocked or disabled. It's only happening in windows 10. I...
  9. Mouse parking

    in Windows 10 Customization
    Mouse parking: I have a Logitch MX Master mouse which now after the 04/2020 update now decides it wants to park on the left hand side of the screen when only the desktop is visible. I'm getting very angry with it As another update screws around with the setting TIA...
  10. Random crashes, sometimes playing War Thunder, bugcheck: 0x000000c4

    in Windows 10 BSOD Crashes and Debugging
    Random crashes, sometimes playing War Thunder, bugcheck: 0x000000c4: Hi, Need some help - have been experiencing random crashes, sometimes while playing War Thunder. I enabled "driver verifier" and was unable to successfully boot on multiple attempts. Each time, I got "Stop code: DRIVER VERIFIER DETECTED VIOLATION", but no code to go with it....