You are having two distinctly different kinds of crashes. Both relate to hardware so I will list both
Quote: Originally Posted by shappzero
A few months back, my computer began blue screening upon start up (would not boot into any mode), and I had to reinstall windows. Since then, I have had daily crashes, which take the form of either (1) BSODs, (2) lockups that require a hard reboot, or (3) a "windows has stopped responding" error, followed by a lockup. This happens most frequently when I am watching Hulu, but can happen anytime, including when the computer is not in use. I don't know if it's related, but the computer (a desktop) is also having trouble connecting to my wireless network. Sometimes it will connect, but often it will refuse to find the network, or find it but fail to connect.
The computer is a 2 year-old HP desktop. Running windows 7 64-bit. Core i-7 processor.
The requested files are attached. Please let me know if I can provide any more information, and thank you very much for the help.
Best advice that I've seen about this error (from here: http://www.sevenforums.com/crashes-d...tml#post356791
What you're looking for will be in one of the following categories:
a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)
So, check the drivers
Then check the inside of the case (temperature, voltage, dust, etc).
Then run some hardware stress tests
Try this free video stress test: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Try this free stress test: Free Software - GIMPS
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.
Then try replacing parts.
Then look up the versions of your BIOS to see what changes were done.[/QUOTE]
Your .dmp file shows a stop error of 0x124 which is a general hardware error .
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.
You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try