1.    04 Jul 2017 #1
    Join Date : Aug 2016
    Posts : 14
    windows 10 pro

    Unknow Blue Screen


    hi,
    can someone take a look at the crash reports and give me some idea what i should do?

    thanks,
    Nathan Saunders
      My ComputerSystem Spec
  2.    04 Jul 2017 #2
    Join Date : Apr 2017
    Posts : 8,584
    windows 10 professional version 1607 build 14393.969 64 bit

    Code:
    BugCheck 3B, {c0000005, fffff80387078c23, ffffb9816a4c3aa0, 0}Probably caused by : memory_corruptionFollowup: memory_corruption
    Code:
    BugCheck A, {ffffde8fd4c6e2b0, 2, 0, fffff801df611f10}*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption
    Code:
    +++ WER8 +++:Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0Event Name: LiveKernelEventResponse: Not availableCab Id: 59e8dde1-d8df-4412-b96c-0605cc066d06Problem signature:P1: 141P2: ffff9a07c3204250P3: fffff80730cdc584P4: 0P5: 2e5cP6: 10_0_15063P7: 0_0P8: 256_1P9: P10:
    Code:
    7/3/2017 6:09 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 59e8dde1-d8df-4412-b96c-0605cc066d06
    
    Problem signature:
    P1: 141
    P2: ffff9a07c3204250
    P3: fffff80730cdc584
    P4: 0
    P5: 2e5c
    P6: 10_0_15063
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20170703-1509.dmp
    \\?\C:\Windows\Temp\WER-1726875-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER613C.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER613C.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER614C.tmp.txt
    \\?\C:\Windows\Temp\WERC14E.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_b6771d1e5beeab77c23c844338337243477ec99_00000000_cab_1dbac2d4
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 3927241f-97a2-4955-b48b-cf59e30b656c
    Report Status: 268435456
    Hashed bucket:6/16/2017 11:35 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Maxwell_3D, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 1915678c-eba5-4331-a16f-ad07e7530565
    
    Problem signature:
    P1: 141
    P2: ffffe0873cd57010
    P3: fffff80850a7fd08
    P4: 0
    P5: 2af4
    P6: 10_0_15063
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20170616-0833.dmp
    \\?\C:\Windows\Temp\WER-10203-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER30E3.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3112.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3132.tmp.txt
    \\?\C:\Windows\Temp\WER6B6E.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_c446659689f3d37a15eb99d1519b7313722a92c_00000000_cab_17086d6f
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 854110c0-eeb2-4986-b8f2-6f827e224bf1
    Report Status: 268435456
    Hashed bucket:6/6/2017 11:40 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Maxwell_3D, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 7dcbe92f-ab6d-4525-9496-de7136b4310e
    
    Problem signature:
    P1: 141
    P2: ffffa8817f08b4a0
    P3: fffff8079d58fb28
    P4: 0
    P5: 950
    P6: 10_0_15063
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20170606-0840.dmp
    \\?\C:\Windows\Temp\WER-766312-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB7C1.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB7D3.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB7E3.tmp.txt
    \\?\C:\Windows\Temp\WERE8C5.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_5bc889f46017b154425f48f2ac21f1b9ee029_00000000_cab_1703ead7
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 4c274c2c-c5b5-4018-a6eb-aa5b8d31fb8c
    Report Status: 268435456
    Hashed bucket:5/24/2017 10:52 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Maxwell_3D, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 835986ec-8942-46d4-951a-bf89585031aa
    
    Problem signature:
    P1: 141
    P2: ffff9e0b6d1b74a0
    P3: fffff805c08efb28
    P4: 0
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20170524-1952.dmp
    \\?\C:\Windows\Temp\WER-2454156-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A3D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A4C.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A5D.tmp.txt
    \\?\C:\Windows\Temp\WER9F98.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_4e87529be35136b27e36843f1327cf51705fa120_00000000_cab_14b1a11e
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: a4e5058e-2ef5-480b-add5-600f6030aab2
    Report Status: 268435456
    Hashed bucket:6/13/2017 8:34 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Maxwell_3D, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 99e48be7-1f88-4f70-839d-ac93c7eca4d8
    
    Problem signature:
    P1: 141
    P2: ffffbd0444060010
    P3: fffff808910afd08
    P4: 0
    P5: 408
    P6: 10_0_15063
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20170613-1734.dmp
    \\?\C:\Windows\Temp\WER-997531-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FDE.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FE0.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FF1.tmp.txt
    \\?\C:\Windows\Temp\WER7363.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_9e116761a241e319c8a839da87bf2b76ba4b5d79_00000000_cab_1e7f7611
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 5052b292-5c07-424c-908f-3e047a5b6f60
    Report Status: 268435456
    Hashed bucket:6/11/2017 6:57 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Maxwell_3D, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: cd52dae3-5257-40a9-8b3f-dbc4e8c79138
    
    Problem signature:
    P1: 141
    P2: ffffc106657864a0
    P3: fffff80ce308fb28
    P4: 0
    P5: 620
    P6: 10_0_15063
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20170611-1557.dmp
    \\?\C:\Windows\Temp\WER-19025656-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER56F7.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5706.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5717.tmp.txt
    \\?\C:\Windows\Temp\WER83E4.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_686662a16ca9b18a858ffb4e9c7cbb3a47b7593_00000000_cab_1a6e855a
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: b10101a5-7f5e-4f8c-a0d1-4b4999c3ffed
    Report Status: 268435456
    Hashed bucket:5/17/2017 12:36 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Maxwell_3D, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: cf3b308a-50ea-43d9-b4a2-ea37b2684ca4
    
    Problem signature:
    P1: 141
    P2: ffffdd02530704a0
    P3: fffff80e1727f44c
    P4: 0
    P5: 2870
    P6: 10_0_15063
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20170517-0936.dmp
    \\?\C:\Windows\Temp\WER-211451593-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER86B9.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER86B9.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER86C9.tmp.txt
    \\?\C:\Windows\Temp\WERAADC.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_89f597eed7e14844d802298b94dde7627a79f_00000000_cab_2982ac61
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: c84041de-711c-4189-8e55-9edd4e307600
    Report Status: 268435456
    Hashed bucket:6/20/2017 11:26 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Maxwell_3D, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: e36f6afc-5429-4ca1-a42e-b03dbd5aab82
    
    Problem signature:
    P1: 141
    P2: ffffc880c694a4a0
    P3: fffff8056308fd08
    P4: 0
    P5: 6bc
    P6: 10_0_15063
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20170620-0826.dmp
    \\?\C:\Windows\Temp\WER-462468-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER15C8.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER15D7.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER15E8.tmp.txt
    \\?\C:\Windows\Temp\WER2C5E.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_1096172cf70a8e48f76ed39945b755d359871_00000000_cab_30bf2de4
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 5a56cd3f-c4af-407a-8a83-224fe7e65088
    Report Status: 268435456
    Hashed bucket:
    Code:
    BugCheck A, {fffff883994ea400, ff, 0, fffff80398d7cdbe}Probably caused by : ntkrnlmp.exe ( nt!KiIsrLinkage+de )
    Code:
    nvlddmkm.sys
    nvlddmkm.sys nVidia Video drivers http://www.nvidia.com/Download/index.aspx
    Get from OEM for laptops

    Code:
    BugCheck A, {2000000000, ff, 2, fffff8017469403d}Probably caused by : ntkrnlmp.exe ( nt!KeAcquireSpinLockAtDpcLevel+d )
    Code:
    amdppm
    amdppm.sys Processor Device Driver Windows Update

    Code:
    BugCheck A, {ffffc860c3f10958, ff, 0, fffff801bbefef01}*** WARNING: Unable to verify timestamp for Xeno7x64.sys*** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption
    Code:
    BFN7x64      Bigfoot Networks Kille Bigfoot Networks Kille Kernel        Manual     Running    OK         TRUE        FALSE        20,480            106,496     0          5/18/2011 7:55:16 PM   C:\Windows\system32\drivers\Xeno7x64.sys         4,096
    Xeno7x64.sys Bigfoot Networks Killer Xeno PCI-E Gaming Adapter (this card is from VisionTek) Download - http://www.killernetworking.com/supp...iver-downloads
    (Scroll below to see the section about Legacy drivers from VisionTek)
    Support - http://www.killernetworking.com/about/contact

    Code:
    5/23/2017 11:27 AM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.18.70, time stamp: 0x58e79258
    Faulting module name: nvd3dum.dll, version: 22.21.13.8205, time stamp: 0x59079242
    Exception code: 0xc0000005
    Fault offset: 0x0064e7d3
    Faulting process id: 0x22d8
    Faulting application start time: 0x01d2d3b777b80cfb
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a2b0acab06663645\nvd3dum.dll
    Report Id: d806f5d0-fa28-4790-ba64-5c2cd7c85e45
    Faulting package full name: 
    Faulting package-relative application ID:4/22/2017 12:01 AM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.18.70, time stamp: 0x58e79258
    Faulting module name: worldoftanks.exe, version: 0.9.18.70, time stamp: 0x58e79258
    Exception code: 0xc0000005
    Fault offset: 0x00660f00
    Faulting process id: 0x2c94
    Faulting application start time: 0x01d2bafb566aaae4
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: D:\Games\World_of_Tanks\worldoftanks.exe
    Report Id: 366bdcfd-542b-49e8-97e0-60a0aef44f12
    Faulting package full name: 
    Faulting package-relative application ID:4/22/2017 12:13 AM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.18.70, time stamp: 0x58e79258
    Faulting module name: worldoftanks.exe, version: 0.9.18.70, time stamp: 0x58e79258
    Exception code: 0xc0000005
    Fault offset: 0x00660f00
    Faulting process id: 0xe6c
    Faulting application start time: 0x01d2bafd458d0cb9
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: D:\Games\World_of_Tanks\worldoftanks.exe
    Report Id: ea0d1193-92af-4342-8d8e-86c58c105f3c
    Faulting package full name: 
    Faulting package-relative application ID:5/14/2017 12:22 PM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.18.70, time stamp: 0x58e79258
    Faulting module name: worldoftanks.exe, version: 0.9.18.70, time stamp: 0x58e79258
    Exception code: 0xc0000005
    Fault offset: 0x00d271aa
    Faulting process id: 0x2160
    Faulting application start time: 0x01d2ccaabff15287
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: D:\Games\World_of_Tanks\worldoftanks.exe
    Report Id: 46718210-cd49-4be3-a16e-657bd830fa3a
    Faulting package full name: 
    Faulting package-relative application ID:5/23/2017 11:26 AM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.18.70, time stamp: 0x58e79258
    Faulting module name: worldoftanks.exe, version: 0.9.18.70, time stamp: 0x58e79258
    Exception code: 0xc0000005
    Fault offset: 0x00d27260
    Faulting process id: 0x12f8
    Faulting application start time: 0x01d2d3b76316f4a0
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: D:\Games\World_of_Tanks\worldoftanks.exe
    Report Id: dcde5c8f-540d-4d5d-b870-3ac5c3fefc31
    Faulting package full name: 
    Faulting package-relative application ID:6/13/2017 9:37 PM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.19.112, time stamp: 0x592c3336
    Faulting module name: nvd3dum.dll, version: 22.21.13.8253, time stamp: 0x593884c7
    Exception code: 0xc0000005
    Fault offset: 0x0064e7d3
    Faulting process id: 0x1440
    Faulting application start time: 0x01d2e48c3dd6e306
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d81f3535ced17c6\nvd3dum.dll
    Report Id: 589c8578-0544-4968-a43c-24df911ca799
    Faulting package full name: 
    Faulting package-relative application ID:6/7/2017 1:21 AM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.19.112, time stamp: 0x592c3336
    Faulting module name: nvwgf2um.dll, version: 22.21.13.8233, time stamp: 0x591d2d0c
    Exception code: 0xc0000005
    Fault offset: 0x000f9d20
    Faulting process id: 0x11f8
    Faulting application start time: 0x01d2df05e8818997
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7209bde3180ef5f7\nvwgf2um.dll
    Report Id: 32f69c1a-3695-4897-9a47-7bc43d2b90c9
    Faulting package full name: 
    Faulting package-relative application ID:6/3/2017 2:09 PM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.19.112, time stamp: 0x592c3336
    Faulting module name: nvwgf2um.dll, version: 22.21.13.8233, time stamp: 0x591d2d0c
    Exception code: 0xc0000005
    Fault offset: 0x0069f6c4
    Faulting process id: 0x1510
    Faulting application start time: 0x01d2dc5f9c20e46a
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7209bde3180ef5f7\nvwgf2um.dll
    Report Id: 43e57123-e288-4e1e-9166-cb52873f24d1
    Faulting package full name: 
    Faulting package-relative application ID:6/6/2017 1:51 AM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.19.112, time stamp: 0x592c3336
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x00000000
    Faulting process id: 0x3a0
    Faulting application start time: 0x01d2de56b8bd410b
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: unknown
    Report Id: a6e11ae3-48ab-4386-8a17-c229f36e39cf
    Faulting package full name: 
    Faulting package-relative application ID:6/11/2017 9:25 PM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.19.112, time stamp: 0x592c3336
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x00000000
    Faulting process id: 0x7b8
    Faulting application start time: 0x01d2e2f624dace19
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: unknown
    Report Id: 7db9d4b4-fc4b-4308-aa16-fd7ee2df347c
    Faulting package full name: 
    Faulting package-relative application ID:6/13/2017 8:33 PM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.19.112, time stamp: 0x592c3336
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x00000003
    Faulting process id: 0xe00
    Faulting application start time: 0x01d2e482b6318a11
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: unknown
    Report Id: 4731e083-733f-428f-83e0-e390568e713b
    Faulting package full name: 
    Faulting package-relative application ID:6/3/2017 2:26 PM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.19.112, time stamp: 0x592c3336
    Faulting module name: worldoftanks.exe, version: 0.9.19.112, time stamp: 0x592c3336
    Exception code: 0xc0000005
    Fault offset: 0x001587b0
    Faulting process id: 0x2840
    Faulting application start time: 0x01d2dc730f2ae405
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: D:\Games\World_of_Tanks\worldoftanks.exe
    Report Id: aee0980e-8c34-4ad4-a003-08faea63952f
    Faulting package full name: 
    Faulting package-relative application ID:6/6/2017 11:38 AM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.19.112, time stamp: 0x592c3336
    Faulting module name: worldoftanks.exe, version: 0.9.19.112, time stamp: 0x592c3336
    Exception code: 0xc0000005
    Fault offset: 0x006b13d6
    Faulting process id: 0x3300
    Faulting application start time: 0x01d2deb7fd1b0447
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: D:\Games\World_of_Tanks\worldoftanks.exe
    Report Id: 5b84c9de-138f-46bd-9738-f2204c3c8489
    Faulting package full name: 
    Faulting package-relative application ID:6/11/2017 7:27 PM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.19.112, time stamp: 0x592c3336
    Faulting module name: worldoftanks.exe, version: 0.9.19.112, time stamp: 0x592c3336
    Exception code: 0xc0000005
    Fault offset: 0x00d97dd2
    Faulting process id: 0x2914
    Faulting application start time: 0x01d2e2e2c025b525
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: D:\Games\World_of_Tanks\worldoftanks.exe
    Report Id: 35f8b43d-f921-45fb-be63-8207dde89507
    Faulting package full name: 
    Faulting package-relative application ID:6/29/2017 8:44 PM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.19.113, time stamp: 0x593e75f6
    Faulting module name: worldoftanks.exe, version: 0.9.19.113, time stamp: 0x593e75f6
    Exception code: 0xc0000005
    Fault offset: 0x006834b3
    Faulting process id: 0xdf8
    Faulting application start time: 0x01d2f118223ecfa0
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: D:\Games\World_of_Tanks\worldoftanks.exe
    Report Id: 65d5784a-6692-4ba6-8d3f-6cacf2744c55
    Faulting package full name: 
    Faulting package-relative application ID:7/3/2017 6:32 PM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.19.113, time stamp: 0x593e75f6
    Faulting module name: worldoftanks.exe, version: 0.9.19.113, time stamp: 0x593e75f6
    Exception code: 0xc0000005
    Fault offset: 0x006aff0b
    Faulting process id: 0x2cd8
    Faulting application start time: 0x01d2f429259f6838
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: D:\Games\World_of_Tanks\worldoftanks.exe
    Report Id: 068226c8-63ab-426f-a595-f54881bde830
    Faulting package full name: 
    Faulting package-relative application ID:6/16/2017 11:30 AM    Application Error    Faulting application name: worldoftanks.exe, version: 0.9.19.113, time stamp: 0x593e75f6
    Faulting module name: worldoftanks.exe, version: 0.9.19.113, time stamp: 0x593e75f6
    Exception code: 0xc0000005
    Fault offset: 0x00d4365a
    Faulting process id: 0x320c
    Faulting application start time: 0x01d2e6935c10f340
    Faulting application path: D:\Games\World_of_Tanks\worldoftanks.exe
    Faulting module path: D:\Games\World_of_Tanks\worldoftanks.exe
    Report Id: 0305709e-5000-4f53-a453-7390895e5fd2
    Faulting package full name: 
    Faulting package-relative application ID:
    Code:
    USBXHCI



    Code:
    The system failed to flush data to the transaction log. Corruption may occur in VolumeId: V:, DeviceName: \Device\HarddiskVolume7.(A device which does not exist was specified.)
    Code:
    Windows failed fast startup with error status 0xC00000D4.

    Code:
    An error was detected on device \Device\Harddisk2\DR2 during a paging operation.

    Open administrative command prompt and type or copy and paste:


    1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)


    2) sfc /scannow


    3) dism /online /cleanup-image /restorehealth


    4) chkdsk /scan


    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 copy > paste into the thread



    5) uninstall/reinstall: world of tanks


    6) Run memtest86+ version 5.01 for at least 8 runs.
    This may take hours so plan to run it overnight.
    Memtest86+ - Advanced Memory Diagnostic Tool
    https://answers.microsoft.com/en-us/...c7b7ff6461When Memtest86+ has completed 8 or more runs make an image of the results to post into the thread.

    7) Uninstall all Nvidia drivers/softwareThe best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the NVidia website.
    When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.
    Display Driver Uninstaller Download version 17.0.6.7: Official Display Driver Uninstaller DDU Download

    8) Uninstall/Reinstall: Bigfoot Networks Killer Xeno PCI-E Gaming Adapter
    So far I have not found a good replacement source for a driver for this gaming adapter.

    9) Perform windows updates and post any failed KB# and error code

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

    11) run one of the SMART tests on your drives:
    CrystalDiskInfo - Software - Crystal Dew World: CrystalDiskMark - Software - Crystal Dew World
    HD Tune: http://www.hdtune.com/
    Hard Disk Sentinel - HDD health and temperature monitoring: Hard Disk Sentinel - HDD health and temperature monitoring
      My ComputerSystem Spec
  3.    05 Jul 2017 #3
    Join Date : Aug 2016
    Posts : 14
    windows 10 pro
    Thread Starter

    windows 10 Pro 1703 15063.413

    Microsoft Windows [Version 10.0.15063]
    (c) 2017 Microsoft Corporation. All rights reserved.

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

    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0

    Image Version: 10.0.15063.0

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

    C:\Windows\system32>
    C:\Windows\system32>sfc /scannow

    Beginning system scan. This process will take some time.

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

    Windows Resource Protection did not find any integrity violations.

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

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

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

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

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

    499526655 KB total disk space.
    56035888 KB in 176061 files.
    110316 KB in 34634 indexes.
    0 KB in bad sectors.
    341263 KB in use by the system.
    65536 KB occupied by the log file.
    443039188 KB available on disk.

    4096 bytes in each allocation unit.
    124881663 total allocation units on disk.
    110759797 allocation units available on disk.

    C:\Windows\system32>
      My ComputerSystem Spec
  4.    05 Jul 2017 #4
    Join Date : Aug 2016
    Posts : 14
    windows 10 pro
    Thread Starter

    so it looks like there was some problems with the install image that sfc was using because i had to fix that before i could complete the sfc... lovely anyways more tests to complete.

    is it alright that i am testing ram with memtest-86 v3.1? i know it is a older version but i find it still works
      My ComputerSystem Spec
  5.    05 Jul 2017 #5
    Join Date : Apr 2017
    Posts : 8,584
    windows 10 professional version 1607 build 14393.969 64 bit

    For the RAM / DIMM testing please use the latest version Memtest86+ version 5.01 for 8 or more passes. It will take many hours so plan to run it overnight.
    Memtest86+ - Advanced Memory Diagnostic Tool
    Please see this link : Memory problems. - Microsoft Community
      My ComputerSystem Spec
  6.    05 Jul 2017 #6
    Join Date : Aug 2016
    Posts : 14
    windows 10 pro
    Thread Starter

    Quote Originally Posted by zbook View Post
    For the RAM / DIMM testing please use the latest version Memtest86+ version 5.01 for 8 or more passes. It will take many hours so plan to run it overnight.
    Memtest86+ - Advanced Memory Diagnostic Tool
    Please see this link : Memory problems. - Microsoft Community
    may i ask why it has to be done with the last version of memtest 86+? (if the c.d. boots and the test starts the outcome will be the same ether way)

    thanks,
    Nathan Saunders
      My ComputerSystem Spec
  7.    05 Jul 2017 #7
    Join Date : Aug 2016
    Posts : 14
    windows 10 pro
    Thread Starter

    so 8 hours of memtest did not find any errors so that is a good sign on that front...
    can i use grc's Spin rite for the hard drive tests?
      My ComputerSystem Spec
  8.    05 Jul 2017 #8
    Join Date : Jun 2015
    Posts : 12,854
    Windows 10 Pro

    Quote Originally Posted by t8z5h3 View Post
    may i ask why it has to be done with the last version of memtest 86+? (if the c.d. boots and the test starts the outcome will be the same ether way)
    thanks,
    Nathan Saunders
    The newest version contains various improvements and fixes since the previous version, any error shown or not shown may be caused by a bug and could be unreliable. To be certain about the result it is best to run the latest version.
      My ComputersSystem Spec
  9.    05 Jul 2017 #9
    Join Date : Aug 2016
    Posts : 14
    windows 10 pro
    Thread Starter

    will i ever get this computer fixed?
      My ComputerSystem Spec
  10.    27 Jul 2017 #10
    Join Date : Aug 2016
    Posts : 14
    windows 10 pro
    Thread Starter

    I enabled A-XMP to fix it... odd how a ram overclock fixed my issues.
      My ComputerSystem Spec

 


Similar Threads
Thread Forum
Blue Screen caused by graphics card/dual screen
I keep getting blue screens when I am in dual screen. Crash happens when I try to use the computer after some time of inactivity with just a video playing.
BSOD Crashes and Debugging
Solved Unknow Publisher Warning
I downloaded and opened updated drivers and software for new printer, but then my comp asks me if I will allow this app to make changes to my computer....publisher unknown. I am hesitant to allow this, but I got the download from Brother website....
General Support
Solved Logon screen problem, blue screen with dots circle after Ann. Update
Running anniversary update here... I start my computer, then it loads until I get the main screen (with the clock and date), where I can choose my username and enter my password ( I have 5 users). Sometimes when clicking or typing enter, I can...
General Support
Black screen or Crash Blue Screen
hy my problem is black screen in access windows 10 or blue screen error nvlddmkm tnk
BSOD Crashes and Debugging
Solved Can't log in. Flashing between lock screen & blue screen
EDIT: I solved the issue. On the GitHub page for the program there was already a well-written tutorial on how to fix the issue. Heh. Well, I made a big mistake. I upgraded from Windows 8 to 10 without a hitch an hour ago and kept all of my...
General Support
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 11:03.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums