Windows 8.1 ntoskrnl.exe crash dumps

Kichirou

Reputable
Jan 19, 2015
1
0
4,510
I periodically get BSOD's that when I look at them on BlueScreenView say they are the ntoskrnl.exe, sometimes it includes hal.dll as the problem. The problem is very off and on.

This is a brand new computer a friend built for me for Christmas and it worked fine for a while then after I installed iTunes to put some files on my fiance's iPad I started getting these errors. I started troubleshooting and it seemed to be some sort of driver error based on the bugcheck strings I was getting. I rolled my computer back to before I installed iTunes and it was good for a while. Now I'm back to getting them. I just tried to roll back again and it didn't fix the error this time.

Here's a dropbox of my my minidumps from tonight.
https://www.dropbox.com/sh/iprxmhff9d4axu6/AADPFZM0RaWHItqNWqUHFQAOa?dl=0 Let me know if there is anything else you need.
 
Solution
second bugcheck was a low level memory corruption.
I would confirm your install of windows by running
cmd.exe as an admin
then
sfc.exe /scannow
if you get any errors reported then run
dism.exe /online /cleanup-image /restorehealth

-------------------
looked at the first bugcheck, it was in memory management where windows detected that its tracking of its virtual memory was corrupted. (the map between the physical RAM and what is paged to the hard drive was corrupted)

hard to say what caused the corruption.

- i would remove your overclocking driver
C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys Wed Sep 11 20:36:40 2013

- go into BIOS and update or reset it to defaults
- move your drive to another SATA port...
second bugcheck was a low level memory corruption.
I would confirm your install of windows by running
cmd.exe as an admin
then
sfc.exe /scannow
if you get any errors reported then run
dism.exe /online /cleanup-image /restorehealth

-------------------
looked at the first bugcheck, it was in memory management where windows detected that its tracking of its virtual memory was corrupted. (the map between the physical RAM and what is paged to the hard drive was corrupted)

hard to say what caused the corruption.

- i would remove your overclocking driver
C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys Wed Sep 11 20:36:40 2013

- go into BIOS and update or reset it to defaults
- move your drive to another SATA port, check the connections.
- run a test on your drive
- I would run a memtest86 to test your memory

I will look at the other bugchecks, maybe something more to the point will show up
 
Solution