Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

PC crashing whilst gaming, likely hardware?


  • Please log in to reply
9 replies to this topic

#1 Burns-Help

Burns-Help

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:11:39 PM

Posted 19 November 2017 - 09:53 AM

My PC has run perfectly for years, but since the 21 of October it has started crashing whilst I play some games. Rocket League seems to be the most often cause but it has crashed once or twice with other games. No hardware or software changes have been made, the case is clean and well ventilated and tempertures appear are normal. I have had to change my powersupply before but this is a relavitley new one. I am by no means an expert so if you need more information please tell me what you need. Any aid would be great, this is driving me mad.

My Specs are:
Windows 10 Pro
ST1000DM003-1ER162 ATA Device (Hard drive)
Radeon RX480 Graphics (8GB) 
AMD FX-6300 Six-core processor
Ballistix Sport 8GB (2x4GB) 1600MHz CL9 DDR3
Gigabyte GA-970A-UD3P AMD Socket AM3+ Motherboard
EVGA 600w 80 plus powersupply

This is the first event, most other events are very similar:

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 04/11/2017 21:48:43
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: Elliotts-pc
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" ></Provider>
<EventID>41</EventID>
<Version>5</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2017-11-04T21:48:43.332045800Z" ></TimeCreated>
<EventRecordID>8764</EventRecordID>
<Correlation ></Correlation>
<Execution ProcessID="4" ThreadID="8" ></Execution>
<Channel>System</Channel>
<Computer>Elliotts-pc</Computer>
<Security UserID="S-1-5-18" ></Security>
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">12</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">true</Data>
</EventData>
</Event>


<Data Name="SystemSleepTransitionsToOn">0</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">true</Data>
</EventData>
</Event>

 

I had these events today as well:

Description

A problem with your hardware caused Windows to stop working correctly.
 
Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffff8108d22104a0
Parameter 2: fffff800ad2af948
Parameter 3: 0
Parameter 4: 24a4
OS version: 10_0_15063
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.15063.2.0.0.256.48
Locale ID: 2057
 
and
 
Problem signature
Problem Event Name: BlueScreen
Code: 9f
Parameter 1: 3
Parameter 2: ffffe484c1de3750
Parameter 3: fffff800b40548f0
Parameter 4: ffffe484c5da8010
OS version: 10_0_15063
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.15063.2.0.0.256.48
Locale ID: 2057
 

Thank you for any help, I really want this to be fixed and for my PC to be OK again.

Attached Files


Edited by Burns-Help, 19 November 2017 - 09:54 AM.


BC AdBot (Login to Remove)

 


#2 Burns-Help

Burns-Help
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:11:39 PM

Posted 19 November 2017 - 10:04 AM

I downloaded WhoCrashed and it has only shown 3 of the crashes:

 

 

Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 19/11/2017 01:34:48 your computer crashed
crash dump file: C:\WINDOWS\Minidump\111917-32406-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x1641)
Bugcheck code: 0x9F (0x3, 0xFFFFE484C1DE3750, 0xFFFFF800B40548F0, 0xFFFFE484C5DA8010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 19/11/2017 01:34:48 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE484C1DE3750, 0xFFFFF800B40548F0, 0xFFFFE484C5DA8010)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 30/05/2017 02:13:34 your computer crashed
crash dump file: C:\WINDOWS\Minidump\053017-56796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x9F (0x3, 0xFFFFE304D98D5060, 0xFFFFF802820548F0, 0xFFFFE304DA527C30)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


Edited by Burns-Help, 19 November 2017 - 10:04 AM.


#3 Burns-Help

Burns-Help
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:11:39 PM

Posted 19 November 2017 - 11:14 AM

I played some Witcher 3 to try and test the system and monitor the temperatures, here it is:
 
 
CPUID HWMonitor Report
-------------------------------------------------------------------------
 
Binaries
-------------------------------------------------------------------------
 
HWMonitor version 1.3.0.0
 
Monitoring
-------------------------------------------------------------------------
 
Mainboard Model 970A-DS3P (0x00000228 - 0x02439970)
 
LPCIO
-------------------------------------------------------------------------
 
LPCIO Vendor ITE
LPCIO Model IT8728
LPCIO Vendor ID 0x90
LPCIO Chip ID 0x8728
LPCIO Revision ID 0x1
Config Mode I/O address 0x2E
Config Mode LDN 0x4
Config Mode registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 
00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 
10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
20 87 28 01 00 00 00 F3 10 00 00 00 40 80 00 00 00 
30 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
60 02 28 02 30 00 00 00 00 00 00 00 00 00 00 00 00 
70 00 02 00 00 04 04 00 00 00 00 00 00 00 00 00 00 
Register space LPC, base address = 0x0228
 
 
Hardware Monitors
-------------------------------------------------------------------------
 
Hardware monitor ITE IT8728
Voltage 0 0.86 Volts [0x48] (CPU VCORE)
Voltage 1 1.46 Volts [0x7A] (DRAM)
Voltage 2 4.98 Volts [0xA6] (+5V)
Voltage 3 12.10 Volts [0xA8] (+12V)
Voltage 4 1.98 Volts [0xA5] (VIN4)
Voltage 5 1.19 Volts [0x63] (VIN5)
Voltage 6 2.22 Volts [0xB9] (VIN6)
Voltage 7 1.64 Volts [0x89] (VIN7)
Voltage 8 1.63 Volts [0x88] (VBAT)
Temperature 0 30 degC (86 degF) [0x1E] (System)
Temperature 1 51 degC (123 degF) [0x33] (CPU)
Temperature 2 37 degC (98 degF) [0x25] (TMPIN2)
Fan 0 2789 RPM [0xF2] (CPU)
Fan 1 608 RPM [0x457] (FANIN1)
Fan 2 1024 RPM [0x293] (FANIN2)
Fan 4 964 RPM [0x2BC] (FANIN4)
Fan PWM 0 0 pc [0x0] (FANPWM0)
Fan PWM 1 0 pc [0x0] (FANPWM1)
Fan PWM 2 0 pc [0x0] (FANPWM2)
Register space LPC, base address = 0x0228
 
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 
00 1B 10 00 00 FF EF 00 00 00 80 48 05 30 F1 57 93 
10 FF FF FF 76 C7 82 80 82 00 04 02 FF FF FF FF FF 
20 48 7A A6 A8 A5 63 B9 89 88 1E 33 25 B9 00 FF FF 
30 FF 00 FF 00 FF 00 FF 00 FF 00 FF 00 FF 00 FF 00 
40 7F 7F 7F 7F 7F 7F 5F 40 AD 6A D4 00 FF FF FF FF 
50 FF CA 7F 7F 7F 80 00 00 90 00 00 12 65 00 00 00 
60 00 00 00 00 00 00 00 FF 00 14 32 46 20 03 00 FF 
70 00 14 41 60 1C 03 00 FF FF FF FF FF FF FF FF FF 
80 FF FF BC 02 FF FF FF FF 00 00 00 00 00 38 00 4B 
90 FF 00 00 00 FF 00 00 00 42 99 00 00 01 4D F2 25 
A0 EB B2 B2 B2 B2 B2 B2 FF FF FF FF FF FF FF FF FF 
B0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
C0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
 
Hardware monitor AMD ADL
Voltage 0 494825.84 Volts [0x1D7E7180] (VIN0)
Temperature 0 47 degC (116 degF) [0x2F] (TMPIN0)
Fan 0 2310 RPM [0x906] (FANIN0)
Clock Speed 0 805.64 MHz [0x325] (Graphics)
Clock Speed 1 300.00 MHz [0x325] (Memory)
 
 
Processors
-------------------------------------------------------------------------
 
Number of processors 1
Number of threads 6
 
APICs
-------------------------------------------------------------------------
 
Processor 0
-- Core 0
-- Thread 0 0
-- Core 1
-- Thread 0 1
-- Core 2
-- Thread 0 2
-- Core 3
-- Thread 0 3
-- Core 4
-- Thread 0 4
-- Core 5
-- Thread 0 5
 
Timers
-------------------------------------------------------------------------
 
Perf timer 14.318 MHz
Sys timer 1.000 KHz
 
 
Processors Information
-------------------------------------------------------------------------
 
Processor 1 ID = 0
Number of cores 6 (max 6)
Number of threads 6 (max 6)
Name AMD FX-6300
Codename Vishera
Specification AMD FX™-6300 Six-Core Processor             
Package Socket AM3+ (942)
CPUID F.2.0
Extended CPUID 15.2
Core Stepping OR-C0
Technology 32 nm
TDP Limit 95.0 Watts
Core Speed 4118.7 MHz
Multiplier x Bus Speed 20.5 x 200.9 MHz
Rated Bus speed 2410.9 MHz
Stock frequency 3500 MHz
Instructions sets MMX (+), SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, SSE4A, x86-64, AMD-V, AES, AVX, XOP, FMA3, FMA4
L1 Data cache 6 x 16 KBytes, 4-way set associative, 64-byte line size
L1 Instruction cache 3 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 3 x 2048 KBytes, 16-way set associative, 64-byte line size
L3 cache 8 MBytes, 64-way set associative, 64-byte line size
FID/VID Control yes
Min FID 7.0x
# of P-States 7
P-State FID 0x19 - VID 0x0A - IDD 17 (20.50x - 1.425 V)
P-State FID 0x16 - VID 0x0F - IDD 17 (19.00x - 1.362 V)
P-State FID 0x13 - VID 0x17 - IDD 12 (17.50x - 1.262 V)
P-State FID 0xE - VID 0x1E - IDD 9 (15.00x - 1.175 V)
P-State FID 0x9 - VID 0x26 - IDD 7 (12.50x - 1.075 V)
P-State FID 0x4 - VID 0x2D - IDD 6 (10.00x - 0.987 V)
P-State FID 0x10C - VID 0x37 - IDD 4 (7.00x - 0.862 V)
 
PStateReg 0x800001A8-0x00001419
PStateReg 0x800001A8-0x00001E16
PStateReg 0x80000174-0x00002E13
PStateReg 0x8000015E-0x00003C0E
PStateReg 0x8000014A-0x00004C09
PStateReg 0x80000138-0x00005A04
PStateReg 0x80000125-0x00006E4C
PStateReg 0x00000000-0x00000000
 
Package Type 0x1
Model 00
String 1 0x0
String 2 0x0
Page 0x0
Base TDP 13 Watts
Boosted P-States 2
Max non-turbo ratio 17.50x
Max turbo ratio 20.50x
TSC 3515.0 MHz
APERF 4080.0 MHz
MPERF 3509.0 MHz
Attached device PCI device at bus 0, device 24, function 0
100 00000000 00000000 00000000 00000000 
110 00000000 00000000 00000000 00000000 
120 00000000 00000000 00000000 00000000 
130 000000C1 00000000 00000000 00000000 
140 00000000 00000000 00000000 00000000 
150 00073900 00000000 00000000 00000000 
160 00000000 00000000 00000400 0066E066 
170 00000109 00000000 00000000 00000000 
180 00000000 00000000 00000000 00000000 
190 00000000 00000000 00000000 00000000 
1A0 80000003 00000000 00000000 00000000 
1B0 00000000 00000000 00000000 00000000 
1C0 00000000 00000000 00000000 00000000 
1D0 00000000 00000000 00000000 0000003E 
1E0 00000000 00000000 00000000 00000000 
1F0 00000000 00000000 00000000 00000000 
 
Attached device PCI device at bus 0, device 24, function 1
100 00000000 00000000 00000000 00000000 
110 00000000 00000000 00000000 00000000 
120 00000000 00000047 00000000 00000000 
130 00000000 00000000 00000000 00000000 
140 00000000 00000000 00000000 00000000 
150 00000000 00000000 00000000 00000000 
160 00000000 00000000 00000000 00000000 
170 00000000 00000000 00000000 00000000 
180 00000000 00000000 00000000 00000000 
190 00000000 00000000 00000000 00000000 
1A0 00000000 00000000 00000000 00000000 
1B0 00000000 00000000 00000000 00000000 
1C0 00000000 00000000 00000000 00000000 
1D0 00000000 00000000 00000000 00000000 
1E0 00000000 00000000 00000000 00000000 
1F0 00000000 00000000 00000000 00000000 
 
Attached device PCI device at bus 0, device 24, function 2
100 00000000 00003E51 00000000 00000000 
110 000005C4 00000000 044CA424 0CE00F41 
120 00401C38 00000000 00000000 00000000 
130 01400003 07140804 18140040 0270C000 
140 00000000 00000000 00000001 00000109 
150 00000000 00000000 00000000 00000000 
160 00000000 00F83EE0 00000000 00000000 
170 00000000 00000000 00020000 18640038 
180 00000070 00800004 33000000 00020000 
190 0B010000 0F580892 8D0F4007 00000000 
1A0 031D0200 00000000 00000000 00000000 
1B0 0FC39001 480F7D26 00000000 00000000 
1C0 00000000 00000000 00000000 00000000 
1D0 00000000 00000000 00000000 00000000 
1E0 00000000 00000000 00000000 00000000 
1F0 00000000 00000000 00000000 00000000 
 
Attached device PCI device at bus 0, device 24, function 3
100 00000000 00000000 00000000 00000000 
110 00000000 00000000 00000000 00000000 
120 00000000 00000000 00000000 00000000 
130 00000000 00000000 00000000 00000000 
140 00A11755 00000055 0000C12A 00000000 
150 00000000 00000000 00000000 00000000 
160 C00A0FFF 00000000 C00A0FFF 00000000 
170 C00A0FFF 00000000 00000000 00000009 
180 017003E3 00000000 08000210 00000008 
190 00000000 00000000 00780400 00000000 
1A0 00034144 00000000 00000000 00000000 
1B0 12088721 00000000 00141000 00000000 
1C0 00000000 0003CCCC 00000000 00000100 
1D0 00000000 00000000 002B170F 00000000 
1E0 00000000 80001387 00000000 00000000 
1F0 00080000 00000000 00000000 004C074F 
 
Attached device PCI device at bus 0, device 24, function 4
100 00000000 00000321 00000000 0085014C 
110 000FE001 00000000 0107000B 00000000 
120 00000000 00000000 00000500 00000000 
130 00000000 00000000 00000000 00000000 
140 1159C931 0000034D 23A2DC39 0000079D 
150 00000B68 00B4B490 00000000 00000089 
160 00600F20 00000003 00000000 00000257 
170 00000000 00000000 00000000 00000000 
180 E000530F 00001004 00000000 00000000 
190 00000000 00000000 00000000 00000000 
1A0 0000000A 00000000 00000000 00000000 
1B0 00000000 00000000 00350182 00000000 
1C0 000000EC 00000110 00000000 00000090 
1D0 00080000 0000FFFF 00000000 00000000 
1E0 0B501419 0B501E16 0AE82E13 0ABC3C0E 
1F0 0A944C09 0A705A04 0A4A6E4C 00000000 
 
Attached device PCI device at bus 0, device 24, function 5
100 00000000 00000000 00000000 00000000 
110 00000000 00000000 00000000 00000000 
120 00001111 80000000 00009137 00000000 
130 00000000 00000000 00000000 00000000 
140 00000000 00000000 00000000 00000000 
150 00000000 00000000 00000000 00000000 
160 0000780D 00000000 00000000 00000000 
170 00000608 0001E030 00000000 00000000 
180 00000000 00000000 00000000 00000000 
190 2233457A 0000000B 00202020 00000000 
1A0 00000000 00000000 00000000 00000000 
1B0 00000000 00000000 00000000 00000000 
1C0 00000000 00000000 00000000 00000000 
1D0 00000000 00000000 00000000 00000000 
1E0 00000000 00000000 00000000 00000000 
1F0 00000000 00000000 00000000 00000000 
 
 
Temperature 0 38 degC (100 degF) (Package)
Power 0 40.60 W (Package)
Clock Speed 0 4118.69 MHz (Core #0)
Clock Speed 1 3817.32 MHz (Core #1)
Clock Speed 2 3515.95 MHz (Core #2)
Clock Speed 3 3515.95 MHz (Core #3)
Clock Speed 4 3515.95 MHz (Core #4)
Clock Speed 5 3515.95 MHz (Core #5)
 
 
Thread dumps
-------------------------------------------------------------------------
 
CPU Thread 0
APIC ID 0
Topology Processor ID 0, Core ID 0, Thread ID 0
Type 02040008h
Max CPUID level 0000000Dh
Max CPUID ext. level 8000001Eh
Cache descriptor Level 1, D, 16 KB, 1 thread(s)
Cache descriptor Level 1, I, 64 KB, 2 thread(s)
Cache descriptor Level 2, U, 2 MB, 2 thread(s)
Cache descriptor Level 3, U, 8 MB, 6 thread(s)
 
CPUID
0x00000000 0x0000000D 0x68747541 0x444D4163 0x69746E65
0x00000001 0x00600F20 0x01060800 0x3E98320B 0x178BFBFF
0x00000002 0x00000000 0x00000000 0x00000000 0x00000000
0x00000003 0x00000000 0x00000000 0x00000000 0x00000000
0x00000004 0x00000000 0x00000000 0x00000000 0x00000000
0x00000005 0x00000040 0x00000040 0x00000003 0x00000000
0x00000006 0x00000000 0x00000000 0x00000001 0x00000000
0x00000007 0x00000000 0x00000008 0x00000000 0x00000000
0x00000008 0x00000000 0x00000000 0x00000000 0x00000000
0x00000009 0x00000000 0x00000000 0x00000000 0x00000000
0x0000000A 0x00000000 0x00000000 0x00000000 0x00000000
0x0000000B 0x00000000 0x00000000 0x00000000 0x00000000
0x0000000C 0x00000000 0x00000000 0x00000000 0x00000000
0x0000000D 0x00000007 0x00000340 0x000003C0 0x40000000
0x80000000 0x8000001E 0x68747541 0x444D4163 0x69746E65
0x80000001 0x00600F20 0x10000000 0x01EBBFFF 0x2FD3FBFF
0x80000002 0x20444D41 0x74285846 0x362D296D 0x20303033
0x80000003 0x2D786953 0x65726F43 0x6F725020 0x73736563
0x80000004 0x2020726F 0x20202020 0x20202020 0x00202020
0x80000005 0xFF40FF18 0xFF40FF30 0x10040140 0x40020140
0x80000006 0x64006400 0x64004200 0x08008140 0x0040C140
0x80000007 0x00000000 0x00000000 0x00000000 0x000007D9
0x80000008 0x00003030 0x00000000 0x00004005 0x00000000
0x80000009 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000A 0x00000001 0x00010000 0x00000000 0x00001CFF
0x8000000B 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000C 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000D 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000E 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000F 0x00000000 0x00000000 0x00000000 0x00000000
0x80000010 0x00000000 0x00000000 0x00000000 0x00000000
0x80000011 0x00000000 0x00000000 0x00000000 0x00000000
0x80000012 0x00000000 0x00000000 0x00000000 0x00000000
0x80000013 0x00000000 0x00000000 0x00000000 0x00000000
0x80000014 0x00000000 0x00000000 0x00000000 0x00000000
0x80000015 0x00000000 0x00000000 0x00000000 0x00000000
0x80000016 0x00000000 0x00000000 0x00000000 0x00000000
0x80000017 0x00000000 0x00000000 0x00000000 0x00000000
0x80000018 0x00000000 0x00000000 0x00000000 0x00000000
0x80000019 0xF040F018 0x64006400 0x00000000 0x00000000
0x8000001A 0x00000003 0x00000000 0x00000000 0x00000000
0x8000001B 0x000000FF 0x00000000 0x00000000 0x00000000
0x8000001C 0x00000000 0x80032013 0x00010200 0x8000000F
0x8000001D 0x00000121 0x00C0003F 0x0000003F 0x00000000
0x8000001D 0x00004122 0x0040003F 0x000001FF 0x00000000
0x8000001D 0x00004143 0x03C0003F 0x000007FF 0x00000001
0x8000001D 0x00014163 0x0FC0003F 0x000007FF 0x00000001
0x8000001E 0x00000011 0x00000100 0x00000000 0x00000000
 
MSR 0x0000001B 0x00000000 0xFEE00900
MSR 0xC0010114 0x00000000 0x00000008
MSR 0xC0010061 0x00000000 0x00000040
MSR 0xC0010062 0x00000000 0x00000000
MSR 0xC0010063 0x00000000 0x00000000
MSR 0xC0010064 0x800001A8 0x00001419
MSR 0xC0010065 0x800001A8 0x00001E16
MSR 0xC0010066 0x80000174 0x00002E13
MSR 0xC0010067 0x8000015E 0x00003C0E
MSR 0xC0010068 0x8000014A 0x00004C09
MSR 0xC0010058 0x00000000 0xE0000021
MSR 0xC0010015 0x00000000 0x09001011
MSR 0xC001001F 0x00404000 0x00810008
MSR 0xC0010071 0x01000006 0x3C011E16
MSR 0xC0010070 0x00000000 0x3C011E16
 
 
Storage
-------------------------------------------------------------------------
 
Drive 0
Device Path \\?\ide#diskst1000dm003-1er162______________________cc43____#5&38210314&0&1.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
Type Fixed
Name ST1000DM003-1ER162
Capacity 931.5 GB
SMART Support Yes
Volume d:\, 0.3 GBytes (14.1 percent available)
Volume f:\, 930.7 GBytes (100.0 percent available)
 
Drive 1
Device Path \\?\ide#diskwdc_wd10ezex-08wn4a0____________________01.01a01#5&f3fe9b2&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
Type Fixed
Name WDC WD10EZEX-08WN4A0
Capacity 931.5 GB
SMART Support Yes
Volume c:\, 930.4 GBytes (33.4 percent available)
Volume e:\, 0.3 GBytes (21.3 percent available)
 
USB Devices
-------------------------------------------------------------------------
 
USB Device Generic USB Hub, class=0x09, subclass=0x00, vendor=0x2109, product=0x3431
USB Device Xbox 360 Wireless Receiver for Windows, class=0xFF, subclass=0xFF, vendor=0x045E, product=0x0291
USB Device USB Composite Device, class=0x00, subclass=0x00, vendor=0x1038, product=0x1702
USB Device Generic Bluetooth Radio, class=0xE0, subclass=0x01, vendor=0x0A12, product=0x0001
USB Device 802.11n USB Wireless LAN Card, class=0x00, subclass=0x00, vendor=0x148F, product=0x5572
USB Device USB Composite Device, class=0x00, subclass=0x00, vendor=0x1017, product=0x0002
 
Graphic APIs
-------------------------------------------------------------------------
 
API ATI I/O
API ADL SDK
 
Display Adapters
-------------------------------------------------------------------------
 
Display adapter 0
Name Radeon ™ RX 480 Graphics
Board Manufacturer ASUSTeK Computer Inc.
Codename Polaris
Technology 14 nm
Memory size 8 GB
Memory type GDDR5
PCI device bus 1 (0x1), device 0 (0x0), function 0 (0x0)
Vendor ID 0x1002 (0x1043)
Model ID 0x67DF (0x0505)
Performance Level 0
Performance Level 1
 
 
Monitor 0
Model S220HQL ()
ID ACR0347
Serial LYKEE0018501
Manufacturing Date Week 25, Year 2014
Size 21.7 inches
Max Resolution 1920 x 1080 @ 60 Hz
Horizontal Freq. Range 31-83 kHz
Vertical Freq. Range 56-76 Hz
Max Pixel Clock 170 MHz
Gamma Factor 2.2


#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:39 PM

Posted 20 November 2017 - 08:42 PM

The Reliability Monitor screenshot shows hardware errors.
Please start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

Please perform ALL of the tests and let us know the results.

 

The Event ID 41 error is simply Windows saying it doesn't know why it was unexpectedly shutdown.

More info on that here:  http://support.microsoft.com/kb/2028504

 

WhoCrashed shows generic info that's not of much help (in this case).

Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR, .7z or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.


 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#5 Burns-Help

Burns-Help
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:11:39 PM

Posted 21 November 2017 - 06:53 PM

Memtest86 - 3 passes and no errors 

hard drive was clean 

no malware 

 

GPU stress test FURMARK - maxed out at 68 C 

CPU Prime95 test - Could only do 2 hours due to not wanting to leave it unattended whilst I slept. No errors reported and temperature stayed at 52C with a peak of 53C

 

I will try and continue testing tomorrow, sadly I dont have much free time to sort this out at the moment. 



#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:39 PM

Posted 22 November 2017 - 06:33 AM

What test did you use on the hard drive?

FYI - SMART is not a diagnostic.  It is a predictive tool and I find that it's frequently inaccurate.

If you have an HDD, then use the Seagate Seatools long/extended test
If you have an SSD, the only reliable test is to try another drive (either SSD or HDD).

I usually suggest a clean install before trying another hard drive - but if you have a drive available it'd be easier just to try the other drive.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#7 Burns-Help

Burns-Help
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:11:39 PM

Posted 22 November 2017 - 01:28 PM

I have 2 HDD's installed though only one is in use. They both passed SMART but as you said it is only predictive and so I am running a long generic test currently. Thank you for helping me, just wanted to ask that if my PC does crash again should I wait until it can compile a report or turn it off ASAP? 



#8 Burns-Help

Burns-Help
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:11:39 PM

Posted 22 November 2017 - 04:44 PM

My HDD passed the long generic test, no issues 



#9 Burns-Help

Burns-Help
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:11:39 PM

Posted 22 November 2017 - 07:41 PM

Ok so I may have worked out some more information. I played some more rocket league to see if the PC could log an specific error when it crashed, however after waiting for a few minutes after it froze I could use CTRL ALT DEL to get a different screen up. Once I tried to open Task Manager the screen turned white and I could not see anything on my desktop. I then used the log off feature on CTRL ALT DEl and relogged in and my PC seems normal. 

 

I think I need to monitor my temp whilst it freezes (but the stress test was fine)  and potentially look at some drivers issues.

 

Looking on the event viewer I found some errors that took place around the time of the freeze, though they are repeated a lot over the event viewer:

 

Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          23/11/2017 00:17:26
Event ID:      10016
Task Category: None
Level:         Error
Keywords:      Classic
User:          SYSTEM
Computer:      Elliotts-pc
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Event Xml:
  <System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="0">10016</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2017-11-23T00:17:26.626795100Z" />
    <EventRecordID>10825</EventRecordID>
    <Correlation />
    <Execution ProcessID="76" ThreadID="1328" />
    <Channel>System</Channel>
    <Computer>Elliotts-pc</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="param1">application-specific</Data>
    <Data Name="param2">Local</Data>
    <Data Name="param3">Activation</Data>
    <Data Name="param4">{D63B10C5-BB46-4990-A94F-E40B9D520160}</Data>
    <Data Name="param5">{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}</Data>
    <Data Name="param6">NT AUTHORITY</Data>
    <Data Name="param7">SYSTEM</Data>
    <Data Name="param8">S-1-5-18</Data>
    <Data Name="param9">LocalHost (Using LRPC)</Data>
    <Data Name="param10">Unavailable</Data>
    <Data Name="param11">Unavailable</Data>
  </EventData>
</Event>
 
And
 
Log Name:      Microsoft-Windows-AppModel-Runtime/Admin
Source:        Microsoft-Windows-AppModel-Runtime
Date:          23/11/2017 00:20:56
Event ID:      37
Task Category: None
Level:         Error
Keywords:      AppContainer
User:          SYSTEM
Computer:      Elliotts-pc
Description:
App Container profile failed with error 0x800700B7 because it was unable to register the AppContainer SID.
Event Xml:
  <System>
    <Provider Name="Microsoft-Windows-AppModel-Runtime" Guid="{F1EF270A-0D32-4352-BA52-DBAB41E1D859}" />
    <EventID>37</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000002</Keywords>
    <TimeCreated SystemTime="2017-11-23T00:20:56.648477700Z" />
    <EventRecordID>2172</EventRecordID>
    <Correlation ActivityID="{A97ED574-613F-0001-E373-87A93F61D301}" />
    <Execution ProcessID="11336" ThreadID="5748" />
    <Channel>Microsoft-Windows-AppModel-Runtime/Admin</Channel>
    <Computer>Elliotts-pc</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="ErrorCode">2147942583</Data>
  </EventData>
</Event>


#10 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:39 PM

Posted 23 November 2017 - 07:31 AM

Usually I don't bother trying to fix DCOM issues unless they are associated repeatedly with the crashes.  That being said, here's what I suggest:

 

Please attempt to fix your DCOM errors by doing this:

Go to Start, and then to Run (or the Win and R keys)
Type in "dcomcnfg" (without the quotes) and press Enter

In the Component Services window that opens, go to the left hand pane and double click on:
- Component Services, then on
- Computers, then on
- My Computer, then on
- DCOM Config
If it asks you to register any of the components, click Yes
This may happen several times if there are several unregistered components

Once you're finished, close the window and reboot the computer.
Check to see if the problems are fixed.
NOTE:  This is a generic "fix" for DCOM errors.  If it does not fix your problems, please post back.

 

The AppModel stuff normally isn't associated with restarts so I tend to ignore it.  I have no suggestions on how to repair this error, and would suggest posting over in the Windows 10 forum for assistance with it if you're concerned.

 

If the second hard drive is connected, then you'll have to run the diagnostics on it also

i suggest running Speedfan to keep track of your temps.

 Also, monitor your system's temperatures with this free tool: 

SpeedFan v. 4.5.1 and later (free from here:  http://www.almico.com/sfdownload.php ) can log temperatures in a CSV file:

To make it work you have to do BOTH of the below:  FYI - I have seen a few users that had problems with this procedure.  I'd suggest checking to make sure that the log feature is working for you.

1. Enable logging in general: Configure...Log...check "Enabled" then click on OK to save.

2. Enable logging for specific checks: Configure...Temperatures..left click on each sensor, then click on "Logged" at the bottom of the Window (for our purposes we want them all) then once you've selected "Logged" for all sensors, then click on OK to save.

The log will be located at C:\Program Files (x86)\SpeedFan

Naming: log files are named SFLogYYYYMMDD.csv, where YYYY is the year (four digits), MM is the month (2 digits, zero padded) and DD is the day (2 digits, zero padded). If a file already exists by that name, the file that already exists is renamed according to the following naming scheme: SFLogYYYYMMDD-CCCC.csv, where CCCC is a increasing number. The new file is then created with the standard file name scheme.

Notes: whenever you change the options related with logging, SpeedFan starts a new log file.

NOTE:You may want to turn logging off when we're done - as I don't know it's impact on performance or on the system.

 

Most likely Prime95 test was OK - but you may want to run it longer with the temp monitor being on.

 

Beyond that, here's a couple of things to try:

Wait until the system crashes, unplug it from the wall and open up the case.

CAUTION!!!  YOU CAN GET 2nd or 3rd DEGREE BURNS DOING THIS!!!
CAREFULLY feel for HEAT inside the case - get close but DO NOT TOUCH ANYTHING!!!
If it's excessively hot, you'll feel it well before you get close to it.

100ºC is the temp of boiling water - and that's awfully hot!
I got 2nd degree burns doing this several years ago (I didn't know it was a temp problem when I started messing around inside the case).

 

You can also try a clean install of Windows to rule out software issues:

A clean install is:
- Windows is installed to a freshly partitioned hard drive with legitimate installation media (W10:  https://www.microsoft.com/en-us/software-download/windows10 ).
- The installation media is only a copy of Windows, not the OEM recovery disks that you can make on some systems.
- Windows is fully updated after it's installed.  That's ALL updates - none excepted.
- NO 3rd party software is installed.
- There are no errors in Device Manager (if you find any, post back for suggestions).

This will wipe everything off of the computer, so it's advisable to backup your stuff first.
Also, it will wipe out all the special software that the OEM added to the system, so if you rely on any of that - let us know what it is so we can figure out a way to save/download it (the easiest way is to create/obtain the OEM;s recovery media)

If unable to find recovery media that has the software (or if you suspect that this is a hardware problem), you can make an image of your system that'll preserve everything in the state that it was in when you made the image.
One drawback to this is that you're making an image of a malfunctioning system - so, if there are errors in the system software, you'll have a nice copy of them :(
Another drawback is that the image of the system will be very large - so you'll most likely need a large external drive to store it on.
But, this will allow you to save everything on the hard drive (although you'll need an image viewer to get things out of the image).
The point here is that, if it's a hardware problem, then you can restore the system to the point it was when you made the image - after you repair the hardware problem.
You can obtain more info on imaging in the Backup/Imaging/DiskMgmt forums located here:  http://www.bleepingcomputer.com/forums/f/238/backup-imaging-and-disk-management-software/

The point of doing this (the clean install) is to:
- rule out Windows as a problem (if the problem continues, it's not a Windows problem as you completely replaced Windows
- rule out 3rd party software (if the problem continues, it's not a 3rd party software problem as you didn't install any 3rd party software)
- so, if the problem continues, it must be a hardware problem.

OTOH, if the problem stops, then it was either a Windows or 3rd party software problem.  If the problem doesn't come back, then you've fixed it.  Then all that remains is setting the computer back up the way that you'd like it and importing your data from the backup you made.

 

Beyond that (or in combination with it) you can also try this procedure to isolate the bad component:  http://www.carrona.org/strpdown.html


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users