[AcEsSalvation]

Had a BSOD at 12:11AM EST and started to gather all the information I could. I don't think this is overclock related (the act of overclocking, not the site... I think this is going to get confusing). The reason being is I've started to attempt to put my computer at sleep at night, but it wakes back up within 15 minutes and I'm not 100% sure why. After it wakes back up, it gets slower. Slower as in, response time, loading time, etc - and it got slower with each sleep cycle. I'm going to attached a lot of information including the information requested in the sticky at the head of this forum. Let me get every thing organized and images/texts with all the information laid out.

Spoiler: System specifications

· Windows 7 64 bit, Home Premium
· 64 bit ^
· Always has been this version of Windows. Tried W10, but that was completely formatted and removed.
· OEM
· Various depending on parts. Oldest would be my H100 at somewhere around 4 years
· Less than 8 months
· On this HDD, W10 then this
· 4690k, 4.4GHz 1.26V
· EVGA GTX 680FTW 4GB
· Gigabyte GA-Z97X-Gaming 5
· Rosewill Capstone 450W

Spoiler: Event Viewer XML data from the restart

-

Code:

- <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="2016-01-12T05:12:22.174831100Z" /> 
  <EventRecordID>245909</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="4" ThreadID="8" /> 
  <Channel>System</Channel> 
  <Computer>Intel</Computer> 
  <Security UserID="S-1-5-18" /> 
  </System>
- <EventData>
  80 
  0xfffffa81151fa1d8 
  0x0 
  0xfffff800035ee46b 
  0x5 
  false 
  0 
  </EventData>
  </Event>

Spoiler: Image of BSOD screen

Currently waiting on the Sysnative BSOD Dump software to finish running and HDTune checking the health of the sectors of my HDDs

SysnativePerfmon.zip 1199k .zip file

HDTune is still running
UPDATE: HDD test came back with perfect health on all sectors of my primary drive
Let me know if you guys need any more information

 

[gopackersjt]

If it's running slower, double check that you don't have two antivirus's kicking in when it starts back up. Also, make sure you don't have a dieing HDD.

 

[AcEsSalvation]

Checking the HDD health right now. Over 50% through the test and all sectors are green so far.

I've only got AVG, which did start spewing out some errors with one of it's parts.

UPDATE: HDD test came back with perfect health on all sectors of my primary drive

 

[gopackersjt]

Try rolling your system back before your most current system update. Maybe one of them didn't install right.

 

[AcEsSalvation]

That would be something like a month or two ago.

UPDATE: Just had yet another crash, only a couple hours after waking up from sleep mode. I've never had any luck with a custom built rig going to sleep, part of why I've just recently started doing this again

 

[Agoriaz]

Rather late to the party here, had any further BSOD's?

My very basic knowledge of debugging points towards a memory failure.

Specifically this googlable problem: nt!MiSectionDelete+3f

The errorcheck returned

Code:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffffa81151fa1d8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800035ee46b, If non-zero, the instruction address which referenced the bad memory
        address.
Arg4: 0000000000000005, (reserved)

-------------------------------------------------------------------

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  DBCTaskman.exe

CURRENT_IRQL:  0

ACESSALVATION_PARSED.txt 32k .txt file


Sleep related problems may be related to your C-states. If you're overclocking that is. There was a pun somewhere in that sentence.