BSOD 166 total send help (Should I get new ram?)

Niall_2

Commendable
Jan 26, 2017
16
0
1,510
I have 166 BSOD on record on my computer and i am getting really fed up i have made maybe 6 forum threads and everyone said replace my PSU so i did but the error still persists my friends think my ram sticks are the problem so i did a diagnostics on the ram sticks using Microsoft's software for it but i got this when i booted up my pc again i got this

Log Name: System
Source: Microsoft-Windows-MemoryDiagnostics-Results
Date: 8/9/2017 8:59:57 PM
Event ID: 1201
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: Niall
Description:
The Windows Memory Diagnostic tested the computer's memory and detected no errors
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-MemoryDiagnostics-Results" Guid="{5F92BC59-248F-4111-86A9-E393E12C6139}" />
<EventID>1201</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2017-08-09T19:59:57.993176900Z" />
<EventRecordID>36766</EventRecordID>
<Correlation />
<Execution ProcessID="5548" ThreadID="5552" />
<Channel>System</Channel>
<Computer>Niall</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<Results xmlns="http://manifests.microsoft.com/win/2005/08/windows/Reliability/Postboot/Events">
<CompletionType>Pass</CompletionType>
</Results>
</UserData>
</Event>

It was working fine for 2 days with the new PSU but started BSOD again when i played games my spec is:

i7 4770 (Not replaced since i built the PC)
Nvidia GTX 1070 (before i had a 750 ti and before that i had intergrated graphics)
2 HDD (added one, one is still there from PC being built)
Asrock H97M Pro4 (Hasnt been replaced)
EVGA 750W Gold PSU (Been replaced twice)

I have really begin to just stop buying stuff to try and fix it as it is not helping the BSOD error from today was this:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 8/9/2017 8:34:42 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: Niall
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>4</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2017-08-09T19:34:42.005255700Z" />
<EventRecordID>36660</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Niall</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">26</Data>
<Data Name="BugcheckParameter1">0x5003</Data>
<Data Name="BugcheckParameter2">0xffffd50010804310</Data>
<Data Name="BugcheckParameter3">0x12065d</Data>
<Data Name="BugcheckParameter4">0x1180220340cba</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>
</EventData>
</Event>

The first BSOD i got was this:

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 11/4/2016 2:53:16 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: Niall
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>4</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2016-11-04T14:53:16.643114400Z" />
<EventRecordID>492</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Niall</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>
</EventData>
</Event>
 
Solution
try making a bootable USB using memtest86 - check 1 stick at a time, and errors are too many as perfect score is 0. Remove/replace any sticks that get errors

Are you on win 10?

event 41 is a reaction, not a cause. Its created by windows on a restart that wasn't expected. It says just as much in the descriptions above - The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a...

Colif

Win 11 Master
Moderator
try making a bootable USB using memtest86 - check 1 stick at a time, and errors are too many as perfect score is 0. Remove/replace any sticks that get errors

Are you on win 10?

event 41 is a reaction, not a cause. Its created by windows on a restart that wasn't expected. It says just as much in the descriptions above - The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and

someone with right software to read them will decode the files and help us fix it :)
 
Solution