Help with Crashes Kernel Power

[timwheeler92684]

I recently had to RMA my motherboard it was an MSI 970 Gaming I got a temp board that is ASRock 970A-G/3.1. After rebuilding the components I start to get crashes now for some reason I only have three dump files but I have crashed more than 10 times in the past two days please help me with my crashes I am not even sure which way to turn.
Crash 1
Crash 2
Crash 3
Everything I have read up to this point has pointed me towards bad ram but nothing has been specific to me so I am hoping to get a full resolution to this topic. I have redone all drivers I have triple checked clock settings and made sure I stock settings thro the CPU MEM and GPU
My current build is
AMD FX8350
ASRock 970A-G
Gskill Ares 16 Gig 1600 MHz
2x MSI R7 370 Gaming 4G

This is just another example of my crashes
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 12/16/2017 6:08:41 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: tg4life666
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}" />
<EventID>41</EventID>
<Version>6</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2017-12-16T11:08:41.286026000Z" />
<EventRecordID>2767</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>tg4life666</Computer>
<Security UserID="S-1-5-18" />
</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">0</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">true</Data>
<Data Name="CheckpointStatus">0</Data>
</EventData>
</Event>

 

[scout_03]

use whocrashed to give us a plain text readings of the crash .

 

[timwheeler92684]

ok here it is thanks for the new software I have been looking for a good bug reviewer
Crash dumps are enabled on your computer.

On Sat 12/16/2017 12:01:17 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\121617-12125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8025952B313, 0xFFFFE90E6856E060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sat 12/16/2017 12:01:17 PM 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: 0x3B (0xC0000005, 0xFFFFF8025952B313, 0xFFFFE90E6856E060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sat 12/16/2017 7:37:41 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\121617-12000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF8012DA886C1)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sat 12/16/2017 6:51:30 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\121617-11593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Wed 12/13/2017 10:00:30 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\121417-12671-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR

 

[scout_03]

https://support.microsoft.com/en-us/help/4028391/windows-how-to-fix-error-0xa-irqlnotlessorequal - the other point since you got another maker board did you reinstall the os lead to corrupted readins .

 

[timwheeler92684]

https://support.microsoft.com/en-us/help/4028391/windows-how-to-fix-error-0xa-irqlnotlessorequal - the other point since you got another maker board did you reinstall the os lead to corrupted readins .

ill try that and check back in here to see thanks for the tip i was dreading this but shit happens right

 

[timwheeler92684]

As of this moment I have had zero crashes so far BUT just recently the pc just rebooted itself while I was playing eveonline not sure if that caused it but just thought I would add that note

 

[scout_03]

check temp and voltages using hwinfo .

 

[timwheeler92684]

I just had my first freeze up but had to hard reset to get anywhere and when it reloaded windows it said please wait, working on updates so I am not sure if it was the updates that caused the freeze or if it was the gaming I was doing.

 

[timwheeler92684]

check temp and voltages using hwinfo .

dunno what I'm looking for but here's a screenshot of it

https://imgur.com/a/y38lD

 

[timwheeler92684]

apparently I cannot post pictures yet

 

[scout_03]

what is that radeon 240 we see in the tab under sata 6 with the drive .

 

[timwheeler92684]

what is that radeon 240 we see in the tab under sata 6 with the drive .

that's an R7 Radeon 240gb SSD

 

[timwheeler92684]

Still Freezing up now when it freezes up is when I run 5+ accounts of eve online now before yall laugh my old board could run 9 accounts stable so that's where I get perplexed

 

[scout_03]

you means you run 5 accounts on eve at the same time do you use your system as a boot .

 

[johnbl]

you have a driver that is corrupting kernel memory.
this is indicated in an attempted access of virtual memory address 40
40 is likely to be a header size rather than a virtual memory address. Most likely a driver wrote over another drivers data and caused the other driver to crash.

you would need to run cmd.exe or powershell as an admin then run
verifier.exe /standard /all
then reboot your system and wait for the next bugcheck. The next bugcheck should name the bad driver in the memory dump.
Note: be sure you know how to get into safe mode so you can turn off verifier if the system bugchecks during the boot process.
also not: you have to turn off verifier after you are done testing or your machine will run slowly until you do.
turn off verifier with the command
verifier.exe /reset

 

[timwheeler92684]

you have a driver that is corrupting kernel memory.
this is indicated in an attempted access of virtual memory address 40
40 is likely to be a header size rather than a virtual memory address. Most likely a driver wrote over another drivers data and caused the other driver to crash.

you would need to run cmd.exe or powershell as an admin then run
verifier.exe /standard /all
then reboot your system and wait for the next bugcheck. The next bugcheck should name the bad driver in the memory dump.
Note: be sure you know how to get into safe mode so you can turn off verifier if the system bugchecks during the boot process.
also not: you have to turn off verifier after you are done testing or your machine will run slowly until you do.
turn off verifier with the command
verifier.exe /reset

Reinstalling OS stopped the blue screens as of right this moment I only get complete freezing of the system meaning i have to hard reset and it boots just fine and i go on my merry way

 

[timwheeler92684]

you means you run 5 accounts on eve at the same time do you use your system as a boot .

im not sure what you mean by this? please dumb it down for me

 

[scout_03]

this one here could you explain Still Freezing up now when it freezes up is when I run 5+ accounts of eve online .

 

[timwheeler92684]

the system just freezes mouse doesnt move songs hand fcked up audio remixes and i have to restart the computer to do anything

 

[scout_03]

then strip system to minimal parts and see if boot comes on if one you have one of the parts in that is defective .

 

[timwheeler92684]

Thanks everyone for all your help for some reason it just started to work to the specs that i was using before swapping mobo thank you to scout for the first issue fix for the blue screens a fresh install stopped that so i pick that as the solution thank you all again for the help 😀