Solved BSOD fresh w7 install custom build, error f4 and 03, event id 41...

[jester88]

I recently built a new computer and have been having an issue with a recurring BSOD.

What I have tried so far to troubleshoot the issue:

Reseated all connections in the computer (unplugged and plugged back in).

chkdsk: pass

WD lifeguard diagnostics: pass on both quick and long scan

memtest86 - 8 iterations: pass

driver updates; chipset, video, bios, network controller

Replaced the 600w psu with a 700w after reading that the 390 is recommended to have at least a 650w

prime95: piece of cake

furmark: no problems

Fresh install of windows 7 - I reformatted the drive and reinstalled.

The crashes seem to happen at random times. Sometimes when I am playing a game, sometimes when the computer is idle, but not asleep, sometimes when I am browsing the web. I can't seem to pin down any particular activity that causes the crashes. It sort of seems to happen most often when I am playing ARK survival evolved, but I think that's because I am usually playing that when I am on the computer. Overall, the crashes seem to happen at fairly regular intervals (every hour or two), regardless of what I am doing.

Anyway, I am at a loss as to what to try next. I've spent hours scouring the net and can't seem to find anything to help. I will be running memtest86+ overnight tonight to see if that comes up with anything that memtest missed.

My BSOD report is attached and the following is the xml report from event viewer:

- <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>2</Version>

<Level>1</Level>

<Task>63</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000002</Keywords>

<TimeCreated SystemTime="2015-07-24T01:05:49.680807300Z" />

<EventRecordID>4608</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="8" />

<Channel>System</Channel>

<Computer>Josh-PC</Computer>

<Security UserID="S-1-5-18" />

</System>


- <EventData>
<Data Name="BugcheckCode">244</Data>

<Data Name="BugcheckParameter1">0x3</Data>

<Data Name="BugcheckParameter2">0xfffffa8008168060</Data>

<Data Name="BugcheckParameter3">0xfffffa8008168340</Data>

<Data Name="BugcheckParameter4">0xfffff800037d5940</Data>

<Data Name="SleepInProgress">false</Data>

<Data Name="PowerButtonTimestamp">0</Data>

</EventData>


</Event>



Thanks in advance!

 

[jester88]

I just noticed that this following bit always seems to be in close proximity to event 41.

Event[2178]:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2015-07-22T22:20:16.912
Event ID: 89
Task: N/A
Level: Information
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: Josh-PC
Description:
ACPI thermal zone ACPI\ThermalZone\TZ00 has been enumerated.
_PSV = 0K
_TC1 = 0
_TC2 = 0
_TSP = 0ms
_AC0 = 353K
_AC1 = 328K
_AC2 = 323K
_AC3 = 318K
_AC4 = 313K
_AC5 = 0K
_AC6 = 0K
_AC7 = 0K
_AC8 = 0K
_AC9 = 0K
_CRT = 378K
_HOT = 0K
_PSL - see event data.

The system does not seem to be overheating, the case is cool to the touch and speccy reports the current temps as:

CPU: 32C
MB: 34C
GCard: 39C

I also carefully watched the temps while running furmark and prime and they stayed within a safe range and well under the _CRT of 378K, which is apparently the temperature at which the system will shutdown (according to https://msdn.microsoft.com/en-us/library/Dn495657%28v=VS.85%29.aspx).

I'm thinking that there may be some issue with the motherboard and windows both trying to control the temperature. I'm kind of grasping at straws here...

Also, nothing is overclocked. I am using the fan that was included with the i7, as well as two case fans, the psu fan, and the two fans on the 390. There seems to be plenty of airflow and the only thing that goes over 50C while under heavy load is the graphics card, which is designed to go up to ~60C before the fans activate.

 

[jester88]

Okay, something new - I went into the BIOS and noticed that enhanced turbo boost was enabled by default, so I disabled that. Since then I have not had a BSOD, although it hasn't been very long. However, I just had a new error pop up, while I was playing ARK. Here is the event view information:

Display driver amdkmdap stopped responding and has successfully recovered.

XML Detail:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Display" />

<EventID Qualifiers="0">4101</EventID>

<Level>3</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2015-07-24T03:23:26.000000000Z" />

<EventRecordID>4895</EventRecordID>

<Channel>System</Channel>

<Computer>Josh-PC</Computer>

<Security />

</System>


- <EventData>
<Data>amdkmdap</Data>

<Data />

</EventData>


</Event>

Maybe this would have previously been a BSOD? I guess this could be progress. I could try reinstalling the display drivers again, but I've done that already, by doing an express uninstall of all AMD software from windows remove programs and then using driver sweeper.

 

[jester88]

Just had another BSOD while I was browsing the web looking for info on BSODs lol. Dump file is attached.

 

[jester88]

Just had another crash...This one was different. A message popped up saying that explorer.exe wasn't able to start with a 0003x error code. The computer then reset, no BSOD.

Details of the event:

- System

- Provider


[ Name] Microsoft-Windows-Kernel-Power


[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}



EventID 41


Version 2


Level 1


Task 63


Opcode 0


Keywords 0x8000000000000002

- TimeCreated


[ SystemTime] 2015-07-24T04:34:51.977207800Z



EventRecordID 5173


Correlation

- Execution


[ ProcessID] 4


[ ThreadID] 8



Channel System


Computer Josh-PC

- Security


[ UserID] S-1-5-18

- EventData

BugcheckCode 0

BugcheckParameter1 0x0

BugcheckParameter2 0x0

BugcheckParameter3 0x0

BugcheckParameter4 0x0

SleepInProgress false

PowerButtonTimestamp 0

This one is a bit different. The others had bugcheck codes and parameters. I'm going to go ahead and start memtest86+ and let it run overnight. Wish me luck...

 

[Laith]

Hiya and welcome to SevenForums! Your PC dosen't want to let you search for info about the BSOD because it wants it to keep BSODing lol. Anyways

BugCheck F4, {3, fffffa8008168060, fffffa8008168340, fffff800037d5940}

Probably caused by : csrss.exe

BugCheck F4, {3, fffffa8008df8b30, fffffa8008df8e10, fffff800037de940}

Probably caused by : wininit.exe

Followup: MachineOwner

Hmm, an F4 can mean several things. It could mean a bad HDD/SSD, virus and more. You did the right thing running MemTest86+. I saw memory things in your dump, so to be in the safe side run that for 8 passes. After that has been ran, run SeaTools and Malwarebytes.
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html http://www.sevenforums.com/tutorials/338716-malwarebytes-anti-malware-free.html

 

[jester88]

Okay! Progress has been made, sort of. Memtest86+ reported no errors after 8 passes, so that's good. However, after ending memtest my computer booted to an all black screen with just a mouse cursor. It seemed like windows was running but not explorer or something. I booted into safe mode and did a system restore. This allowed me to get back into windows.

I then downloaded seatools - Dos version, and ran it. The short test passes, but then around 32% of the way through the extended test, a bunch of green text (including a dos prompt) popped up on the screen and the test froze.

So, this makes me think it may be the drive! I'm going to go swap out the hdd today and hope for the best. I'll be sure check back here if that solves the problem.

Ps. I somehow forgot to mention that after the seagate test failed my computer will no longer boot to windows. I cant even get into safe mode, and all startup repair and restore options have failed. I do have my win7 installation cd that i could n possibly use for repairs, but I feel like my time would be better spent returning my hdd for a new one. Luckily i bought it locally and am still within the return period.

 

[Laith]

That's good to hear. I'm certain that the drive is failing. Also the green text is probably reporting that it couldn't continue the test because the disc is corrupting very heavily.

 

[jester88]

Well, so far so good! At this point I have been up and running for longer than ever before. If everything stays stable for the next 24hrs or so I will be back to mark this as solved!

 

[Laith]

No problem! It's my duty to help.

 

[jester88]

Still no crashes since I installed the new hard drive. I'm marking this as solved. Thanks again!

 

[Laith]

No problem! It's my duty to help!