Windows 10: BSOD for 3 years ago "Probably caused by : GenuineIntel"

Discus and support BSOD for 3 years ago "Probably caused by : GenuineIntel" in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi I've made up my computer something like 3 years ago with windows 8 I encounter sporadic BSOD and always though it was windows issue. Always... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by jerelev, Sep 6, 2017.

  1. jerelev Win User

    BSOD for 3 years ago "Probably caused by : GenuineIntel"


    Hi
    I've made up my computer something like 3 years ago with windows 8
    I encounter sporadic BSOD and always though it was windows issue. Always hopping that a windows update will fix it someday.

    I recently updated my PC to windows 10 - same behavior. I've updated the bios, reset to default - nothing helps.

    I decided to investigate.
    Attached 2 log files with same windbg content.
    I ran your tool and again, BSOD ... i will run it right after i finish this and upload the file if available.

    Seems my CPU is the issue here.

    Your help will be highly appreciated.

    Thanks
    Attachment 152353 Attachment 152354

    System Spec

    Computer typeBSOD for 3 years ago "Probably caused by : GenuineIntel" :pC/Desktop
    System Manufacturer/Model Number:Hand made
    OS:windows 10
    CPU:i7 4770K
    Motherboard:ASUS H87-PRO bios 2104
    Memory:16GB
    Graphics Card(s):Nvidia GTX 1050 (recently added)


    Here it is : Attachment 152355

    :)
     
    jerelev, Sep 6, 2017
    #1

  2. cakewalk (a multi track recording studio)

    That is true today Michael but that post was written over 3 years ago before the branding was a huge deal.
     
    Jack Cook - aka Help_Line, Sep 6, 2017
    #2
  3. vilu85 Win User
    " Waiting for approval " until when !????

    It means that it's waiting for approval from your operator and it has nothing to do with Nokia.

    You could call your operator and ask about this approval, someone in technical service may know that how long it takes to approve the newest firmware. (For some reason, every operator has to approve the firmware updates and only after that their clients
    can do the update)
     
    vilu85, Sep 6, 2017
    #3
  4. Spectrum Win User

    BSOD for 3 years ago "Probably caused by : GenuineIntel"

    From the crash dumps you are indeed seeing hardware errors, specifically issues with your CPU's cache.

    Code: =============================================================================== Common Platform Error Record @ ffffba018966a028 ------------------------------------------------------------------------------- Record Id : 01d327f94c662ad4 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 9/7/2017 18:57:52 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffba018966a0a8 Section @ ffffba018966a180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Generic Flags : 0x00 Level : 0 CPU Version : 0x00000000000306c3 Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffba018966a0f0 Section @ ffffba018966a240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : c3 06 03 00 00 08 10 00 - bf fb da 7f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffba018966a240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffba018966a138 Section @ ffffba018966a2c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : DCACHEL0_WR_ERR (Proc 0 Bank 1) Status : 0xbf80000000000124 Address : 0x000000029a03d380 Misc. : 0x0000000000000086[/quote] Since you are already running the latest firmware, I'd say your next steps should include:

    1. Ensuring nothing is overclocked, and that all power settings in your BIOS are set to default.

    2. Checking that your CPU and motherboard aren't overheating, use something like HWMonitor

    3. Considering replacing the CPU or building a new system when your funds allow it.
     
    Spectrum, Sep 6, 2017
    #4
  5. jerelev Win User
    Yes, that's what i saw. just wanted a professional advice. I will check your recommendations.
    Thanks!
     
    jerelev, Sep 6, 2017
    #5
  6. zbook New Member
    There were WHEA 0x124 errors in the BSOD debugging which is highly indicative of a hardware problem.
    For WHEA we typically test CPU, GPU, drive, PSU , RAM/MB
    Stress testing is performed with temperature monitoring.

    1) open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /restorehealth
    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) chkdsk /x /f /r
    This may take many hours so plan to run over night.
    5) When chkdsk has completed please open event.vwr to find the log and post into the thread:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials

    5) Turn off Windows fast startup:
    Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

    6) Run HDTune: 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 Windows 10 General Tips Tutorials

    7) Make sure that there is no over clocking while troubleshooting.
    8) Sometimes there are problems in the bios that produce bsod.
    The BIOS: BIOS Version/Date American Megatrends Inc. 2104, 28/10/2014
    9) Please check to see if this is the most up to date version.
    10) To ensure that there are no improper bios settings please reset the bios.
    11) Sometimes there can be failure to boot after resetting the bios.
    12) So please make sure your files are backed up.
    13) Please make a backup image with Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Your Image is Everything
    Macrium Software | Your Image is Everything
    14) 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
    How to Clear Your Computers CMOS to Reset BIOS Settings
    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow
    3 Ways to Reset Your BIOS - wikiHow


    Once the bios is reset and there is no overclocking:
    15) Use temperature monitroing software such as:
    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
    HWMONITOR | Softwares | CPUID

    16) Run Prime95 - Stress Test Your CPU
    Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
    Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
    17) Record maximum temperatures and duration of testing.
    18) Please use the Microsoft snipping tool to post images into the thread.
    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
    Please record test duration and maximum temperature.

    19) 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
    Microsoft Community
    20) When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image of the results into the thread.
    MemTest86+ - Test RAM Windows 10 BSOD Tutorials
    MemTest86+ - Test RAM Windows 10 BSOD Tutorials
    MemTest86+ needs to be run for at least 8 complete passes for conclusive results.

    21) Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
    Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
    FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
    FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
    Please record test duration and maximum temperature.

    22) All of these test should be done with the bios reset and no over clocking.

    23) For each of the above tests please record maximum temperatures.

    24) And please make sure that you use the Microsoft snipping tool to post images of each into the thread.
    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials

    25) Please update the information on the computer specifications:
    Ten Forums System Specificiations (Specs)
    Please fill in your system specs
    Please follow this tutorial and download the tool.
    System Info - See Your System Specs - Windows 7 Help Forums
    System Info - See Your System Specs - Windows 7 Help Forums
    The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling, case, and other used stuff like mouse, keyboard, joystick, xbox, headphone, printer, etc.
    The PSU, cooling and other stuff are NOT mentioned in the tool.
    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.

    26) download and install the Intel Processor Diagnostic Tool
    When the test completes please use the Microsoft snipping tool to post an image into the thread.
    Download Intel® Processor Diagnostic Tool:
    Download Intel® Processor Diagnostic Tool
    The Intel® Processor Diagnostic Tool:
    The Intel® Processor Diagnostic Tool


    Code: Windows failed fast startup with error status 0xC00000D4.[/quote] Code: Event[2915]: Log Name: System Source: Application Popup Date: 2017-07-24T08:47:34.193 Event ID: 26 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-4AB24FD Description: Application popup: Windows - Delayed Write Failed : Exception Processing Message 0xc0000222 Parameters 0x7ffcaf771718 0x7ffcaf771718 0x7ffcaf771718 0x7ffcaf771718[/quote] Code: Event[2914]: Log Name: System Source: NTFS Date: 2017-07-24T08:47:34.191 Event ID: 50 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-4AB24FD Description: {Delayed Write Failed} Windows was unable to save all the data for the file \$Mft::$BITMAP. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.[/quote] Code: Event[8555]: Log Name: System Source: volmgr Date: 2017-09-07T19:49:41.816 Event ID: 49 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-4AB24FD Description: Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.[/quote] Code: Event[2910]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-07-24T08:46:40.237 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-4AB24FD Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: G:, DeviceName: \Device\HarddiskVolume9. (A device which does not exist was specified.)[/quote] Code: 0: kd> !errrec ffffba018966a028 =============================================================================== Common Platform Error Record @ ffffba018966a028 ------------------------------------------------------------------------------- Record Id : 01d327f94c662ad4 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 9/7/2017 18:57:52 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffba018966a0a8 Section @ ffffba018966a180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Generic Flags : 0x00 Level : 0 CPU Version : 0x00000000000306c3 Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffba018966a0f0 Section @ ffffba018966a240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : c3 06 03 00 00 08 10 00 - bf fb da 7f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffba018966a240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffba018966a138 Section @ ffffba018966a2c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : DCACHEL0_WR_ERR (Proc 0 Bank 1) Status : 0xbf80000000000124 Address : 0x000000029a03d380 Misc. : 0x0000000000000086[/quote]
    Code: 17/08/2017 20:23 Windows Error Reporting Fault bucket 0x124_GenuineIntel_PROCESSOR_CACHE, type 0 Event Name: BlueScreen Response: Not available Cab Id: 141e1ca3-c321-4588-b4cd-41d69dfa2644 Problem signature: P1: 124 P2: 0 P3: ffffb004f0478028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\081717-14343-01.dmp \\?\C:\Windows\Temp\WER-14921-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45F2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4611.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4622.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_5d080c2f97ade3cae05448714ad313c1f42dc4_00000000_cab_13387f9f Analysis symbol: Rechecking for solution: 0 Report Id: 14a6253b-acdf-4c49-b886-4a8bff0bd385 Report Status: 268435456 Hashed bucket:22/08/2017 15:29 Windows Error Reporting Fault bucket 0x124_GenuineIntel_PROCESSOR_CACHE, type 0 Event Name: BlueScreen Response: Not available Cab Id: 2530ea37-3578-4668-a4b9-6839fb5b4029 Problem signature: P1: 124 P2: 0 P3: ffffd6839d685028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\082217-14203-01.dmp \\?\C:\Windows\Temp\WER-14578-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4556.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4575.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4576.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_33498acc8eeaba478a5a278c5fc48d531ebbcf54_00000000_cab_020c6205 Analysis symbol: Rechecking for solution: 0 Report Id: 43d90443-564d-4762-bd92-be3b1434b5c5 Report Status: 268435456 Hashed bucket: 07/09/2017 08:24 Windows Error Reporting Fault bucket 0x124_GenuineIntel_PROCESSOR_CACHE, type 0 Event Name: BlueScreen Response: Not available Cab Id: 5a549347-3fca-4951-9129-6b069519f297 Problem signature: P1: 124 P2: 0 P3: ffffcc003aa99028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\090717-14265-01.dmp \\?\C:\Windows\Temp\WER-14687-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4507.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4527.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4528.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_edb641354cf31a6531fceb1fc167ea99b79dcfa6_00000000_cab_1360631f Analysis symbol: Rechecking for solution: 0 Report Id: 07179abf-1fb3-45f7-a14f-95bd060a83ed Report Status: 268435456 Hashed bucket: 07/09/2017 18:59 Windows Error Reporting Fault bucket 0x124_GenuineIntel_PROCESSOR_CACHE, type 0 Event Name: BlueScreen Response: Not available Cab Id: 7b5e3eab-c255-48b0-a949-ac28f0114a66 Problem signature: P1: 124 P2: 0 P3: ffffba018966a028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\090717-14343-01.dmp \\?\C:\Windows\Temp\WER-14843-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4601.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4621.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4622.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_69f08c4952253dc06dd5dbd6d3659a9a17aab6c7_00000000_cab_13ac6eb7 Analysis symbol: Rechecking for solution: 0 Report Id: dcca2c2b-5a3c-4a43-a4cc-062681e63abe Report Status: 268435456 Hashed bucket: 03/09/2017 18:30 Windows Error Reporting Fault bucket 0x124_GenuineIntel_PROCESSOR_CACHE, type 0 Event Name: BlueScreen Response: Not available Cab Id: bcc1a4b6-6767-4199-86d9-ae78e1a20916 Problem signature: P1: 124 P2: 0 P3: ffffc20b53078028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\090317-14468-01.dmp \\?\C:\Windows\Temp\WER-15140-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46EC.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46FB.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER470C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_51dc60e126a869e0e5db161ece532c7f195ab3_00000000_cab_13847251 Analysis symbol: Rechecking for solution: 0 Report Id: 4f4edf08-26d2-4975-9030-910d44663b31 Report Status: 268435456 Hashed bucket: 06/09/2017 22:58 Windows Error Reporting Fault bucket 0x124_GenuineIntel_PROCESSOR_CACHE, type 0 Event Name: BlueScreen Response: Not available Cab Id: e6e5b9d5-f28b-4f54-aa72-e25e4ce5a95e Problem signature: P1: 124 P2: 0 P3: ffffa60808864028 P4: ff800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\090717-14281-01.dmp \\?\C:\Windows\Temp\WER-14859-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46CD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46DC.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46DD.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_835a724dd3f1f1fea8284a9057795d6d26c2d2_00000000_cab_164b17de Analysis symbol: Rechecking for solution: 0 Report Id: 6624c10c-939d-425d-b5eb-c0c3262ba0af Report Status: 268435556 Hashed bucket:[/quote]
    Code: 05/09/2017 18:10 Windows Error Reporting Fault bucket LKD_LEAKED_SESSION_POOLTAG_DCwr, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 39157b08-eea8-4a38-ac3c-372370f82a4a Problem signature: P1: ab P2: 3 P3: 180 P4: 0 P5: 8 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\win32k.sys\win32k.sys-20170905-2110.dmp \\?\C:\Windows\Temp\WER-92063187-0.sysdata.xml \\?\C:\Windows\LiveKernelReports\win32k.sys-20170905-2110.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF87.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF89.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF9A.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ab_f57362a98196c9b35d9d63c21780e7c364fae8c0_00000000_cab_04c913d4 Analysis symbol: Rechecking for solution: 0 Report Id: adda9006-cd8b-4bfa-990d-fe9431e28dbf Report Status: 268435456 Hashed bucket:[/quote] Code: 05/09/2017 18:10 Application Error Faulting application name: NVDisplay.Container.exe, version: 1.2.0.0, time stamp: 0x59079e96 Faulting module name: ntdll.dll, version: 10.0.15063.447, time stamp: 0xa329d3a8 Exception code: 0xc0000005 Fault offset: 0x00000000000199f4 Faulting process id: 0x728 Faulting application start time: 0x01d3259bf5ed58b0 Faulting application path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 4c447aac-cbf9-426a-ae30-3757ab247a08 Faulting package full name: Faulting package-relative application ID:03/09/2017 17:51 Application Error Faulting application name: NVDisplay.Container.exe, version: 1.2.0.0, time stamp: 0x59079e96 Faulting module name: NvXDCore.dll_unloaded, version: 8.17.13.8205, time stamp: 0x59079dd9 Exception code: 0xc0000005 Fault offset: 0x00000000000c1951 Faulting process id: 0x704 Faulting application start time: 0x01d32415b4c50339 Faulting application path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe Faulting module path: NvXDCore.dll Report Id: f4ef7360-1d52-4cbc-8f52-77ed652b47c1 Faulting package full name: Faulting package-relative application ID: 06/08/2017 17:19 Application Error Faulting application name: NVDisplay.Container.exe, version: 1.2.0.0, time stamp: 0x59079e96 Faulting module name: NvXDCore.dll_unloaded, version: 8.17.13.8205, time stamp: 0x59079dd9 Exception code: 0xc0000005 Fault offset: 0x00000000000c1951 Faulting process id: 0x730 Faulting application start time: 0x01d30ed7b388300a Faulting application path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe Faulting module path: NvXDCore.dll Report Id: e40c64b7-e00e-4618-af89-87bc571798a9 Faulting package full name: Faulting package-relative application ID:[/quote]
    Code: 04/08/2017 06:21 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffff9d8293678028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\080317-14453-01.dmp \\?\C:\Windows\Temp\WER-14875-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4650.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER465F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4660.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_dd2ce669e221d6350fc664fd4669c116cc8685_00000000_cab_12ac473a Analysis symbol: Rechecking for solution: 0 Report Id: 2866f77d-7879-4399-86de-8dc2565bdd95 Report Status: 2049 Hashed bucket:04/08/2017 06:21 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffff9d8293678028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\080317-14453-01.dmp \\?\C:\Windows\Temp\WER-14875-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4650.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER465F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4660.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_dd2ce669e221d6350fc664fd4669c116cc8685_00000000_031c465f Analysis symbol: Rechecking for solution: 0 Report Id: 2866f77d-7879-4399-86de-8dc2565bdd95 Report Status: 4 Hashed bucket: 26/07/2017 06:07 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffff9f06b066a028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\072517-14421-01.dmp \\?\C:\Windows\Temp\WER-14843-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46AD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46BD.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46BE.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_c1119d2bff758343a932258aeecce26d2a92d_00000000_cab_130847a7 Analysis symbol: Rechecking for solution: 0 Report Id: b3b4ecaf-f53c-44fb-8510-c46e2b160f0b Report Status: 2049 Hashed bucket: 26/07/2017 06:07 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffff9f06b066a028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\072517-14421-01.dmp \\?\C:\Windows\Temp\WER-14843-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46AD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46BD.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46BE.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_c1119d2bff758343a932258aeecce26d2a92d_00000000_031c46bd Analysis symbol: Rechecking for solution: 0 Report Id: b3b4ecaf-f53c-44fb-8510-c46e2b160f0b Report Status: 4 Hashed bucket: 06/08/2017 17:16 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffa28149464028 P4: ff800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\080617-26984-01.dmp \\?\C:\Windows\Temp\WER-27359-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER74D2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER74E1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER74F2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_1a26c383d986f92eb5ea2b4d9d50318998cd6cf9_00000000_cab_1280756e Analysis symbol: Rechecking for solution: 0 Report Id: b778b8ae-bbec-41de-8077-fb80d05f83f6 Report Status: 2049 Hashed bucket: 06/08/2017 17:16 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffa28149464028 P4: ff800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\080617-26984-01.dmp \\?\C:\Windows\Temp\WER-27359-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER74D2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER74E1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER74F2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_1a26c383d986f92eb5ea2b4d9d50318998cd6cf9_00000000_031474f1 Analysis symbol: Rechecking for solution: 0 Report Id: b778b8ae-bbec-41de-8077-fb80d05f83f6 Report Status: 4 Hashed bucket: 06/09/2017 22:55 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffa60808864028 P4: ff800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\090717-14281-01.dmp \\?\C:\Windows\Temp\WER-14859-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46CD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46DC.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46DD.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_835a724dd3f1f1fea8284a9057795d6d26c2d2_00000000_cab_031c46dc Analysis symbol: Rechecking for solution: 0 Report Id: 6624c10c-939d-425d-b5eb-c0c3262ba0af Report Status: 100 Hashed bucket: 06/09/2017 22:55 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffa60808864028 P4: ff800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\090717-14281-01.dmp \\?\C:\Windows\Temp\WER-14859-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46CD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46DC.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46DD.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_835a724dd3f1f1fea8284a9057795d6d26c2d2_00000000_cab_031c46dc Analysis symbol: Rechecking for solution: 0 Report Id: 6624c10c-939d-425d-b5eb-c0c3262ba0af Report Status: 4 Hashed bucket: 22/08/2017 08:17 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffae827c678028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\082217-14390-01.dmp \\?\C:\Windows\Temp\WER-14875-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4601.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4621.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4622.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_119a9e3d4dfb95b599a9828293f1728337c595b_00000000_cab_031c4630 Analysis symbol: Rechecking for solution: 0 Report Id: 8d4401e2-f9a3-480e-b99c-54ca1d66ff82 Report Status: 100 Hashed bucket: 22/08/2017 08:14 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffae827c678028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\082217-14390-01.dmp \\?\C:\Windows\Temp\WER-14875-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4601.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4621.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4622.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_119a9e3d4dfb95b599a9828293f1728337c595b_00000000_cab_031c4630 Analysis symbol: Rechecking for solution: 0 Report Id: 8d4401e2-f9a3-480e-b99c-54ca1d66ff82 Report Status: 100 Hashed bucket: 22/08/2017 08:14 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffae827c678028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\082217-14390-01.dmp \\?\C:\Windows\Temp\WER-14875-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4601.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4621.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4622.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_119a9e3d4dfb95b599a9828293f1728337c595b_00000000_cab_031c4630 Analysis symbol: Rechecking for solution: 0 Report Id: 8d4401e2-f9a3-480e-b99c-54ca1d66ff82 Report Status: 4 Hashed bucket: 14/07/2017 23:25 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffb00450e6a028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\071417-14453-01.dmp \\?\C:\Windows\Temp\WER-15031-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4630.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4650.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4651.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_d9b7ce776ee94d1de5c3851cf5e0ad7f8647b_00000000_cab_12ac47e6 Analysis symbol: Rechecking for solution: 0 Report Id: 3148d070-1543-4007-88d8-54ef3ffca836 Report Status: 2049 Hashed bucket: 14/07/2017 23:25 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffb00450e6a028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\071417-14453-01.dmp \\?\C:\Windows\Temp\WER-15031-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4630.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4650.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4651.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_d9b7ce776ee94d1de5c3851cf5e0ad7f8647b_00000000_031c4650 Analysis symbol: Rechecking for solution: 0 Report Id: 3148d070-1543-4007-88d8-54ef3ffca836 Report Status: 4 Hashed bucket: 17/08/2017 20:23 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffb004f0478028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\081717-14343-01.dmp \\?\C:\Windows\Temp\WER-14921-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45F2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4611.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4622.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_5d080c2f97ade3cae05448714ad313c1f42dc4_00000000_cab_03204621 Analysis symbol: Rechecking for solution: 0 Report Id: 14a6253b-acdf-4c49-b886-4a8bff0bd385 Report Status: 4 Hashed bucket: 07/09/2017 18:59 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffba018966a028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\090717-14343-01.dmp \\?\C:\Windows\Temp\WER-14843-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4601.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4621.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4622.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_69f08c4952253dc06dd5dbd6d3659a9a17aab6c7_00000000_cab_03144630 Analysis symbol: Rechecking for solution: 0 Report Id: dcca2c2b-5a3c-4a43-a4cc-062681e63abe Report Status: 4 Hashed bucket: 14/07/2017 23:29 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffbf01a9264028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\071417-14390-01.dmp \\?\C:\Windows\Temp\WER-14953-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45C3.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45D3.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45E3.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_a310ba153749396fa2dce14906b857d2fa57c_00000000_cab_12d44788 Analysis symbol: Rechecking for solution: 0 Report Id: b4b9e85e-d71a-4ae5-81e0-3d06f1a2996c Report Status: 2049 Hashed bucket: 14/07/2017 23:29 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffbf01a9264028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\071417-14390-01.dmp \\?\C:\Windows\Temp\WER-14953-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45C3.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45D3.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45E3.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_a310ba153749396fa2dce14906b857d2fa57c_00000000_032045e2 Analysis symbol: Rechecking for solution: 0 Report Id: b4b9e85e-d71a-4ae5-81e0-3d06f1a2996c Report Status: 4 Hashed bucket: 03/09/2017 18:30 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffc20b53078028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\090317-14468-01.dmp \\?\C:\Windows\Temp\WER-15140-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46EC.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46FB.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER470C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_51dc60e126a869e0e5db161ece532c7f195ab3_00000000_cab_0314470b Analysis symbol: Rechecking for solution: 0 Report Id: 4f4edf08-26d2-4975-9030-910d44663b31 Report Status: 4 Hashed bucket: 07/09/2017 08:24 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffcc003aa99028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\090717-14265-01.dmp \\?\C:\Windows\Temp\WER-14687-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4507.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4527.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4528.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_edb641354cf31a6531fceb1fc167ea99b79dcfa6_00000000_cab_03144536 Analysis symbol: Rechecking for solution: 0 Report Id: 07179abf-1fb3-45f7-a14f-95bd060a83ed Report Status: 4 Hashed bucket: 22/08/2017 15:29 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffd6839d685028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\082217-14203-01.dmp \\?\C:\Windows\Temp\WER-14578-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4556.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4575.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4576.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_33498acc8eeaba478a5a278c5fc48d531ebbcf54_00000000_cab_03184575 Analysis symbol: Rechecking for solution: 0 Report Id: 43d90443-564d-4762-bd92-be3b1434b5c5 Report Status: 4 Hashed bucket: 17/07/2017 07:02 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffe28dd0e6a028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\071717-14593-01.dmp \\?\C:\Windows\Temp\WER-15046-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E2F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E3F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E40.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_b6af2295ff79723f937cdc193f97477416809140_00000000_cab_13b84e8d Analysis symbol: Rechecking for solution: 0 Report Id: 7f1b3a57-6516-4464-ad12-05f0d85efb69 Report Status: 2049 Hashed bucket: 17/07/2017 07:02 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffe28dd0e6a028 P4: bf800000 P5: 124 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\071717-14593-01.dmp \\?\C:\Windows\Temp\WER-15046-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E2F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E3F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E40.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_b6af2295ff79723f937cdc193f97477416809140_00000000_030c4e3f Analysis symbol: Rechecking for solution: 0 Report Id: 7f1b3a57-6516-4464-ad12-05f0d85efb69 Report Status: 4 Hashed bucket:[/quote]
     
    zbook, Apr 5, 2018
    #6
Thema:

BSOD for 3 years ago "Probably caused by : GenuineIntel"

Loading...
  1. BSOD for 3 years ago "Probably caused by : GenuineIntel" - Similar Threads - BSOD years ago

  2. My computer restarted to a version 3 years ago

    in Windows 10 Installation and Upgrade
    My computer restarted to a version 3 years ago: My computer was accidentally shut down while it was in sleep mode by the power supply. I think it was turning on when the power switch was turned off then on again. When i turned it on it restarted to a version 3 years ago- the wallpaper, the apps, folders, files and...
  3. My computer restarted to a version 3 years ago

    in Windows 10 Gaming
    My computer restarted to a version 3 years ago: My computer was accidentally shut down while it was in sleep mode by the power supply. I think it was turning on when the power switch was turned off then on again. When i turned it on it restarted to a version 3 years ago- the wallpaper, the apps, folders, files and...
  4. My computer restarted to a version 3 years ago

    in Windows 10 Software and Apps
    My computer restarted to a version 3 years ago: My computer was accidentally shut down while it was in sleep mode by the power supply. I think it was turning on when the power switch was turned off then on again. When i turned it on it restarted to a version 3 years ago- the wallpaper, the apps, folders, files and...
  5. Probable cause of "CRITICAL_STRUCTURE_CORRUPTION" BSOD

    in Windows 10 Gaming
    Probable cause of "CRITICAL_STRUCTURE_CORRUPTION" BSOD: This is my first experience with this specific BSOD. I have not manually updated any drivers recently so I'm not quite sure of the issue, although it could be related to the NVIDIA display drivers I installed approx 1 month ago.Microsoft R Windows Debugger Version...
  6. Probable cause of "CRITICAL_STRUCTURE_CORRUPTION" BSOD

    in Windows 10 Software and Apps
    Probable cause of "CRITICAL_STRUCTURE_CORRUPTION" BSOD: This is my first experience with this specific BSOD. I have not manually updated any drivers recently so I'm not quite sure of the issue, although it could be related to the NVIDIA display drivers I installed approx 1 month ago.Microsoft R Windows Debugger Version...
  7. Probable cause of "CRITICAL_STRUCTURE_CORRUPTION" BSOD

    in Windows 10 BSOD Crashes and Debugging
    Probable cause of "CRITICAL_STRUCTURE_CORRUPTION" BSOD: This is my first experience with this specific BSOD. I have not manually updated any drivers recently so I'm not quite sure of the issue, although it could be related to the NVIDIA display drivers I installed approx 1 month ago.Microsoft R Windows Debugger Version...
  8. bsod probably caused by a driver

    in Windows 10 BSOD Crashes and Debugging
    bsod probably caused by a driver: i was getting bsod error's for a few days so today i decided to run driver verifier and i got a bsod with driver verifier detected violation error, i viewed the minidump file and this issue is apparently being caused by "SteamStreamingMicrophone.sys" driver, how can i fix...
  9. BSOD Probably caused by : memory_corruption

    in Windows 10 BSOD Crashes and Debugging
    BSOD Probably caused by : memory_corruption: Hi, My computer frequently has BSOD. I have used windbg to analyze 800mb dump file as attached bellow: please help , thank you! Microsoft (R) Windows Debugger Version 10.0.17763.1 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File...
  10. BSOD, Bugcheck Analysis : "probably caused by : GenuineIntel"

    in Windows 10 BSOD Crashes and Debugging
    BSOD, Bugcheck Analysis : "probably caused by : GenuineIntel": My 4-year-old custom build started having Bluescreens a month ago, it's rather random and sometimes I don't have crashes for days but it's very unpredictable. I wasn't able to trigger the crash with various test programs so I'm a little lost how I find a solution to my...