Many BSOD's without any specific reason

Hi!
First of all, sorry for my English, it's not my first language :).
To the point- specs of my comp- AMD Phenom II X2 550 (no OC), 4 Gb Memory (Kingston), Geforce GTX 260 (latest drivers), Chieftec 600W, Windows 7 Professional 64 Bit. From time to time, without any specific reason, I've got BSOD's. I realise that often (but not always) they are connected with watching films or playing games (recently for instance Diablo 3). Sometimes BDSOD's occur 5 times during one day and sometimes I have they off my head for 2 weeks. I tested my hardware with Memtest, Orthos, Prime95 and some other programs- can't remember their names- no errors at all. Here are my dumps file. Can someone help me out?
Thanks in advance
Simon

Code:

ASACPI	fffff880`06aa6000	fffff880`06aae000	Sun Mar 27 20:30:36 2005 (42476c4c)	00003c77		ASACPI.sys

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.)

Thanks to JMH and zigzag3143 for the above information.

I did, but the problem still exists. Moreover, now I get a message (after 20-40 minutes) that critical error has occured and the system will be restarted within 1 minute (or sth like that).

Please upload your latest crash reports by following the https://www.sevenforums.com/crashes-d...tructions.html for us to analyze.

Well, so here's my last .dmp file. May you analyze it?

Please upload your latest crash reports by following the https://www.sevenforums.com/crashes-d...tructions.html for us to analyze.

Sorry for misunderstanding, there it is.

Problem Devices:

Code:

Niedostępne	ACPI\ATK0110\1010110	The drivers for this device are not installed.

The above is very important to have installed for your system to operate properly. I actually gave a link to the updated driver for it in a previous post; it is the ASACPI.sys driver.

Please fill in your system specs in your profile and not in a post in this thread: System Info - See Your System Specs


You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through Stop 0x124 - what it means and what to try and use the following hardware checks to supplement that link.

• 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 Hardware - Stress Test With Prime95 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
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Remember to read closely through Stop 0x124 - what it means and what to try for the crash.