bsod involving ntoskrnl.exe. i dont even know what to do anymore!

[lordbredd]

Hello tom's hardware community. I come to you with help about yet another DREADED BSOD!!!

First I shall describe my situation. My computer is a custom build I did myself and I have been using it for over a year with relatively no problems. However, for the past few months everything has been going wrong with it in such an inconsistent way I cannot isolate the problem. Yesterday it ran perfectly fine nonstop for 12 hours while this morning I can't boot without crashing as soon as I reach my desktop. I get crashes that only sometimes are blue screens. When this problem started the crash code I would get was mainly bc code f4 but sometimes it would be bc code 50 or 51. When it crashes w/o a blue screen my computer just goes to black and all the fans spin up as if the computer is trying to start up, but I cannot hard reset it. Only thing I can do is pull the power plug. The kicker here is that these problems have persisted through multiple reinstalls of windows using different hdds and different methods, i.e. cd vs usb. While the bc codes might change between the three, using bluescreenview to look at my dump files they always say ntoskrnl.exe was the problem. Right now the only way I can boot is into safe mode.

Now as far as what I have done to try to fix this on my own I'll try to give as much detail as I can. I have looked up each bc code to see what it affects and how to fix it. I have run Seatools, Western Digital's hdd checker, and check disk but all my hdds pass short and long tests. One drive did have a bad sector after a Seatools long test but it was fixed and now consistently passes. I have switched my hdds around with different sata cords and in different sata ports on my motherboard. I have tried booting with every possible combination of ram and it still crashes exactly the same. I have run memtest individually on my ram sticks and on them together getting no errors after 4 passes. I have switched my graphics card in case that was the problem and it had no effect. I have completely taken my computer apart, cleaned everything, put it back together and it still happens.

What am I doing now? Well after this most recent reformat and reinstall of windows on a fresh drive I'm getting mostly bc code 50. So I'm trying out memtest again.

I should say my computer was originally overclocked but completely stable. It ran prime 95 a full 24 hours with no errors and not going over 60C. Since these problems started though I returned it to stock settings.

Once this memtest is finished I'll get some dump files to share.

At this point I'm thinking my motherboard is just bad. I have no idea what to do anymore.

Motherboard: Gigabyte F2A85X-UP4
CPU: AMD A10-5800K with Corsair Hydro H60 cooling system
RAM: 2 sticks of Patriot Memory G2 Series 8GB
GPU: EVGA Geforce GTX 650 and EVGA Geforce GTX 550TI. The 550ti is currently plugged in as I'm writing this post.
PSU: Rosewill Green Series RG630-S12 630W
HDDs: Seagate SV35.5 500GB <----plugged in, has windows
WD Caviar Blue WD10EZEX 1TB <----plugged in, just used as storage
Seagate Barracuda 7200.10 80GB
WD Caviar WD2000 200GB
Seagate Barracuda 7200.10 250GB
Maxtor DiamondMax Plus 9 160GB
OS: Windows 7 Ultimate 64-bit

Please let me know if there is any other information that is needed and thank you in advance for any help you may be able to offer.

EDIT: The memtest passed with no errors after 4 passes again. I'm providing a link to a .zip file with the minidumps I have recieved.
https://onedrive.live.com/redir?resid=EAD96ADC7E2A068%211631

 

[lordbredd]

My computer is a custom build I did myself and I have been using it for over a year with relatively no problems. However, for the past few months everything has been going wrong with it in such an inconsistent way I cannot isolate the problem. Yesterday it ran perfectly fine nonstop for 12 hours while this morning I can't boot without crashing as soon as I reach my desktop. I get crashes that only sometimes are blue screens. When this problem started the crash code I would get was mainly bc code f4 but sometimes it would be bc code 50 or 51. When it crashes w/o a blue screen my computer just goes to black and all the fans spin up as if the computer is trying to start up, but I cannot hard reset it.


after rereading your post I wonder if the psu is failing ? lets say its not putting the correct power to the board or vid card and comes and goes so one time its seems good then next time its bad .. read a few reviews at newegg on your psu and there a few with the ''lasted 6 months -good for a year'' tour right at that point in its life [??] I know where your coming from when you get down to should I need to replace something and now its a gamble ..

did you not want to open the files you linked to se we can look at them with out having to download ?

I didn't copy paste the dump file because I thought it was just preferred to have them like I did it. At least, it looked like that from other threads I was reading before I started my thread.

I am scared it might be a power supply issue too. That's something I can't do anything about except buy a new one. I have had my current one for a year and a half now so it might be that but I don't know for sure and I don't know how I'd test it. But it only MIGHT be a power supply issue. If I can't fix my computer perfectly I would like to be able to narrow it down to what the problem is and see if I can get a manufacturer repair because everything is still under warranty I believe.

 

[junkeymonkey]

ya but I just don't download anything from anywhere also that johnbl guy posted what I kinda wanted to see and like I guessed your spyware caused the one he posted above ..

johnbl

looks like it was caused by a virus scanner
1: kd> lmvm aswSP
start end module name
fffff880`04200000 fffff880`0426d000 aswSP T (no symbols)
Loaded symbol image file: aswSP.sys
Image path: \SystemRoot\system32\drivers\aswSP.sys
Image name: aswSP.sys
Timestamp: Mon May 05 01:11:11 2014 (5367479F)
CheckSum: 00075AAC
ImageSize: 0006D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

you might want to remove avast or update it to see if the problem still occurs.
will look at the other dumps in a minute

 

[lordbredd]

I received 2 more crashes last night. The first one happened when I was trying to download something with utorrent. I got an error that said the disk was unwriteable I think, it popped up in the task manager fast so I couldn't really read it, then my computer promptly crashed after that message popped up giving me an f4 bsod error. After it restarted it went to desktop just fine and in uninstalled everything utorrent related and deleted all related files. I tried to install wildstar onto my TB harddrive that is plugged in and it got 4% done then it appeared that my TB remounted itself. I got the autorun dialogue box that pops up as if I had plugged in a usb drive. The install failed so I closed and was going to shutdown and worry about it later. As I was shutting down it crashed again giving me another f4 bsod error.

I'll copy paste the error event from bluescreenview

062114-29499-01.dmp
6/21/2014 4:54:36 AM
CRITICAL_OBJECT_TERMINATION
0x000000f4
00000000`00000003
fffffa80`0ee7d060
fffffa80`0ee7d340
fffff800`031c9270
ntoskrnl.exe
ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System
Microsoft Corporation
6.1.7601.18409 (win7sp1_gdr.140303-2144) x64 ntoskrnl.exe+75bc0
C:\Windows\Minidump\062114-29499-01.dmp
4
15
7601
285,752
6/21/2014 4:58:10 AM

Please let me know if there is any other information needed. Thank you.

 

[johnbl]

well, the system detected a corruption of a key data structure and shut down.

- i would delete the pagefile.sys and create another one
- would unplug the cables to the drive or replace them and enable hotswap in the BIOS for the sata port.
(if you get a thermal expansion/contraction on the cable connection the system will act like you unplugged the drive and plugged it back in, this can happen several times a second and really cause problems for you. The enable hotswap in the BIOS is a work around that will allow the drive to reconnect and the file access to work again after the reconnection. Otherwise you will bugcheck the same as if you pulled out the drive from your machine. if you have lots of memory you can unplug idle windows OS drive for hours before you bugcheck windows. (most of the time you will not get a memory dump unless you have a pagefile on another drive that is not connected.)

 

[junkeymonkey]

you may try to get the Microsoft c+ runtime downloads and the dx9 runtime from Microsoft to see if something needs help from them that's not covered in windows 8 [ I run older programs and games so I get them] and se how that works

read this overview part were it shows the need for c runtime
http://en.wikipedia.org/wiki/Ntoskrnl

 

[lordbredd]

Sorry I haven't responded in a while I have been busy with other things in my life. The last thing I did was turn on hot swapping yet I'm still getting crashes. Here is the event from bluescreenview:

062214-20014-01.dmp
6/22/2014 12:45:22 AM
CRITICAL_OBJECT_TERMINATION
0x000000f4
00000000`00000003
fffffa80`0ef02b30
fffffa80`0ef02e10
fffff800`03189270
ntoskrnl.exe
ntoskrnl.exe+75bc0
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation
6.1.7601.18409 (win7sp1_gdr.140303-2144)
x64
ntoskrnl.exe+75bc0
C:\Windows\Minidump\062214-20014-01.dmp
4
15
7601
287,528
6/22/2014 12:51:45 AM


I believe I already have the Microsoft C+ runtimes and dx9. Also I'm running Windows 7 Ultimate x64 not Windows 8.

I'll try changing around my sata cords some more to see if that does anything.

At this point I'm wondering could it just be a faulty motherboard or failing power supply? I don't have the money to deal with it now but if I could at least isolate it and replace it when I can that would be nice.

 

[junkeymonkey]

well like you said the drives come up with bad sectors they just don't go bad for the heck of it .. were these new drives that you started out with or are you reusing old drives ?
found this guy said something about firmware update

http://www.techpowerup.com/forums/threads/using-a-seagate-surveillance-sv35-5-hd-for-a-standard-pc.106388/

don't know - I'm out of ideas

 

[lordbredd]

well like you said the drives come up with bad sectors they just don't go bad for the heck of it .. were these new drives that you started out with or are you reusing old drives ?
found this guy said something about firmware update

http://www.techpowerup.com/forums/threads/using-a-seagate-surveillance-sv35-5-hd-for-a-standard-pc.106388/

don't know - I'm out of ideas

Yes these are old drives. All but the TB which I get the same crash even if I run windows off of it. Thanks for that link I'll try find the firmware update and see if I need it.

Thank you for your help though really. I came here because I was out of ideas as well.

 

[junkeymonkey]

well as for me when I try to reuse a hard drive it ends up I wished I just got a new drive right from the start now I always get a new drive with a new build or a new install of windows cause these issues seem to always pop up

 

[johnbl]

ok, your system is detecting a critical data structure is getting corrupt and windows is shutting down your system.
if you can get a memory dump you can use the windows debugger and run the following command on your crash dump file:
!for_each_module !chkimg @#ModuleName

this will go to most of the key windows modules in your debug dump and check them for corruption in the copy of your system memory. generally, if you get several memory dumps with the same corruption, you will find that a virus or rootkit is the main cause. Since windows loads the modules into different places of memory on each boot, if you have a physical hardware problem you will get a different module corrupted on each boot and the debugger can detect it.

before you assume you have a power supply problem, you want to confirm that the BIOS voltages are set correctly for your cpu.

also, if you have a solid state drive, you want to make sure there is free space and that its TRIM functions are being called.
(boot into the BIOS screen and leave the machine there to allow the drives garbage collection cleanup routines to run without windows blocking them, generally they will start running 5 mins after the machine goes idle, if you boot into BIOS the drive gets power and windows will tell the drive to go to a low power state, this will give the drive time to catch up on its garbage collection)
newer versions of windows 8.x and above will work much better for SSD than windows 7.

The main point is that windows is detecting that its internal data structures are being modified after they were written.
windows assumes this is because of a virus (most often) or certain types of hardware failures (crack in the copper trace in a memory chip address line, bugs in external cache memory (cpu will issue its own bugcheck if its cache memory is corrupted)

if you can get a memory dump on a cloud server, I can take a quick look and see if I can tell you the cause, or at least what windows thinks the cause is.

 

[junkeymonkey]

was trying to download something with utorrent [??] what do you do with this stuff when I see anything with torrent I think unsafe I don't know with all them drives and downloading it seems you do theres no telling what you picked up I'm just guessing
now as johnbl states about corruption we know the drive has bad sectors also has it now got read write issues?? and did what caused the bad sectors affecting that?? its a used drive and how many times has it been wrote over? see this is what I found when reuseing a drive I never had good luck in doing so and I end up getting a new drive for boot and windows I got several here with bad sectors that I tried to reuse and ended up just storage just like you I reuse a drive and its fine for awile then issues come up a few bsods then detected a bad sector and more bsods .. this may not be your case but it how it went for me over the years..

 

[lordbredd]

ok, your system is detecting a critical data structure is getting corrupt and windows is shutting down your system.
if you can get a memory dump you can use the windows debugger and run the following command on your crash dump file:
!for_each_module !chkimg @#ModuleName

this will go to most of the key windows modules in your debug dump and check them for corruption in the copy of your system memory. generally, if you get several memory dumps with the same corruption, you will find that a virus or rootkit is the main cause. Since windows loads the modules into different places of memory on each boot, if you have a physical hardware problem you will get a different module corrupted on each boot and the debugger can detect it.

before you assume you have a power supply problem, you want to confirm that the BIOS voltages are set correctly for your cpu.

also, if you have a solid state drive, you want to make sure there is free space and that its TRIM functions are being called.
(boot into the BIOS screen and leave the machine there to allow the drives garbage collection cleanup routines to run without windows blocking them, generally they will start running 5 mins after the machine goes idle, if you boot into BIOS the drive gets power and windows will tell the drive to go to a low power state, this will give the drive time to catch up on its garbage collection)
newer versions of windows 8.x and above will work much better for SSD than windows 7.

The main point is that windows is detecting that its internal data structures are being modified after they were written.
windows assumes this is because of a virus (most often) or certain types of hardware failures (crack in the copper trace in a memory chip address line, bugs in external cache memory (cpu will issue its own bugcheck if its cache memory is corrupted)

if you can get a memory dump on a cloud server, I can take a quick look and see if I can tell you the cause, or at least what windows thinks the cause is.

Here is a cloud link for minidumps and other data that was collected using sevenforums.com's dm log collector. I was trying to get help there as well but after 3k+views the only help I received was, "get a legitimate copy of windows and then we will help."
https://onedrive.live.com/redir?resid=EAD96ADC7E2A068%211634

I attempted another reformat using a windows 7 professional download with a legitimate cd key from a friend of mine. Currently the only things installed are drivers for chipset, ethernet controller, audio, gpu, microsoft visual c++ 2010 redistributable, and wildstar (but this is on the TB instead of the hard drive that windows is installed on). I have not done ANY windows updates, I have not even opened Internet Explorer, I have not installed anything except for what was stated above.

Because of this I'm not sure if the link I provided will be of any help, but it is the most recent logs of anything before I reformatted.

Since the reformat my computer has crashed but not by bsod. The whole thing goes to black and restarts immediately booting to the dos menu that asks if I want to boot in safe mode, safe mode with networking, safe mode with command prompt, or start windows normally.

I will continue using it and report on any events that do happen.

 

[lordbredd]

was trying to download something with utorrent [??] what do you do with this stuff when I see anything with torrent I think unsafe I don't know with all them drives and downloading it seems you do theres no telling what you picked up I'm just guessing
now as johnbl states about corruption we know the drive has bad sectors also has it now got read write issues?? and did what caused the bad sectors affecting that?? its a used drive and how many times has it been wrote over? see this is what I found when reuseing a drive I never had good luck in doing so and I end up getting a new drive for boot and windows I got several here with bad sectors that I tried to reuse and ended up just storage just like you I reuse a drive and its fine for awile then issues come up a few bsods then detected a bad sector and more bsods .. this may not be your case but it how it went for me over the years..

As soon as I can get a fresh hard drive I will. That might not be for a while but I will heed your words.

 

[junkeymonkey]

"get a legitimate copy of windows and then we will help."

I attempted another reformat using a windows 7 professional download with a legitimate cd key from a friend of mine

so your trying to boot leg windows ?? why not get a real copy on the disk that never been used .. doing all this jackleageng around anit getting you nowhere .. you start with crap and you end up with the same ..

I see lots of this 'I downloaded windows '' threads here.. and determined that its something I won't be trying any time soon.

 

[johnbl]

I looked at one of your crash dumps..
the copy of windows really is really not the issue. you have a user mode process that is attempting to kill your virus scanner and it causes the bugcheck.

I assume it is a virus/malware that did it.

you will want to download and run malwarebytes to remove the infection.

I specify malwarebytes because they will remove a malware even if you accepted the bogus license agreement that some of these have. Some software will put "we can do anything to your machine" in the license and claim that since you agreed to it they are not malware, they then sue virus scanner vendors to prevent them from removing their software.

I will take a look at another one of your memory dumps and see if it is the same cause.

looks like the second one was caused by a corrupted registry entry. this could be malware, or just a side effect of your system crashing from the first bugcheck. (crash while with pending writes to the registry)
I would fix the potential virus problem first, then run
the system file checker
start cmd.exe as a admin
run sfc.exe /scannow (this will check the core windows files and if corrupt will attempt to replace them with their hidden backup copy)

note: there can be other issues that can cause this but a virus is the most likely.

 

[junkeymonkey]

johnbl- well he claims that this is on a fresh install so wheres the virus stored at ? so if he used seatool and wiped the drive clean and did a fresh install the only way in is through the downloaded windows he got right at the start of things [???] also I don't think he unhooks the internet so theres no online access wile windows installs is so then it should be only connecting to Microsoft . I don't know ..

he said up top ''What am I doing now? Well after this most recent reformat and reinstall of windows on a fresh drive I'm getting mostly bc code 50. So I'm trying out memtest again. ''

so hows the virus affecting this ??

 

[johnbl]

random hardware failures don't hunt through windows kernal code and attempt to kill virus scanner processes with valid windows thread kill commands. The information provided must be incorrect. For a valid bugcheck the memory dump contains the correct information as to the problem.

johnbl- well he claims that this is on a fresh install so wheres the virus stored at ? so if he used seatool and wiped the drive clean and did a fresh install the only way in is through the downloaded windows he got right at the start of things [???] also I don't think he unhooks the internet so theres no online access wile windows installs is so then it should be only connecting to Microsoft . I don't know ..

he said up top ''What am I doing now? Well after this most recent reformat and reinstall of windows on a fresh drive I'm getting mostly bc code 50. So I'm trying out memtest again. ''

so hows the virus affecting this ??

 

[junkeymonkey]

well ok looking this back over it looks like he does a lot of downloading of anything and everything like I said I won't even download his bug check link just because . and if this is in one of them files ?? you never know

I guess I done all I can here on this ..

 

[johnbl]

generally a memory dump file will not infect you. but the darn virus writers put malware wrappers around various tools and put them up on the internet for people to download. for example someone might zip up a file or .rar a bunch of files for you
then you need a tool to unarchive them. you have to get the unarchive tool to extract the memory dumps. That is where you pick up the viruses.

for example lots of versions of various extractors will have viruses or browser search tools that are actually viruses. Well at least windows 8.1 will crash your system when you click yes you want to install the tool. (virus corrupts windows core code and it is detected and windows calls a bluescreen)