BSOD and Random Lockups while Gaming.

anthrax2471 · 07 Apr 2018

Hey all, My friend has left me with her PC whilst on holiday, for months now shes been having BSOD issues and random lock ups (to the point where she has to physically turn the power off and on again). She can be browsing all day up until she puts a little strain on the rig like running a game for example she loads PlayerUnknown BattleGround's and she will crash out 3 times then on the 4th attempt she can continue playing has normal, I tried it myself on her system tonight first hand and it did the same thing for me, is there anything you guys can do to diagnose this?

Thanks guys.

philc43 · 10 Apr 2018

Hello,

Can you please provide some more details of your friends system? What motherboard is it?

Running the beta10 log collector will provide us with more details - see end of BSOD posting instructions and use this file. It needs to be downloaded, extracted to a folder and then run from that folder. The program will create a zip file on your desktop which can then be uploaded here.

No mini-dump files are being created after a BSOD. There might be a memory.dmp file but even this may have failed to be created. If you can find one and upload it to a file share service and share a link here that would also be helpful (it will be too big to upload directly to this thread).

Code:

2018-04-05T22:04:01.119 Dump file creation failed due to error during dump creation.
2018-04-05T22:04:19.017 Unable to produce a minidump file from the full dump file.
2018-04-05T22:04:19.032 The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000fffffffff, 0x0000000000000002, 0x0000000000000008, 0x0000000fffffffff). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.
2018-04-07T23:08:18.838 Dump file creation failed due to error during dump creation.
2018-04-07T23:15:01.103 Dump file creation failed due to error during dump creation.
2018-04-07T23:15:19.208 The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x0000000000000003, 0xffff9500e2aa7830, 0xffff9500e2aa7788, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 3c1126a3-97a2-416f-8032-81859a02e1a8.
2018-04-07T23:28:33.220 Unable to produce a minidump file from the full dump file.
2018-04-07T23:28:33.220 The computer has rebooted from a bugcheck. The bugcheck was: 0x000000fe (0x0000000000000006, 0xffffb40027849f20, 0x0000000063706458, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.
2018-04-08T14:19:27.962 Dump file creation failed due to error during dump creation.
2018-04-08T14:19:42.855 Unable to produce a minidump file from the full dump file.
2018-04-08T14:19:42.855 The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x000048beda8b48f8, 0x0000000000000002, 0x0000000000000008, 0x000048beda8b48f8). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.

anthrax2471 · 11 Apr 2018

Hey ya, I have run the Log Collector V2-Beta10 and still doesn't look like a mini dump was created, even though I had a blue screen while running it lol, anyway her motherboard is a GA-990FXA-UD3 Attachment 184366

zbook · 12 Apr 2018

The log files displayed that a memory dump file was created on 4/11/2018:
Crash dump found at C:\WINDOWS\MEMORY.DMP
Creation date: 04/11/2018 21:01:27
Size on disk: 1040 MB

The bugchecks reported in the logs were:
F7
FE
18
1A
7F
D1
A
EF
139
3B

For all steps / tests please post images into the thread.
Take Screenshot in Windows 10 Windows 10 Tutorials
In case there are problems posting images please use one drive or drop box share links.

1) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > un-check automatically restart > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

2) Open file explorer > this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp > zip > post a one drive or drop box share link into the thread

3) Open administrative command prompt and type or copy and paste:
4) sfc /scannow
5) dism /online /cleanup-image /restorehealth
6) 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
7) chkdsk /x /f /r (run on all partitions using the syntax chkdsk /x /f /r C: or chkdsk /x /f /r D: changing the partition letter to the applicable partition)
8) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste > notepad > post the results into the thread using a one drive or drop box share link.

Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Tutorials

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

10) 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.
a) 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 test 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.
b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM Windows 10 Tutorials

Code:

Event[6682]:  Log Name: System  Source: Microsoft-Windows-WER-SystemErrorReporting  Date: 2018-04-11T21:01:39.897  Event ID: 1005  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-CJK5VHC  Description: Unable to produce a minidump file from the full dump file.

Code:

Event[3206]:  Log Name: System  Source: Ntfs  Date: 2018-03-27T19:20:55.635  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-CJK5VHC  Description: A corruption was discovered in the file system structure on volume C:.The exact nature of the corruption is unknown.  The file system structures need to be scanned online.

The DRIVER_OVERRAN_STACK_BUFFER bug check has a value of 0x000000F7

The BUGCODE_USB_DRIVER bug check has a value of 0x000000FE. This indicates that an error has occurred in a universal serial bus (USB) driver.

The REFERENCE_BY_POINTER bug check has a value of 0x00000018. This indicates that the reference count of an object is illegal for the current state of the object.

The MEMORY_MANAGEMENT bug check has a value of 0x0000001A. This indicates that a severe memory management error occurred.

The UNEXPECTED_KERNEL_MODE_TRAP bug check has a value of 0x0000007F. This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

The DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at an invalid address while at a raised interrupt request level (IRQL). This is typically either a bad pointer or a pageability problem.

The CRITICAL_PROCESS_DIED bug check has a value of 0x000000EF.

The KERNEL_SECURITY_CHECK_FAILURE bug check has a value of 0x00000139. This bug check indicates that the kernel has detected the corruption of a critical data structure.

The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

Code:

18/02/2018 12:24    Windows Error Reporting    Fault bucket 0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiInsertTimerTable, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: eb33107b-3374-4fc0-8d83-a455aedbb857

Problem signature:
P1: 139
P2: 3
P3: ffffb48130c84710
P4: ffffb48130c84668
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\021818-7828-01.dmp
\\?\C:\WINDOWS\TEMP\WER-27046-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8760.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER876F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER879F.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: b01526e2-06d4-46ae-aaaf-4bc5b52c0ebb
Report Status: 268435456
Hashed bucket:13/03/2018 21:47    Windows Error Reporting    Fault bucket 0x139_3_CORRUPT_LIST_ENTRY_nt!EtwpDeleteRegistrationObject, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: a4dd4d95-a2c2-49a7-b716-91992ea208e0

Problem signature:
P1: 139
P2: 3
P3: ffffda0bdce6f690
P4: ffffda0bdce6f5e8
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\031318-8890-01.dmp
\\?\C:\WINDOWS\TEMP\WER-26218-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER82AD.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER82CC.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER830B.tmp.txt
\\?\C:\Windows\Temp\WER8D9B.tmp.WERDataCollectionStatus.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: 31dc7079-5de6-46dd-9522-af255c10f850
Report Status: 268435456
Hashed bucket:
21/01/2018 14:48    Windows Error Reporting    Fault bucket 0x139_3_CORRUPT_LIST_ENTRY_nt!ExAllocatePoolWithTag, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 2a5515ed-4ce7-429c-96f9-c93aa3a7aa2e

Problem signature:
P1: 139
P2: 3
P3: fffff10281afaaf0
P4: fffff10281afaa48
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\012118-7421-01.dmp
\\?\C:\WINDOWS\TEMP\WER-30250-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER92BA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER92D9.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER92FA.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: 7f43470d-71d3-40e8-b9cb-9e42a0a0e23f
Report Status: 268435456
Hashed bucket:
21/02/2018 21:25    Windows Error Reporting    Fault bucket 0x139_3_CORRUPT_LIST_ENTRY_nt!ExDeferredFreePool, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 6b227c85-8191-4d2b-80b2-97caedb68963

Problem signature:
P1: 139
P2: 3
P3: fffff68f51d94430
P4: fffff68f51d94388
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\022118-8671-01.dmp
\\?\C:\WINDOWS\TEMP\WER-28468-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8ACB.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8ADA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8B0A.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: c45cdc4f-bd0b-446e-aaa2-22f57775994b
Report Status: 268435456
Hashed bucket:
07/04/2018 22:15    Windows Error Reporting    Fault bucket 0x139_3_CORRUPT_LIST_ENTRY_nt!KiTryUnwaitThread, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0698f82a-5d40-4818-aa69-bdeaf7a19cb5

Problem signature:
P1: 139
P2: 3
P3: ffff9500e2aa7830
P4: ffff9500e2aa7788
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\040718-7421-01.dmp
\\?\C:\WINDOWS\TEMP\WER-20937-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A52.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A72.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AA1.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: 3c1126a3-97a2-416f-8032-81859a02e1a8
Report Status: 268435456
Hashed bucket:
05/04/2018 19:23    Windows Error Reporting    Fault bucket 0x18_nt!NtTerminateThread, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: e453d069-e4a6-46db-b15b-277646b3d27d

Problem signature:
P1: 18
P2: 0
P3: ffffaf8ff09c0e20
P4: 10
P5: 1
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\040518-7390-01.dmp
\\?\C:\WINDOWS\TEMP\WER-26078-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8954.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER89B2.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER89D2.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: f096e2f7-2d75-4f8c-a279-668f12f9c98f
Report Status: 268435456
Hashed bucket:
08/03/2018 19:55    Windows Error Reporting    Fault bucket 0x1a_4477_nt!MiCheckFatalAccessViolation, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: a2102ed9-b536-4cc4-9c1a-78b8fffdc3b2

Problem signature:
P1: 1a
P2: 4477
P3: 20ffffffd0
P4: 0
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\030818-7609-01.dmp
\\?\C:\WINDOWS\TEMP\WER-23609-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7781.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER77A1.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER77C1.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: 85e0c1e1-4914-45cd-8e66-8d42dbf0d98c
Report Status: 268435456
Hashed bucket:
15/02/2018 21:22    Windows Error Reporting    Fault bucket 0x3B_fltmgr!FltpPerformPreCallbacks, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 1b033526-490d-48fd-83ec-c5121b5d9d94

Problem signature:
P1: 3b
P2: c0000005
P3: fffff800877775cd
P4: ffff88842fa83d60
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\021518-7218-01.dmp
\\?\C:\WINDOWS\TEMP\WER-25640-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F90.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7FCE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7FEF.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: 14073d76-8e49-46d5-9d87-ffab5ea717a3
Report Status: 268435456
Hashed bucket:
17/03/2018 21:02    Windows Error Reporting    Fault bucket 0x3B_win32kbase!RGNOBJ::vSwap, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: a007611f-949e-4a1a-a92c-2990c764e3bb

Problem signature:
P1: 3b
P2: c0000005
P3: fffff5de11a072e0
P4: ffffe287c08de2f0
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\031718-8562-01.dmp
\\?\C:\WINDOWS\TEMP\WER-31984-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER99A0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER99BF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER99EF.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: 3b233f4c-9428-460f-b7ef-20641c30931e
Report Status: 268435456
Hashed bucket:

Code:

16/03/2018 23:50    Windows Error Reporting    Fault bucket ACCESS_VIOLATION_smss.exe_BUGCHECK_CRITICAL_PROCESS_c0000005_nt!PspCatchCriticalBreak, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 8ebe3b73-9991-44f8-8458-a4098ffe6b59

Problem signature:
P1: ef
P2: ffffe488c5797040
P3: 0
P4: 0
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\031618-7281-01.dmp
\\?\C:\WINDOWS\TEMP\WER-22140-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72AF.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72CE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72EE.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: fd06fe54-fab3-4a41-822e-a19077e4a2c1
Report Status: 268435456
Hashed bucket:20/03/2018 21:27    Windows Error Reporting    Fault bucket AV_mmcss!CiSchedulerSetPriority, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 868d1a78-52fd-4bf5-9922-73d593904517

Problem signature:
P1: d1
P2: 400c0102
P3: 2
P4: 0
P5: fffff80728fe30b5
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\032018-7265-01.dmp
\\?\C:\WINDOWS\TEMP\WER-22546-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7242.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7261.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7291.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: f06971f7-29b5-43fa-b771-fa73478ddd1f
Report Status: 268435460
Hashed bucket:
18/03/2018 19:57    Windows Error Reporting    Fault bucket AV_nt!IopCloseWaitCompletionPacket, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 9aa2153b-2d91-4672-9143-2078c2e4dda0

Problem signature:
P1: a
P2: 60
P3: 2
P4: 1
P5: fffff802b434810c
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\031818-7984-01.dmp
\\?\C:\WINDOWS\TEMP\WER-27015-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7FFD.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER801C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER804C.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: bb830bac-6914-4f4d-93a4-debce398a569
Report Status: 268435456
Hashed bucket:
24/02/2018 11:58    Windows Error Reporting    Fault bucket AV_R_INVALID_nt!ObpCreateHandle, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: aeb06a2f-e477-4931-b674-e407ea03694e

Problem signature:
P1: 50
P2: ffff8c80477b5a68
P3: 0
P4: fffff8019c90efa3
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\022418-7593-01.dmp
\\?\C:\WINDOWS\TEMP\WER-25796-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7FBF.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7FFD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER802D.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: 579da0f2-5fb6-48b4-96b2-fd58ca9e2bf3
Report Status: 268435456
Hashed bucket:
30/01/2018 19:40    Windows Error Reporting    Fault bucket AV_usbohci!OHCI_PollAsyncEndpoint, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 24b4275a-320a-4cfe-a9e1-0ee7081fc229

Problem signature:
P1: d1
P2: ffffd581e0d940a8
P3: 2
P4: 1
P5: fffff808cb6b3044
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\013018-7375-01.dmp
\\?\C:\WINDOWS\TEMP\WER-24609-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A12.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A31.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A80.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: b8d97fee-a153-4b96-89cb-83ec11f756b3
Report Status: 268435456
Hashed bucket:
18/02/2018 12:33    Windows Error Reporting    Fault bucket IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 4830c889-7826-4606-96c1-96037feaae82

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

Attached files:
\\?\C:\WINDOWS\Minidump\021818-8062-01.dmp
\\?\C:\WINDOWS\TEMP\WER-26312-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER83B6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER83C6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER83E6.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: 3eb66dac-2bb0-49fb-b0a5-d4e2636ea279
Report Status: 268435456
Hashed bucket:
28/02/2018 21:14    Windows Error Reporting    Fault bucket IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: b218219f-257c-4910-8685-3e9e8b7a8642

Problem signature:
P1: 7f
P2: 8
P3: fffff803e2467e70
P4: ffff9e0d10d66028
P5: fffff803e02ecc10
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\022818-9968-01.dmp
\\?\C:\WINDOWS\TEMP\WER-39218-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB3A0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB3B2.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB3D2.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: ea02d73d-8051-4d57-9424-154a6b15bc66
Report Status: 268435456
Hashed bucket:
26/03/2018 22:02    Windows Error Reporting    Fault bucket IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: df3c1b1b-e34d-4e61-a188-4476c41c699c

Problem signature:
P1: 7f
P2: 8
P3: fffff80050e67e70
P4: fffff10a190a1f80
P5: fffff8004ed03d97
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\032618-7359-01.dmp
\\?\C:\WINDOWS\TEMP\WER-25265-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7E77.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7EA5.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7FDF.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: 8c9437aa-de5d-4751-878d-e78574953588
Report Status: 268435456
Hashed bucket:
28/01/2018 19:57    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Maxwell_3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 337704a1-02ff-4bdf-9f16-8419d4b53707

Problem signature:
P1: 141
P2: ffff95048fc7e4a0
P3: fffff80d0b01b8e4
P4: 0
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180128-1957.dmp
\\?\C:\WINDOWS\TEMP\WER-21720187-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER836E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER837E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER839E.tmp.txt
\\?\C:\Windows\Temp\WERC48F.tmp.WERDataCollectionStatus.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: b5db42af-3afe-46d5-a8f2-66cb21fb776f
Report Status: 268435456
Hashed bucket:

anthrax2471 · 14 Apr 2018

Hey ya, sorry for the delayed reply I have had to give the pc back so having to use teamviewer, I have the memory.DMP file and the ccleaner in the onedrive folder Adam - Google Drive.

Will get the disk check done and post the results back bud.

zbook · 14 Apr 2018

1) For Ccleaner uncheck:
a) Memory dumps
b) Windows log files

2) The memory dump file that was posted displayed partition corruption.

3) For any BSOD post:
a) beta log collector zip
b) memory dump: C:\Windows\memory.dmp > zip > one drive or drop box share link

4) When available post the results of steps in post #4

anthrax2471 · 25 Jun 2018

I'm currently at wits end with a friends pc, I was told her pc lock ups and blue screens were looking towards a ram issue, she bought a Corsair 16GB DDR3 Vengeance kit (2 8GB sticks) but when she boots up a game her pc just locks up, no BSOD just a lock up, I thought it might have been overheating but she cleaned it yesterday so can't be that, could it be a bad DIMM slot? or Hard drive related? For what it's worth shes running Windows 10 with all the updates up to date.

zbook · 25 Jun 2018

Is the post today for the same computer with the last post on April 14?
The information requested was not yet posted.
If it is the same computer please update the progress for the steps in the prior post and in post #4.

anthrax2471 · 25 Jun 2018

It is the same computer, and I did all the tasks that were asked last time, I think the only thing I didn't upload was a Memory.DMP file as I couldn't find it on her pc, I'm going to check her Bios tomorrow to see if that's up to date.

zbook · 25 Jun 2018

For post #4 please post the images / results of each of the steps ( scannow, restorehealth, chkdsk, etc)
Please post a BETA log collector zip into the thread.
https://www.tenforums.com/attachment...-v2-beta10.zip
(extract > open)
When available post an image of the Memtest86+ version 5.01 results for 8 or more passes.