Blue screen, hardware problem?

Two different BSOD's pointing to 2 different Windows drivers. I'd suspect that this is a hardware issue - but with only 2 BSOD's it's hard to verify that "pattern".

So, I'd suggest running these hardware tests as you have time:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

*****
Additional tests for certain specific circumstances:
Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Try this free stress test: Free Software - GIMPS

Also, run this to check your file system:

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

Then, please update this driver: ath2425.sys Thu Jan 25 21:15:05 2007
This is a component of your wireless network device.

Then, to see if this is a driver issue, please run Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

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

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

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the memory dumps:

Code:

Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Fri Jan 29 20:04:31.336 2010 (GMT-5)
System Uptime: 0 days 0:17:10.008
BugCheck A, {ffffffe4, 2, 0, 828d9869}
Probably caused by : cng.sys ( cng!GatherRandomKey+272 )
DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Fri Jan 29 20:07:10.416 2010 (GMT-5)
System Uptime: 0 days 0:02:05.009
BugCheck 1000007E, {c0000005, 88655678, 8a997b50, 8a997730}
Probably caused by : cdrom.sys ( cdrom!RequestSetupMcnRequest+5e )
DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO
PROCESS_NAME:  System

Have you been overclocking anything? if you don't know what that means, it won't be the cause.
The first dump file has the error IRQL_NOT_LESS_OR_EQUAL, that is usually an overheating problem. Download CPU-Z to monitor your CPU temps, and monitor while running this program. Tell us the highest temps you get. Doing this might reproduce the blue screen, and if it does we will give some information on what to do. This first BSOD was caused by 'halmacpi.dll'. Using the CHKDSK command as usasma mentioned can fix this corruption if the solution mentioned above doesn't reproduce anything.

The second dump file is related to your drivers not being updated, of which one specific one was mentioned by usasma, and also one called 'Wdf01000.sys'.

Hope me and usasma solve your error :)

that is extremely high temperatures!
IntelBurn test would only say you didn't past the if your system crashed or bluescreened again.
That would be the problem causing irql_not_less_or_equal error.
Okay, we need to know your system specification (and be prepared to spend some money) and you can do it here.
We need to know the socket of your CPU so we can give you a link to a decent cooler.

Okay, here is a cooler that you will need to install. With this item, instructions will be included with how to install it.
That was an American site, here is a UK site for a similar cooler.
(Remember to remove your stock cooler first, if you have one.)
Extra cooling is vital in your situation, make sure there is good airflow throughout your case, and clean off any dust around components that you see. Make sure to unplug your computer before doing any of this, and ground yourself so no static electricity (killers) goes through your components.

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).
Copy/paste the results into your next post.

Otherwise, go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Navigate to the Windows Logs and then to the Application log file
Right click on the Application Log File and select "Save all events as..."
And save the log to your desktop. Then zip it up and upload/attach it to your next post.
We'll search it for the words "chkdsk" once it's uploaded.

The memory dump file is a Verifier Enabled Minidump (which is good), and it points to USBPORT.SYS (which isn't so good). We were verifying 3rd party drivers with Driver Verifier - yet Driver Verifier points to a Windows component. When this happens it usually points to a hardware error.

Since you're experiencing overheating (thanks to Lil' Domii's excellent work for uncovering this), I'd have to suggest waiting until the overheating is fixed before working on the BSOD's any further. Keep an eye on your temp's - as that may be the clue to the BSOD's (increased temps may = increased numbers of BSOD's)

Here's a summary of the latest BSOD:

Code:

Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sun Jan 31 20:53:14.156 2010 (GMT-5)
System Uptime: 0 days 0:00:09.765
BugCheck 1000008E, {c0000005, 82a4994a, 873953bc, 0}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_RegisterDeviceInterface+35 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System