BSOD on windows 8.1 caused by ntoskrnl.exe (Internal_Power_Error)

[KazenoS]

I have suffered from BSOD ever since I installed a SSD after Christmas. After it was installed I did a full reinstall and installed windows 7. After a couple months of crashing I tried reinstalling again and install windows 8.1. This made it so I no longer BSOD but instead the computer freezes and a hard reboot is needed to resume using the computer. The BSOD/freezes mostly occurs when using google chrome but also when playing League of Legends (it haven't while playing any other games)
I am using a 256 GB SSD for windows and frequently played games and a 1 TB HDD for the rest.
Below are one of the dump files
Dump File 032515-11093-01.dmp
Crash Time 25-03-2015 18:03:37
Bug Check String INTERNAL_POWER_ERROR
Bug Check Code 0x000000a0
Parameter 1 00000000`0000010a
Parameter 2 00000000`0000000a
Parameter 3 ffffe001`c7023760
Parameter 4 ffffffff`c0000001
Caused By Driver ntoskrnl.exe
Caused By Address ntoskrnl.exe+1509a0
File Description
Product Name
Company
File Version
Processor x64
Crash Address ntoskrnl.exe+1509a0
Stack Address 1
Stack Address 2
Stack Address 3
Computer Name
Full Path C:\Windows\Minidump\032515-11093-01.dmp
Processors Count 4
Major Version 15
Minor Version 9600
Dump File Size 96.04.00
Dump File Time 25-03-2015 18:14:23

Here is a zip link to the dump files:
https://onedrive.live.com/redir?resid=13658DB7F59932E5!592&authkey=!AGqrPSs26_p8mrE&ithint=file%2czip

Here is the CHKDSK for the HDD and SSD

Spoiler

Chkdsk was executed in read/write mode.
Checking file system on E:
The type of the file system is NTFS.
Volume label is HDD.

Stage 1: Examining basic file system structure ...


6912 file records processed. File verification completed.


79 large file records processed.

0 bad file records processed.
Stage 2: Examining file name linkage ...


9240 index entries processed. Index verification completed.


0 unindexed files scanned.

0 unindexed files recovered.
Stage 3: Examining security descriptors ...
Cleaning up 15 unused index entries from index $SII of file 0x9.
Cleaning up 15 unused index entries from index $SDH of file 0x9.
Cleaning up 15 unused security descriptors.
Security descriptor verification completed.


1165 data files processed. CHKDSK is verifying Usn Journal...


8271136 USN bytes processed. Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...


6896 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...


235446126 free clusters processed. Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

976759807 KB total disk space.
34862488 KB in 5249 files.
1752 KB in 1166 indexes.
0 KB in bad sectors.
111059 KB in use by the system.
65536 KB occupied by the log file.
941784508 KB available on disk.

4096 bytes in each allocation unit.
244189951 total allocation units on disk.
235446127 allocation units available on disk.

Here is the CHKDSK for the SSD
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
253184 file records processed. File verification completed.
7409 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
366446 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered.
Stage 3: Examining security descriptors ...
Cleaning up 117 unused index entries from index $SII of file 0x9.
Cleaning up 117 unused index entries from index $SDH of file 0x9.
Cleaning up 117 unused security descriptors.
Security descriptor verification completed.
56632 data files processed. CHKDSK is verifying Usn Journal...
40442216 USN bytes processed. Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
253168 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...
31064630 free clusters processed. Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

243837951 KB total disk space.
119069896 KB in 160919 files.
139224 KB in 56633 indexes.
0 KB in bad sectors.
370307 KB in use by the system.
65536 KB occupied by the log file.
124258524 KB available on disk.

4096 bytes in each allocation unit.
60959487 total allocation units on disk.
31064631 allocation units available on disk.

Internal Info:
00 dd 03 00 63 51 03 00 f6 9e 06 00 00 00 00 00 ....cQ..........
aa 9c 00 00 79 00 00 00 00 00 00 00 00 00 00 00 ....y...........

Windows has finished checking your disk.
Please wait while your computer restarts.

 

[johnbl]

I would update the bios, remove the drivers listed below, maybe change they type of sleep/hibernation mode

most likely related to this driver:
wdcsam64.sys Wed Apr 16 01:39:08 2008
Western Digital SCSI Arcitecture Model (SAM) WDM driver
maybe look here for a update if you really want this driver:
http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys

----------
Bug Check 0xA0: INTERNAL_POWER_ERROR
Parameter 1 00000000`0000010a = POP_HIBER_CONTEXT
which means The disk subsystem failed to properly read or write part of the hibernation file.

-I was unable to read your BIOS info in your memory dump.

your machine has two copies of the same overclocking driver (2 versions) running at the same time.
AODDriver2.sys Wed Sep 11 20:36:40 2013
AODDriver2.sys Tue Feb 11 03:06:52 2014

I would remove both. I would also update the BIOS and reconfigure it.
(I am not sure why I could not read its settings info in the debugger)


I would remove this driver:
wdcsam64.sys Wed Apr 16 01:39:08 2008

 

[KazenoS]

I have removed the drivers and done both a memory test and used the diagnostic software for my HDD which both showed nothing wrong but I am still getting the crashes.
I haven't updated by BIOS because I was unsure if it would be smart to update it while running the chance of crashing.

Here is the dumps for recent crashes
https://onedrive.live.com/redir?resid=13658DB7F59932E5!593&authkey=!AK4ZKyON4VNDHdQ&ithint=file%2czip

 

[johnbl]

note: I just looked at all three memory dumps, all have the same problem. All still seem to have 2 copies of the overclocking software installed.
The internal date of the crash was Fri Mar 20 16:56:12.353 2015
am I looking at the correct file? Maybe delete the old files and make sure only the new one is on your server share.

you could also run cmd.exe as an admin then run
powercfg.exe /energy

this will make a report you can then copy to your directory and open and look at to see what it says about your power management system.

you can also change your memory dump type from a mindump to a kernel memory dump and the power managent info will not be stripped out of the memory dump and I can look at it with the windows debugger.

--------------
I would think this is a bug in the BIOS power management. Your fix normally would be to update the BIOS or load a device driver from your motherboard vendor to work around the problem. You could also go to BIOS and turn off some power management options, then go to windows control panel and turn off sleep functions for the failing device. Or turn off all sleep functions (set your system to high performance) and do a full shutdown rather than sleep when you are done using the system.

Note: was unable to read your BIOS info, I guess you might also update your SATA controller software in case the problem is with the disk controller. Also, depending on what disk is not working correctly, it is common to find issues on certain drives that can be resolved by turning off lazy writes for the disk in question. Hard to say without knowing info on the actual drive.
---------------
first bugcheck:

INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 000000000000010a, The disk subsystem failed to properly read or write part of the hibernation
file.
Arg2: 000000000000000a
Arg3: ffffe00035950010, POP_HIBER_CONTEXT
Arg4: ffffffffc0000001, NTSTATUS failure code

0: kd> !error 0xc0000001
Error code: (NTSTATUS) 0xc0000001 (3221225473) - {Operation Failed} The requested operation was unsuccessful.

here is the call stack: you can google this string hal!HaliAcpiSleep and get more info on what is failing.
but something is wrong with the sleep states supported by your machine. Very common for devices that were used on windows 7. and were migrated to windows 8.x. Windows 7 had the low power states turned off by defaults, while windows 8.x turns them on by default. (you can update the BIOS or turn the support off for individual devices or the entire OS)

here is some info: http://arstechnica.com/civis/viewtopic.php?f=8&t=354552


0: kd> kc
Call Site
nt!KeBugCheckEx
nt! ?? ::OKHAJAOM::`string'
nt!PopWriteHiberImage
nt! ?? ::OKHAJAOM::`string'
nt!PopSaveHiberContextWrapper
hal!HaliAcpiSleep
nt!PopHandleNextState
nt!PopIssueNextState
nt!PopInvokeSystemStateHandler
nt!PopEndMirroring
nt!MmDuplicateMemory
nt!PopTransitionToSleep
nt!PspSystemThreadStartup
nt!KiStartSystemThread

 

[KazenoS]

Sorry I uploaded the wrong dump files here are the right ones
https://onedrive.live.com/redir?resid=13658DB7F59932E5!592&authkey=!AGqrPSs26_p8mrE&ithint=file%2czip

I have after these crashes "reinstalled" my BIOS, I was on the current one, and have had a crash but a dump file wasn't made. I will edit in a dump file with updated BIOS when I get one.
I have also used the powercfg.exe /energy command and there seems to be some problems like "USB Suspend:USB Device not Entering Selective Suspend". But I am not sure how to properly analyse it so I am including it here:

Not sure how sharing html works so here is both a .zip and a copypasted version
https://onedrive.live.com/redir?resid=13658DB7F59932E5!597&authkey=!AEsvezIWYSUJtqw&ithint=file%2czip

Spoiler

Power Efficiency Diagnostics Report

Computer Name NIELSPC
Scan Time 2015-04-05T15:24:42Z
Scan Duration 60 seconds
System Manufacturer Gigabyte Technology Co., Ltd.
System Product Name GA-970A-D3
BIOS Date 09/03/2013
BIOS Version F12
OS Build 9600
Platform Role PlatformRoleDesktop
Plugged In true
Process Count 70
Thread Count 1165
Report GUID {92a34fed-ac68-48f5-b607-d9fa987943b5}
Analysis Results

Errors

Power Policyower Plan Personality is High Performance (Plugged In)
The current power plan personality is High Performance when the system is plugged in.
Power Policy:Sleep timeout is disabled (Plugged In)
The computer is not configured to automatically sleep after a period of inactivity.
Power Policy:Minimum processor performance state is 100% (Plugged In)
The processor is not configured to automatically reduce power consumption based on activity.
Power PolicyCI Express ASPM is disabled (Plugged In)
The current power policy for PCI Express Active State Power Management (ASPM) is configured to Off.
USB Suspend:USB Device not Entering Selective Suspend
This device did not enter the USB Selective Suspend state. Processor power management may be prevented when this USB device is not in the Selective Suspend state. Note that this issue will not prevent the system from sleeping.
Device Name USB Mass Storage Device
Host Controller ID PCI\VEN_1B6F&DEV_7023
Host Controller Location PCI bus 2, device 0, function 0
Device ID USB\VID_058F&PID_6387
Port Path 2
USB Suspend:USB Device not Entering Selective Suspend
This device did not enter the USB Selective Suspend state. Processor power management may be prevented when this USB device is not in the Selective Suspend state. Note that this issue will not prevent the system from sleeping.
Device Name USB Composite Device
Host Controller ID PCI\VEN_1002&DEV_4397
Host Controller Location PCI bus 0, device 22, function 0
Device ID USB\VID_04B4&PID_0101
Port Path 3
USB Suspend:USB Device not Entering Selective Suspend
This device did not enter the USB Selective Suspend state. Processor power management may be prevented when this USB device is not in the Selective Suspend state. Note that this issue will not prevent the system from sleeping.
Device Name Microsoft Hardware USB Mouse
Host Controller ID PCI\VEN_1002&DEV_4397
Host Controller Location PCI bus 0, device 19, function 0
Device ID USB\VID_045E&PID_0724
Port Path 1
USB Suspend:USB Device not Entering Selective Suspend
This device did not enter the USB Selective Suspend state. Processor power management may be prevented when this USB device is not in the Selective Suspend state. Note that this issue will not prevent the system from sleeping.
Device Name USB Root Hub
Host Controller ID PCI\VEN_1002&DEV_4397
Host Controller Location PCI bus 0, device 22, function 0
Device ID USB\VID_1002&PID_4397
Port Path
USB Suspend:USB Device not Entering Selective Suspend
This device did not enter the USB Selective Suspend state. Processor power management may be prevented when this USB device is not in the Selective Suspend state. Note that this issue will not prevent the system from sleeping.
Device Name USB Root Hub
Host Controller ID PCI\VEN_1002&DEV_4397
Host Controller Location PCI bus 0, device 19, function 0
Device ID USB\VID_1002&PID_4397
Port Path
Warnings

Platform Timer Resolutionlatform Timer Resolution
The default platform timer resolution is 15.6ms (15625000ns) and should be used whenever the system is idle. If the timer resolution is increased, processor power management technologies may not be effective. The timer resolution may be increased due to multimedia playback or graphical animations.
Current Timer Resolution (100ns units) 10000
Maximum Timer Period (100ns units) 156250
Platform Timer Resolution:Outstanding Timer Request
A program or service has requested a timer resolution smaller than the platform maximum timer resolution.
Requested Period 10000
Requesting Process ID 5192
Requesting Process Path \Device\HarddiskVolume2\Program Files (x86)\AVG Web TuneUp\avgcefrend.exe
Power Policyisplay timeout is long (Plugged In)
The display is configured to turn off after longer than 10 minutes.
Timeout (seconds) 7200
Power Policyim timeout is long (Plugged In)
The display is configured to automatically dim after longer than 10 minutes.
Timeout (seconds) 885
CPU Utilizationrocessor utilization is moderate
The average processor utilization during the trace was moderate. The system will consume less power when the average processor utilization is very low. Review processor utilization for individual processes to determine which applications and services contribute the most to total processor utilization.
Average Utilization (%) 2.38
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name CCC.exe
PID 4852
Average Utilization (%) 0.79
Module Average Module Utilization (%)
\Device\HarddiskVolume2\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll 0.21
\Device\HarddiskVolume2\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll 0.11
\SystemRoot\system32\ntoskrnl.exe 0.10
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name svchost.exe
PID 1148
Average Utilization (%) 0.62
Module Average Module Utilization (%)
\SystemRoot\system32\ntoskrnl.exe 0.52
\Device\HarddiskVolume2\Windows\System32\sysmain.dll 0.04
\SystemRoot\System32\Drivers\Ntfs.sys 0.02
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name vprot.exe
PID 4204
Average Utilization (%) 0.28
Module Average Module Utilization (%)
\Device\HarddiskVolume2\Program Files (x86)\AVG Web TuneUp\vprot.exe 0.14
\SystemRoot\system32\ntoskrnl.exe 0.05
\Device\HarddiskVolume2\Windows\SysWOW64\ntdll.dll 0.02
Information

Platform Timer Resolution:Timer Request Stack
The stack of modules responsible for the lowest platform timer setting in this process.
Requested Period 10000
Requesting Process ID 5192
Requesting Process Path \Device\HarddiskVolume2\Program Files (x86)\AVG Web TuneUp\avgcefrend.exe
Calling Module Stack \Device\HarddiskVolume2\Windows\SysWOW64\ntdll.dll
\Device\HarddiskVolume2\Windows\SysWOW64\kernel32.dll
\Device\HarddiskVolume2\Program Files (x86)\AVG Web TuneUp\libcef.dll
\Device\HarddiskVolume2\Windows\SysWOW64\kernel32.dll
Power Policy:Active Power Plan
The current power plan in use
Plan Name Custom
Plan GUID {7f94e5a5-a79a-469e-80e5-bf746d7d87ff}
Power Policyower Plan Personality (Plugged In)
The personality of the current power plan when the system is plugged in.
Personality High Performance
Power Policy:802.11 Radio Power Policy is Maximum Performance (Plugged In)
The current power policy for 802.11-compatible wireless network adapters is not configured to use low-power modes.
Power Policy:Video quality (Plugged In)
Enables Windows Media Player to optimize for quality or power savings when playing video.
Quality Mode Optimize for Video Quality
System Availability Requests:Analysis Success
Analysis was successful. No energy efficiency problems were found. No information was returned.
Battery:Analysis Success
Analysis was successful. No energy efficiency problems were found. No information was returned.
Platform Power Management Capabilities:Supported Sleep States
Sleep states allow the computer to enter low-power modes after a period of inactivity. The S3 sleep state is the default sleep state for Windows platforms. The S3 sleep state consumes only enough power to preserve memory contents and allow the computer to resume working quickly. Very few platforms support the S1 or S2 Sleep states.
S1 Sleep Supported false
S2 Sleep Supported false
S3 Sleep Supported true
S4 Sleep Supported true
Platform Power Management Capabilities:Connected Standby Support
Connected standby allows the computer to enter a low-power mode in which it is always on and connected. If supported, connected standby is used instead of system sleep states.
Connected Standby Supported false
Platform Power Management Capabilitiesrocessor Power Management Capabilities
Effective processor power management enables the computer to automatically balance performance and energy consumption.
Group 0
Index 0
Idle State Count 1
Idle State Type ACPI Idle (C) States
Nominal Frequency (MHz) 3600
Maximum Performance Percentage 100
Lowest Performance Percentage 22
Lowest Throttle Percentage 22
Performance Controls Type ACPI Performance (P) / Throttle (T) States
Platform Power Management Capabilitiesrocessor Power Management Capabilities
Effective processor power management enables the computer to automatically balance performance and energy consumption.
Group 0
Index 1
Idle State Count 1
Idle State Type ACPI Idle (C) States
Nominal Frequency (MHz) 3600
Maximum Performance Percentage 100
Lowest Performance Percentage 22
Lowest Throttle Percentage 22
Performance Controls Type ACPI Performance (P) / Throttle (T) States
Platform Power Management Capabilitiesrocessor Power Management Capabilities
Effective processor power management enables the computer to automatically balance performance and energy consumption.
Group 0
Index 2
Idle State Count 1
Idle State Type ACPI Idle (C) States
Nominal Frequency (MHz) 3600
Maximum Performance Percentage 100
Lowest Performance Percentage 22
Lowest Throttle Percentage 22
Performance Controls Type ACPI Performance (P) / Throttle (T) States
Platform Power Management Capabilitiesrocessor Power Management Capabilities
Effective processor power management enables the computer to automatically balance performance and energy consumption.
Group 0
Index 3
Idle State Count 1
Idle State Type ACPI Idle (C) States
Nominal Frequency (MHz) 3600
Maximum Performance Percentage 100
Lowest Performance Percentage 22
Lowest Throttle Percentage 22
Performance Controls Type ACPI Performance (P) / Throttle (T) States
Device Drivers:Analysis Success
Analysis was successful. No energy efficiency problems were found. No information was returned.

And thanks so far for your help!

 

[johnbl]

initially your system will keep power to the RAM so it can wake up fast, (this is working) but after some time it will copy the RAM to the hard drive and power off the system. Problem is parts of the info are not being correctly copied to disk. The system detects this and calls the bugcheck.

it can be that your hard drive has a problem, it spins down but maybe is not waking up to complete the write from memory to the disk. Normally this can be a bug in the BIOS, the hard drive or the hard drive controller. Your driver for your hard drive controller was old (2009) a updated verison my fix the problem.
I think you could also use windows control panel, device manger, find the disk drive power management and tell it not to go to sleep. I think the default it to spin down after 15 mins or so.

very common for USB devices to have sleep problems on older machines, often these are "fixed" in BIOS
sometimes in driver updated. (most often the drivers just disable the functions) I say it is common mostly because hardware made during the windows 7 time frame had the functions disabled in the windows 7 by default so people did not see the problems until they went to windows 8.x which have them enabled by default. if you can, get a BIOS update or a driver update it is a best chance to get it working correctly otherwise you have to disable the power management features for the device (hard drive)




------------
BugCheck A0, {10a, a, ffffe0013655a380, ffffffffc0000001}
INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 000000000000010a, The disk subsystem failed to properly read or write part of the hibernation
file.
Arg2: 000000000000000a
Arg3: ffffe0013655a380, POP_HIBER_CONTEXT
Arg4: ffffffffc0000001, NTSTATUS failure code


0: kd> !error 0xc0000001
Error code: (NTSTATUS) 0xc0000001 (3221225473) - {Operation Failed} The requested operation was unsuccessful.
0: kd> kc
Call Site
nt!KeBugCheckEx
nt! ?? ::OKHAJAOM::`string'
nt!PopWriteHiberImage
nt!PopSaveHiberContext
nt!PopSaveHiberContextWrapper
hal!HaliAcpiSleep
nt!PopHandleNextState
nt!PopIssueNextState
nt!PopInvokeSystemStateHandler
nt!PopEndMirroring
nt!MmDuplicateMemory
nt!PopTransitionToSleep
nt!PspSystemThreadStartup
nt!KiStartSystemThread

 

[KazenoS]

I have gone into the power options in the control panel and changed turn hard disk off after 20 min to never and will wait and see if it fixes it.
I am using the newest stable BIOS according to the website but that and the newer one was released in 2013.

 

[johnbl]

I was thinking about this problem, you might also consider making a new pagefile.sys. you would disable your virtual memory, reboot, unhide the file c:\pagefile.sys and rename it to pagefile.bad, then re enable your virtual memory so that a new pagefile.sys is created on a new location of your hard drive. This would be on the assumption that your current pagefile is on a sector that is having problems writing to your drive. (just more likely to be a problem with your old sata driver though)

you can also run crystaldiskinfo.exe and see if your drive is reporting any errors. I would also read the firmware version from the SSD and see if there are known problems with it. ie, check for a firmware update for your SSD. This would not apply if your pagefile.sys is not on your SSD.

I have gone into the power options in the control panel and changed turn hard disk off after 20 min to never and will wait and see if it fixes it.
I am using the newest stable BIOS according to the website but that and the newer one was released in 2013.

 

[KazenoS]

I am having problems renaming the pagefile.sys. The way I am disabling virtual memory i via Performance Options into Virtual Memory and checking "No paging file" but predictable enough this removes the pagefile.sys so I cannot rename it. Is this the way to do it?

Also I haven't been getting crash dumps since I switched it to Kernel memory dump so should I switch it back to automatic memory dump?

The firmware for the SSD should be up to date. Using a Samsung 840 evo with the firmware version ext0cb6q. And I used Samsung SSD 840 EVO Performance Restoration which should also update the firmware and the version didn't change

 

[johnbl]

if the pagefile was deleted when you turned off the virtual memory. That would be ok. just make sure because it is a hidden file and would not show up unless you enable the show hidden files flag in explorer.

Main point was to get rid of it and create another. (most likely not the problem anyway)

- you have to enable kernel memory dump to keep the debugging info from being stripped out of the memory dump.
I would leave it as a kernel dump for a while and see if you bugcheck.

I am having problems renaming the pagefile.sys. The way I am disabling virtual memory i via Performance Options into Virtual Memory and checking "No paging file" but predictable enough this removes the pagefile.sys so I cannot rename it. Is this the way to do it?

Also I haven't been getting crash dumps since I switched it to Kernel memory dump so should I switch it back to automatic memory dump?

The firmware for the SSD should be up to date. Using a Samsung 840 evo with the firmware version ext0cb6q. And I used Samsung SSD 840 EVO Performance Restoration which should also update the firmware and the version didn't change

 

[KazenoS]

I have had very few crashes lately and haven't gotten a kernel memory dump file, but are seem to be another problem. When I turn of f my computer it does a standard shutdown but then it black screens and the computer doesn't turn off. When I turn it on again and check the minidump folder a file has been made even though it is set to kernel memory dump. When I turned on my computer today I got this error screen, but after a hard reboot I could access my computer as normal.

Here is the error screen:
https://onedrive.live.com/redir?resid=13658DB7F59932E5!599&authkey=!AG4aVbTMdZPapWw&ithint=file%2czip
Here are the dump files it makes
https://onedrive.live.com/redir?resid=13658DB7F59932E5!598&authkey=!ADETuAIwDhgFsIQ&ithint=file%2czip

 

[johnbl]

the memory dump looks the same. the disk subsystem failed to write part of the hibernation file.
returned error code: (NTSTATUS) 0xc0000001 (3221225473) - {Operation Failed} The requested operation was unsuccessful.

I think you just have a BIOS bug.
Also, I can not read your BIOS info out of your memory dump.
you might also want to remove some of your suspect drivers:
like WinDivert.sys (hacking software) often used for game cheats, hacks network packets.

also, the memory dump still shows overclocking software installed.
AODDriver2.sys Tue Feb 11 03:06:52 2014

 

[KazenoS]

Hello, I am still trying to get a kernel memory dump but it never happens
I have tried increasing the paging file size to 20000 MB, using system managed size and automatically manage paging file size. I have set the dump file to kernel memory dump and checked "Write an event to the system log" and the dump file location is %SystemRoot%\MEMORY.DMP. So I was wondering if you had any ideas to actually make it write a kernel memory dump
Another thing is that I don't BSOD anymore, now it just freezes forever ( have tried waiting 3 hours, nothing changed).

 

[johnbl]

set some registry keys so you can force a memory dump by hitting the keyboard.
http://blogs.technet.com/b/askpfeplat/archive/2015/04/06/how-to-force-a-diagnostic-memory-dump-when-a-computer-hangs.aspx

that way you don't actually have to wait for a bugcheck, you can just wait until your system hangs then force a memory dump and have some one look at it.

Note: you can do it on a system that is running without problems to test to make sure the registry keys are set correctly.
and that you get a proper dump file.

if your system is hanging you will want to make sure you run cmd.exe as an admin and run
verifier.exe /standard /all
then reboot. It will place extra debug info in the memory dump and will check for common driver bugs.

note use
verifier.exe /reset
to turn off verifier functions when you are done testing or your system will run slowly.

Hello, I am still trying to get a kernel memory dump but it never happens
I have tried increasing the paging file size to 20000 MB, using system managed size and automatically manage paging file size. I have set the dump file to kernel memory dump and checked "Write an event to the system log" and the dump file location is %SystemRoot%\MEMORY.DMP. So I was wondering if you had any ideas to actually make it write a kernel memory dump
Another thing is that I don't BSOD anymore, now it just freezes forever ( have tried waiting 3 hours, nothing changed).

 

[KazenoS]

I have set CrashonCtrlScoll up and when I test it it creates a kernel memory dump file, however when the pc freezes and I force crash it doesn't write a kernel memory dump nor a minidump for that matter.

set some registry keys so you can force a memory dump by hitting the keyboard.
http://blogs.technet.com/b/askpfeplat/archive/2015/04/06/how-to-force-a-diagnostic-memory-dump-when-a-computer-hangs.aspx

that way you don't actually have to wait for a bugcheck, you can just wait until your system hangs then force a memory dump and have some one look at it.

Note: you can do it on a system that is running without problems to test to make sure the registry keys are set correctly.
and that you get a proper dump file.

if your system is hanging you will want to make sure you run cmd.exe as an admin and run
verifier.exe /standard /all
then reboot. It will place extra debug info in the memory dump and will check for common driver bugs.

note use
verifier.exe /reset
to turn off verifier functions when you are done testing or your system will run slowly.

 

[johnbl]

that can happen if the problem is in the storage subsystem.
I would try and put my drive on a different SATA port or on the primary SATA controller (the slower one)
if you system BIOS has a setting for hotswap for the sata port, enable it.

maybe update your SATA drivers if they are custom (or a custom sata chipset)
- maybe move your location of where your memory dump is being stored to a different physical drive.

I have set CrashonCtrlScoll up and when I test it it creates a kernel memory dump file, however when the pc freezes and I force crash it doesn't write a kernel memory dump nor a minidump for that matter.

set some registry keys so you can force a memory dump by hitting the keyboard.
http://blogs.technet.com/b/askpfeplat/archive/2015/04/06/how-to-force-a-diagnostic-memory-dump-when-a-computer-hangs.aspx

that way you don't actually have to wait for a bugcheck, you can just wait until your system hangs then force a memory dump and have some one look at it.

Note: you can do it on a system that is running without problems to test to make sure the registry keys are set correctly.
and that you get a proper dump file.

if your system is hanging you will want to make sure you run cmd.exe as an admin and run
verifier.exe /standard /all
then reboot. It will place extra debug info in the memory dump and will check for common driver bugs.

note use
verifier.exe /reset
to turn off verifier functions when you are done testing or your system will run slowly.

 

[KazenoS]

I tried moving the memory dump to another drive but that didn't work.
However since I change the SATA port my SSD is connected to I haven't had a crash (7 days), so I believe the problem is solved. I will wait a weeks time before I mark it as solved to see if it isn't. Thanks a ton for all your help!

 

[Sushant Shekhar]

this worked for me
AMD driver was the culprit
http://www.onehackup.com/2015/08/01/internal-power-error-dell-laptop-error-solved/