BSOD while launching Windows

radzik07 · 16 Mar 2014

Hello everyone.
I'm getting a little frustrated now because of my Asus notebook (K70IO).
Almost everytime I turn it on, I get a BSOD with one of following errors: BAD_POOL_CALLER, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, PAGE_FAULT_IN_NONPAGED_AREA. Sometimes there's even no error, just blue screen without it. At most of the times it's fast - I can only see a blink of blue screen and computer restarts. Usually there are 2-3 bsods before system loads up, most of the times it's on "Starting windows" black screen, but sometimes also at "Welcome" screen.
I noticed the bsods appear doesn't appear while restarting system - only on 'first' start.
It's been a long time since I experienced it for the first time and I managed to live with it till now, but there's a possibility I'll get a new hardware soon and then this one's going for sale. I just don't want the new owner to have that problems.
Ok so what have I recently done:
1. memtest with no errors
2. HDTune check + MHDD - here comes the story:
I was facing another strange problem with my comp, this one was even more annoying. From time to time my Asus was getting "freezed" for two minutes, if at the time I had my music player turned on, there was only a loud sound coming out, like a truck or something. For one-two minutes. I couldnt do a thing except wait.
Soo I checked HDtune.
It showed me a bad sector on HDD, so I launched MHDD and did a remap. I also did a full hdd format and installed a new system. And it helped. No more bads in HDtune. I thought these two problems could be caused by one reason, but unfortunately one problem still happens.
3. verifier.exe - I followed some tutorial found at the top of google, set this thing up and did a restart as it asked. Unfortunately, I couldn't get into the system after that - there was a non-error BSOD everytime at Welcome screen. So I had to turn verifier.exe off in safe mode.
4. I really did a google.
5. Somebody said to clean the ram slots, put the sticks off and on, replace them. Im going to do it soon..
Ah, long story, with hard english and no happy end - I know, I know.
I put my minidump folder in attachments. I see the last two dumps from today are empty - the bsods said DUMP is 100% and I had to restart it manually, dunno why it didn't save.
I also put log from BlueScreenView.
And the DM Log package.
Thank you

Arc · 16 Mar 2014

Hi radzik07.

How many passes you ran memtest? It is suggested to run memtest86+ for at least 8 passes, because there is a possibility as per some crash dumps of the beginning of the month.

Code:

BugCheck 50, {fffff1400027b41e, 1, fffff80002d4e017, 7}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff80002b00150, fffff88002e28588, fffff88002e27de0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

But the most recent crash dumps are not opening.

Attachment 310624

That means, those took place before you got into the desktop.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept then restart.

Hopefully it will allow you to go to desktop before you see a BSOD screen.

Let us know the results.

radzik07 · 16 Mar 2014

Hey Arc, thanks for fast reply!
I did what you said - turned off most of startups. Then I turned on the verifier.exe again (should I?) and it worked! - I mean I think it worked, i got the same bsod as before, with no error, but this time the dump file isn't empty. It's in attachments.

About memtest.. 8 times? Wow. Is there a setting which will allow the program to loop 8 times? Or should I restart memtest 8 times manually (that would take time)?

Im also thinking about cleaning that ram slots a little.. but won't be able to do it today..
Thanks again!

// forgot to add: I ran the memtest just once :P

Arc · 17 Mar 2014

The BSOD points to ATK Hotkey ATK0101 ACPI UTILITY Driver.

Code:

BugCheck C4, {3c, 5151515100000184, 0, 0}

*** WARNING: Unable to verify timestamp for ATK64AMD.sys
*** ERROR: Module load completed but symbols could not be loaded for ATK64AMD.sys
Probably caused by : ATK64AMD.sys ( ATK64AMD+11e4 )

Followup: MachineOwner
---------

Which is extremely old.

Code:

fffff880`05945000 fffff880`0594d000   ATK64AMD T (no symbols)           
    Loaded symbol image file: ATK64AMD.sys
    Image path: \SystemRoot\system32\DRIVERS\ATK64AMD.sys
    Image name: ATK64AMD.sys
    Timestamp:        Fri Oct 27 18:15:25 2006 (4541FF65)
    CheckSum:         0000F651
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I'd recommend you to Clean Up Factory Bloatware, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

About memtest, it is counted by passes, not by times. And, the "at least 8 passes" means "at least 8 consecutive passes". :)

Let memtest run. it will run at its own till you abort it manually. Just keep an eye on the passes count.

Attachment 310717

radzik07 · 17 Mar 2014

Arc, thank you very much!
Reinstalling ATK hotkey with newer version seems to have solved my problems.
I think I will PASS ( :) ) with memtest for a while now. I remember last time I left memtest for maybe 10-12 hours, but didn't check how many passes it went through. Maybe it even was 8.
However, my Asus is happy now, and so am I.
Thanks again!

Arc · 17 Mar 2014

You are welcome mate.

Let us know about any further issue.

radzik07 · 21 Mar 2014

Unfortunately, I'm back with same problem. It seems atk hotkey didn't solve it. I mean partially it did, because there aren't so many bsods now, just one (there were 2-3 before).
The bsod appears at "Starting Windows" black screen. The biggest problem is the bsod is 0.5 second long - I can't read what it says, and it doesn't save any minidump files. It's too fast, it just blinks and the computer restarts.
I removed the ATK hotkey completely (uninstalled).
I also did a memtest with 7 passes without an error.
What else can I do? Is there any way to make the bluescreen last longer?

Arc · 22 Mar 2014

If you report about a BSOD, you have to Post it following the Blue Screen of Death (BSOD) Posting Instructions. We cannot suggest you without seeing the required data.