Solved Crashes during various PC actions.

[Salamandrex]

Yeah wasn't sure if one would be created since windows didnt fully load. So wanted to share the info. I'll get on posting the ststem health and all that. Hopefully my computer will allow me. Seems like running JCGRIFF2 gets me to freeze more often then everyday tasks. Last time I checked my temps
CPU was running around 35 and gpu 37 with just firefox running.

 

[Salamandrex]

No, that seemed like just a one time thing hopefully. Also on my BSOD's half the time the screen freezes on it and it doesn't finish. Is this indicitive of something or what can cause the corrupted .dmp files?

 

[Salamandrex]

Systemhealth along with the JCGRIFF.

 

[Salamandrex]

Sorry about the flood of posts, wasn't sure when I would get another freeze. Here are the CC cleaner files.

 

[writhziden]

The fact that it is freezing can indicate a number of things: A failing hard disk, faulty memory, overheating hardware, other faulty hardware (CPU, PCI card, graphics card, etc.), etc.

Basically, I would suggest that you run some hardware checks.

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest

Also, when you ran SeaTools, did you run all but the advanced tests including the SMART test?


Older versions of ASACPI.SYS are a known BSOD problem on Windows 7. Update the driver by:

1. Going to the Asus motherboard support site
   When you reach the website:
2. Scroll down the page and click Utilities
3. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
4. Search for "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" (without quotes)
5. Download and install the driver.
6. After installation is complete, verify that it installed correctly.
   • Click Start Menu
   • Click My Computer
   • Go to C:\WIndows\System32\drivers\
   • Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)

 

[karlsnooks]

Those three files look good.

I do suggest:
WIN | type MSCONFIG | ENTER | STARTUP tab
uncheck ALL except for:

MSC    "c:\Program Files\Microsoft Security Client\msseces.exe" -hide -runkey

REBOOT!

A very high priority for you is to update the ASACPI.SYS driver as recommended by writhziden. Be sure to use the procedure which he gave.

 

[Salamandrex]

Thanks guys. I'm going to have to get off for the night but tomorrow I'll update and run the test. As for the seatools scan I only did the long scan. I'll do the extra test tomorrow. Any others in particualr I should run?

 

[writhziden]

Run all but the advanced tests. There is a short self test, a short generic test, a SMART test, and a long generic test. Run all four (five if you include information) Basic tests.

 

[Salamandrex]

Running stress tests today. Just thought I'd give you an idea of my temps when running prime 95. I have monitored temps before this because that was my main suspect, overheating, but nothing really was I maxed out my temp on my GPU at around 55 and cpu around 50 while playing games at max settings. Which I believe is in the right area correct? Obviously the tests coming up will tell for sure, I was just curious.

 

[Salamandrex]

Another thing of note that I've stated before but may have been looked over is that when the crashes started happening a weird static noise would emit from my headphone if it was plugged into the front jack. The noise is also permanently there ever since the crashes started if the volume is turned up enough, it's just a static noise that plays constantly. Is this unrelated and a common problem that just happened to show up at the same time

 

[writhziden]

Temperatures look fine. How did the tests themselves go? Any problems found? Any crashes during tests that could be recreated by running the same test?

The noise issue is common with unexpected crashes. It is probably unrelated. However, you may want to re-install your Audio drivers. The device can be found in Device Manager under Sound, video and game controllers.


To fully re-install a driver, use the following steps.

1. First, download the latest driver. Then do the next steps.
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Find the device you are trying to uninstall by expanding the appropriate set of devices
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer only if Windows asks you to.
11. Install the latest driver for the device.

Alternatively:

1. Login as an adminstrative user.
2. First, download the latest driver. Then do the next steps.
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Find the device you are trying to uninstall by expanding the appropriate set of devices
8. Right click the device
9. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
10. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
11. Restart your computer only if Windows asks you to.
12. Install the latest driver for the device.

 

[Dave76]

Do the crashes happen with the headphone disconnected?

While testing you should disconnect all non-essential external devices.
Anything not necessary for the basic function of your computer, all USB devices, external drives.
If you have a keyboard and mouse with different connectors, try them for testing purposes, if you have a wireless keyboard and mouse try using a PS2/USB wired keyboard and mouse.

From your system event log:
There are a lot of these errors.

Event[17]:
  Log Name: System
  Source: Microsoft-Windows-PNRPSvc
  Date: 2012-06-19T22:53:46.000
  Event ID: 102
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Josh-PC
  Description: 
The Peer Name Resolution Protocol cloud did not start because the creation of the default identity failed with [COLOR="Red"]error code: 0x80630801[/COLOR].

Common Return Codes

PEER_E_CERT_STORE_CORRUPTED
The Identity Store has been corrupted. Delete idstore.sst from the %appdata%\peernetworking folder.
Value: 0x80630801

Error 0x80630801 - The Identity Store has been corrupted. Delete idstore.sst from the C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking.
The file will be recreated correctly when the PNRP service is started up again.
This may be the result of what's causing your crashes and not the cause, should be corrected anyway.

Your last crash was:

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
Arguments:
Arg1: fffff80001acbeaa, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff80001acbeaa, address which referenced memory
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d03100
GetUlongFromAddress: unable to read from fffff80002d031c0
 fffff80001acbeaa Nonpaged pool
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

This is usually caused by a device driver, but can be induced by hardware itself.
Let us know the results from the hard drive and CPU tests.
If they come back clean, run memtest86+ on each RAM card.

These are 'Unloaded Modules' that need to be considered.

Unloaded modules:
fffff880`06fe3000 fffff880`06feb000   drmkaud.sys - Microsoft DRM audio descrambler file
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00008000
fffff880`06fe1000 fffff880`06fe3000   MSPQM.sys - MS Proxy Quality Manager
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00002000
fffff880`06fdf000 fffff880`06fe1000   MSTEE.sys - WDM Tee/Communication Transform Filter
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00002000
fffff880`06fdc000 fffff880`06fdf000   MSKSSRV.sys - MS KS Server
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00003000
fffff880`06fda000 fffff880`06fdc000   MSPCLOCK.sys - MS Proxy Clock
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00002000
fffff880`06f65000 fffff880`06fbf000   atikmpag.sys - ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0005A000
fffff880`06229000 fffff880`06d23000   atikmdag.sys - ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00AFA000
fffff880`03d8b000 fffff880`03de5000   atikmpag.sys - Same as above
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0005A000
fffff880`0628f000 fffff880`06d89000   atikmdag.sys - Same as above
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00AFA000
fffff880`03d8b000 fffff880`03d95000   atdcm64a.sys - ATI DSM Dynamic Driver
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000A000
fffff880`019b6000 fffff880`019c4000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`019c4000 fffff880`019d0000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`019d0000 fffff880`019d9000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
fffff880`019d9000 fffff880`019ec000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000

Re-install your Audio drivers as recommended by writhziden, be sure to get the latest version.
Which ATI Radeon graphics driver are you using?
Update to the latest stable version, install drivers only do not install the Catalyst Control Center and only install the Display Driver.

Did you update the ASACPI driver mentioned in post #65 by writhziden?
ASACPI.sys Mon Mar 28 10:30:36 2005
This is out of date and known to cause crashes.

Update this Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC driver from your Asus drivers website.
Rt64win7.sys Thu Feb 26 17:04:13 2009

What anti-virus are you using?

spldr.sys    Tue May 12 00:56:27 2009
spsys.sys    Tue May 12 01:20:58 2009

 

[Salamandrex]

Updated the asacpi driver and have been good so far for several hours now. Ran prime95 and everything passed after a while of testing. Will be doing more tests today. I'm using MSE as an anti-virus and latest graphics drivers as suggested before.

 

[karlsnooks]

Excellent!
Thanks for the update.

 

[Salamandrex]

I ran the seatools test and it came back ok after the basic then the short. I came back 5 minutes after to then start up the long and my display froze like it normally does when running windows. This is the first time a freeze has occured outside of windows for me which I believe means its hardware related? Not sure about it but I thought this information was relevant. Going to try the long test again and see what happens. (the freeze did not happen during active testing) Just wanted to make sure that was clear.

 

[Dave76]

Your right, the freeze outside of Windows indicates a hardware issue.

Just for reference, what are your Power Plan settings?
How to Change the Power Plan Settings in Windows 7

If your HDD tests are clean, then run memtest86+ tests.
RAM - Test with Memtest86+

 

[Salamandrex]

Can't seem to get the furmark page to load for some reason. But HDD scans came back fine. I've run memtest before and it came back clean but to make sure i'll give it another run overnight

 

[Dave76]

Most of the time you'll need to run memtest86+ a couple of times to be sure the RAM is not causing the problem.
Always a good idea to check other things as well, if the problem is elusive then testing the RAM again is recommended.

Let us know the results.

 

[karlsnooks]

Salamandrex,
Since you have a Seagate drive, then burn SeagateforDos to a CD/DVD, insert the CD, Power off your computer with the CD inserted, Boot from the CD.

Run the SeaGate extended test.
http://www.seagate.com/staticfiles/support/seatools/SeaToolsDOS223ALL.ISO
SeaTools | Seagate

 

[Salamandrex]

The scan came back fine the two times I've ran it. I can try again if you'd like. Again memtest froze after 4 passes this time without the blinking light just like the one of the seatools scan. Does that indicate a video card problem? Or something causing the pc to freeze.