Abhorrent BSoDing - Asus G60JX i5

ultranothing · 27 Jul 2010

Hello, all,

I've been doing some research here on various BSoD's and their associated stop errors, and while I haven't been able to discover a solution to my particular issue(s), I must say I was absolutely impressed with the level of professionalism and sincerity shown by the sevenforums community in helping others. For that, I thank you all.

I've attached the archive of my minidump files. There are 51 of them, and it's been rather frustrating to say the least.

In the middle of any random activity, but usually when I'm listening to audio, the BSOD will occur. I've noticed several different stop codes, but the DMPs will give you more info than I can remember offhand.

The BSOD will almost always occur after a buzzing sound which I can't quite describe here. Forgive the metaphor, but I can only describe it as a sustained "boner" sound effect...you know..."sproing!"

Anyway, it's driving me insane. I've tried multiple things, such as driver updates and rollbacks, bios updates, chipset driver updates and rollbacks...

Please, guide me to a solution!

reventon · 27 Jul 2010

Hi,

All are near identical 0x7f_8 (usually software) BSODs but no 3rd party driver is specifically mentioned. Because of this you should run Driver Verifier.

Driver Verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Other things you can do:

1. Uninstall Avast

Avast has been known to cause BSODs before, I would uninstall it if I were you just in case.

Download the Avast Removal Tool (ART) from here -> save to desktop.

Boot into SAFEMODE - NO Networking. Then go to desktop, RIGHT-click on the ART icon and select Run as Administrator.

When complete - re-boot.

Install MS Security Essentials --> http://www.microsoft.com/Security_Essentials/

Then reset the Windows Firewall to its default settings -
START -> type cmd.exe -> right-click -> run as administrator -> type netsh advfirewall reset press enter

2. Out of Date Driver

Code:


ASMMAP64.sys Mon Feb 05 08:52:56 2007 (45C63998)

The above driver appears to be an ASUS ACPI UTILITY Driver. It's 'brother' ASACPI.sys causes lots of trouble, so I am really suspicious of this one too.

ASMMAP64.sys - Update link here, update instructions (slideshow) here (note that in the last step you select the ATK0101 ACPI driver in the list instead of the one mentioned)

Regards,
Reventon

BUGCHECK SUMMARY

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 28 13:54:38.540 2010 (GMT+12)
System Uptime: 0 days 1:35:54.758
BugCheck 7F, {8, 80050031, 6f8, fffff80003090e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 28 12:18:11.029 2010 (GMT+12)
System Uptime: 0 days 20:23:51.621
BugCheck 7F, {8, 80050031, 6f8, fffff80003098e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 27 15:53:48.102 2010 (GMT+12)
System Uptime: 0 days 1:03:25.694
BugCheck 7F, {8, 80050031, 6f8, fffff8000303ae58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 27 14:49:25.149 2010 (GMT+12)
System Uptime: 0 days 1:35:27.741
BugCheck 7F, {8, 80050031, 6f8, fffff80003057e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 27 13:12:59.968 2010 (GMT+12)
System Uptime: 0 days 19:51:51.560
BugCheck 7F, {8, 80050031, 6f8, fffff80003055e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 26 17:20:06.153 2010 (GMT+12)
System Uptime: 0 days 1:35:59.371
BugCheck 7F, {8, 80050031, 6f8, fffff80003098e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 26 13:35:13.092 2010 (GMT+12)
System Uptime: 0 days 1:21:58.555
BugCheck 7F, {8, 80050031, 6f8, fffff80003048e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 24 12:56:34.710 2010 (GMT+12)
System Uptime: 0 days 1:03:26.302
BugCheck 7F, {8, 80050031, 6f8, fffff8000303be58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System

ultranothing · 28 Jul 2010

Hi there,

First of all, thank you - so - much. It's assistance like this that makes me feel there's hope, not just for my computer, but for humanity as well (not to sound too sappy, or anything).

It's this kind of attention that I might expect from, say, the manufacturer of the notebook which is still under warranty. Ironically, they've remained silent in response to my repeated requests for assistance. Thanks, ASUS!

Alright, Reventon, I completed all the steps for driver verifier last night. I also removed Avast!, and replaced it with Security Essentials.

Regarding the out of date driver, and the suspect module, I attempted to install the latest "Cool and Quiet" software from the manufacturers website, but the computer COMPLETELY freezes at about 50% completion, each of the three times I made the attempt.

I am no longer getting the buzzing sound before the BSOD (though we're still BSoDing), but I am noticing that when the PC is attempting to play more than one audio stream, the audio (and video) will slow down, and I can hear the remnants of the sustained springy sound, as if my PC is going into some type of time-warp.

I believe the STOP code is different. I will update this post with new DMPs within the hour.

reventon · 28 Jul 2010

ultranothing said:

Regarding the out of date driver, and the suspect module, I attempted to install the latest "Cool and Quiet" software from the manufacturers website, but the computer COMPLETELY freezes at about 50% completion, each of the three times I made the attempt.

I am no longer getting the buzzing sound before the BSOD (though we're still BSoDing), but I am noticing that when the PC is attempting to play more than one audio stream, the audio (and video) will slow down, and I can hear the remnants of the sustained springy sound, as if my PC is going into some type of time-warp.

I believe the STOP code is different. I will update this post with new DMPs within the hour.

Ok.

Re: The ASUS driver update - try installing it in Safe Mode

ultranothing · 28 Jul 2010

reventon said:

Re: The ASUS driver update - try installing it in Safe Mode

Tried. Failed. Some .DLL fails to load. Would it help to try it again and give you the specific filename?

As for the new DMPs, the system doesn't appear to be creating them. There are no dump files in the minidump folder.

From what I remember, the initial STOP code ends in C. 0009C, I want to say. The BSoD refers to a file called "iastor.sys".

Apparently, IASTOR.SYS refers to the Intel Matrix Storage Manager. I am going to update that software from the ASUS website, and report the outcome.

In the meantime, if you have any more suggestions, I'm ready...

UPDATE:

Installed the new Intel Matrix Storage Manager. BSoD's continue. Since I did the driver verifier and uninstalled Avast!, I have been getting intermittent BSoD's at start-up. Quite a few times, the system would just halt completely at the "Starting Windows" screen. The last BSoD didn't reference any specific file, but here are the codes:

0x000000C4
0x0000000000000081
0xFFFFFA800720C7C0
0x000000000000008A
0x0000000000000000

How deep IS the rabbit-hole?

Jonathan_King · 28 Jul 2010

Could you please follow these directions?

https://www.sevenforums.com/crashes-d...tructions.html

ultranothing · 29 Jul 2010

Jonathan_King said:

Could you please follow these directions?

https://www.sevenforums.com/crashes-d...tructions.html

You're in the "BSOD Squad"? I would submerge this computer in the tub, if you told me to :)

I'm on it...

Update: (Possibly important information)

The only file in my minidump folder was the RAR I had created initially of the DMPs, which were uploaded here.

The "BSOD Dump & System File Collection app", which is running now, has detected this "Minidump.rar" and has, from what I can see, copied this archive and is now in the process of "copying mini-kernel dimp(sic) files".

Assuming the app was supposed to process the actual DMP files (which were CUT, not copied, and pasted into a folder on the desktop), should I return those dump files to the minidump folder, and re-run the application?

Another update:

Since the DMP files are supposed to be in the minidump folder, I'm going to go ahead and return them to the minidump folder, and re-run the BSOD Dump & System File Collection App.

ultranothing · 30 Jul 2010

Hi,

I ran the BSoD app from step one as instructed. This may be normal, but I wanted to say that the BSoD app never actually "stopped". It stayed on the "Copying mini-kernel dump files" screen, until inevitably I'd get another BSoD.

The app did produce an output folder with quite a few files in addition to what appear to be the original dump files.

I'm running the health report now...

Update:

I've attached the JGriff folder and the HTML document from the health report. As for the system information:

- Windows 7 x64
- Re-installed version from the restore partition
- OEM
- System debuted in March 2010
- I reinstalled the OS (from the restore partition) at the beginning of
June because the system was freezing when I tried to launch newer PC games.
I suspect that the freezing was a BSoD without the blue.

I should add, that since I ran the "driver verifier" per Reventon's suggestion, It's been progressively harder to start up the system without a BSoD loop. After the most recent BSoD(about twenty minutes ago), the computer blued out and restarted itself three times, then froze at the startup logo animation screen.

I wanted to add, it seems quite a few people who purchased the ASUS Republic of Gamers G60JX-RBBX05 (BestBuy edition) have been experiencing not only rampant BSoD issues, but a substantial lack of support from the manufacturer. Appeals to various community forums from frustrated owners have yielded, from my research, mostly dead-ends and more questions than solutions. I'll do my best to see this through to the end, in the hopes that it may help others.

reventon · 30 Jul 2010

ultranothing said:

I should add, that since I ran the "driver verifier" per Reventon's suggestion, It's been progressively harder to start up the system without a BSoD loop. After the most recent BSoD(about twenty minutes ago), the computer blued out and restarted itself three times, then froze at the startup logo animation screen.

Ok, that is definitely a sign there is a driver problem here.

However, as this crash was after you ran the BSOD info collection(?) there is no record of it in any of the files.

You do not need to run the full collection application again, simply go to C:\Windows\Minidump , sort the files by date and copy any files dated newer than 07/27/10 to a zipped folder.

ultranothing · 30 Jul 2010

reventon said:

ultranothing said:

I should add, that since I ran the "driver verifier" per Reventon's suggestion, It's been progressively harder to start up the system without a BSoD loop. After the most recent BSoD(about twenty minutes ago), the computer blued out and restarted itself three times, then froze at the startup logo animation screen.

Ok, that is definitely a sign there is a driver problem here.

However, as this crash was after you ran the BSOD info collection(?) there is no record of it in any of the files.

You do not need to run the full collection application again, simply go to C:\Windows\Minidump , sort the files by date and copy any files dated newer than 07/27/10 to a zipped folder.

I haven't had a BSoD in about two hours, though it's only a matter of time. Until then, I can only say that when I'm getting the most recent BSoD's, it seems to hang at the part where it says something to the effect of "collecting" or "retrieving" or "something"...

Whatever it says, it's not creating any new dumps, and I have no records after 7/27.