New
#1
Semi-random freezes BSOD 0x0000124
Hello there!
So this problem is getting really old.
I had my computer for more than two years and it war running fine and dandy all the time pretty much.
After the last format I decided to move to Windows 7 64 bit from Windows XP 32 bit with the addition of 2GB of ram extra.
Here is the current computer specs:
System: Microsoft Windows 7 Professional 64bit
CPU: Intel Core 2 Duo E8400 3.0 Ghz
Motherboard: ASUS P5QL-EM
Memory: 2x OCZ Gold XTC OCZ2G8002G (2GB)
Graphics Card(s): NVIDIA GeForce 275 GTX (896 MB)
Sound Card: Realtek ALC1200 @ Intel 82801JB ICH10 - High (Integrated)
Hard Drives: SAMSUNG HD322HJ ATA Device (320 GB, 7200 RPM, SATA-II)
PSU: OCZ StealthXStream 500W SLI
Case: Asus TA-863 Black
Cooling: Arctic Cooling Alpine 7 Pro PWM
Soon after the system was up and running I started encountering this strange problem which is bugging me since January.
Here's what's hapening:
The system is runnig smoothly basicly all the time. It doesn't strutter or overheat or crash. I can run most of program without any problems (Office, Firefox, Solid Works). The problem only occurs whan playing certain games OR when playing certaing games with the addition of voice chat communication (like Mumble, Ventrilo, Team Speak).
Originally the crashes where most frequent while playing Battlefield 3, but I simply decided my system might be too weak to handle that game so I switched back to Minecraft (which I've played no problem on Windows XP) and boy when I was suprised when it froze.
The freezes are compleate and total. Everything stops and none of the keybord input is working (Caps lock, Num lock, etc.), I can only push the rest button and nothing else.
Games that crash the computer:
Battlefield 3 + Mumble
Minecraft + Mumble, or Minecraft + Modpack (Technic pack)
Assasins Creed Refelations
Blacklight Revolution
Games that DO NOT crash the computer:
World of Tanks (even with Mumble on)
Civilization V
NBA 2k12
Saint's Row The Third (it froze once or twice with mumble but not all the time)
Minecraft without Mumble (it works stable around 95% of the time WITHOUT voice comm.)
Suprisingly this freeze/crash happens without any BSOD all the time.
So the proccess of debugging this freezes is allready long.
I've started by running any benchmarks I've found in google (related to the problem) so I did Memtest, Prime, 3D Mark, etc. The only thing I ruled out is the memory (I've tried using only one sticks and trying both the new ones, and the old ones in each DIMM slot it crashed everytime no matter the configuration).
I also updated any drivers possible starting form NVIDIA and ending with updating all motherboard drives, and the BIOS as well. Still nothing helped.
After a lot of Driver related checks and updates I finally managed to create a BSOD after running the computer in clean and alert mode (with the minimal number of drivers and procceses), BSOD 0x00000124.
Here are all the dumps I've created back then:
Attachment 230663
EDIT: Also forgot about this thing:
Attachment 230662
After that I was adviced to send my computer to a computer service for repairs. I've send but after a week of troubleshooting and benchmarkig the computer returned to me with only a replaced CMOS battery and a note "Problem not found computer is working properly".
So ATM I'm puzzled what to do I was thinking of getting some new computer parts (like a new processor) but I need to know which one is the faulty one to actually change it.
This is what I've tried also trying to make it go away:
- Update Graphics Drivers
- Update Motherboard Drivers
- Update Sound Card Drivers
- Update Chipset Drivers
- Update BIOS
- Reinstalling Punkbuster (Battlefield 3 related)
- Reinstalling, updating JAVA 32 bit and 64 bit (Minecraft related)
- Running games "As Administrator"
- Allocating more RAM for games (Minecraft related)
- Benchmarking
- Browsing the Event Viewer for potential problems
- Overclock the proccesor
- Underclock the proccesor
- Upping Voltages on proccesor
- Upping VOltages on memory
That's all I can think of. I hope somone could pinpoint at least the faulty hardware part (if it's hardware), but ATM I'm absolutely out of ideas on what to do next.
HELP PLEASE!
P.S. I hope my spelling wasn't that tragic...
Last edited by Kamradziejtomal; 08 Sep 2012 at 05:42.