Ongoing crash issues.

[Asako]

I've had various issues with crashing/rebooting, and having eliminated a few of them (Firewall being disabled hanging HomeFinder processes, and G19 issues) now I'm suffering BSOD's on boot.

I looked at the diag tool provided here, and ran it, but it didn't create a folder on my desktop as the thread stated it does, so I have no idea how to go about finding its output, and uploading the diagnostic information. I suppose that would be the place to start.

 

[Tews]

[1 - Novice] How to ask for help with a BSOD problem Summary:

If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

• Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
• Zip up the copy.
• Start your own thread in the "Crashes and Debugging" section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
• Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

 

[Asako]

Okay, here's the contents of minidump.

The issue is as outlined in the first post. I've resolved what I can with event logs and google, but the BSODs on boot aren't leaving logs so I have no idea what it may be, sans perhaps memory, but I don't see how it could be.

I built the system about a month ago, and it was running fine until a few days ago. The BSODs I'm getting on boot are something new after having resolved the other issues... I think.

Hopefully somebody who can understand the dumps can at least narrow down what is causing the latest issue.

 

[Asako]

And after another crash it appears it's not just a BSOD issue. Managed to get SF diag working so here's the complete set of files.

 

[reventon]

Hi,

BSOD Summary

[font=lucida console]
BugCheck A, {fffff80002842760, 2, 0, fffff80002ad205b}
Probably caused by : win32k.sys ( win32k!NtUserCallNoParam+19 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 109, {a3a039d89a3cc6cc, 0, 8e8a64afcceccc58, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {ffffeb8015630505, 1, fffff80002d62041, 7}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {ffffffffffffffd8, 2, 0, fffff80002a7d8eb}
Probably caused by : ntkrnlmp.exe ( nt!ExpScanGeneralLookasideList+a0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000007E, {ffffffffc0000005, fffff88000ee2001, fffff880031b6638, fffff880031b5ea0}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 109, {a3a039d899f19533, 0, c11d78233919b35d, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

At this point I am thinking hardware however I just spotted the following driver:

[font=lucida console]
[B]ASACPI.sys[/B]   Mon Mar 28 15:30:36 [COLOR=Red]2005 [/COLOR]
[/font]

It is almost guaranteed to cause BSODs in Windows 7.

Update it from the ASUS site: ASUSTeK Computer Inc.-Support-

Use this slideshow to help navigate the site (but at the final step scroll down and chose the driver for the Asus ATK0110 ACPI Utility instead of the one shown): Asus mobo utility driver updates - Windows Live

Regards,
Reventon

 

[Asako]

That driver caused a BSOD loop and I had to format and reinstall. I left the computer on overnight without issue; was fine when I woke up, but just got home to a warning about an unexpected shutdown so even after a fresh install (+updates and latest device drivers, which I already had anyway) it's still happening.

So it's likely a hardware issue, like bum RAM?

 

[reventon]

Start hardware testing with a memtest:

Memtest - Instructions:

Download the ISO (or the .exe for USB drives) from here Memtest86+ - Advanced Memory Diagnostic Tool

Then (if you have chosen the ISO) burn the ISO using ImgBurn: The Official ImgBurn Website

Boot from the CD/USB and run the test (at least 5 passes per test) with only one stick of RAM in place at a time.

It is a time consuming process but it is the only way to be sure it isn't a RAM fault.

For your final test, run the test with all the RAM in place.

 

[Asako]

Okay, memtest revealed 49 errors on the first pass, which is more than enough to RMA it and get some new stuff. Hopefully replacing it will be the last of the issue.

 

[reventon]

Ok, please let us know if the replacement RAM solved your problem.

 

[Asako]

Okay, had new RAM for a few days with no issues, then just got a bluescreen while gaming tonight. The bluescreen file reference was unfamiliar so I think it's a different issue to before, though event log says pretty much the same about unexpected shutdown etc.

This may just be a random sporadic type crash that is just part of using Windows, but I figured I'd see if anyone here has any ideas.

Dump files attached.

 

[reventon]

Hi,

BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 10 20:34:19.509 2010 (GMT+12)
System Uptime: 0 days 4:55:16.945
BugCheck 1000007E, {ffffffffc0000005, fffff88004fa6cee, fffff8800215d6a8, fffff8800215cf10}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/font]

More of the same sort of BSOD as before. This one is graphics related; there is a possibility that a graphics hardware fault caused your BSOD.

Run a graphics stress test:

FurMark Setup:
Download from here: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Of course, as you said it could be a one-off. But the BSOD looks too similar to the previous ones for my liking.

 

[Asako]

I've used furmark a bit in the past, but just doing a ten minute stability test, the temp maxed out at 75 and there were no issues.

 

[reventon]

Lets just wait and see if you get any more.