New
#1
Intermittent BSOD when playing SWTOR, stop error 0x124
I am getting BSOD, usually when playing SWTOR. It occurs randomly during the game, sometimes just a minute or two into the game and other times I may be able to play for over an hour.
I have recieved 2 BSOD messages:
IRQL_NOT_LESS_OR_EQUAL
Uncorrectable Hardware Error
One of the error codes I wrote down was:
stop: 0x00000124 (0x0000000000000000 0xFFFFFA80093E1028 0x00000000FE200000 0x0000000000021136)
another I wrote down was
stop: 0x00000124 (0x0000000000000000 0xFFFFFA80040C7028 0x00000000FE200000 0x0000000000021136)
I have also recieved BSOD during these tasks:
Running the Windows Experience Index assessment (a couple of times)
Once when running Furmark gpu test
A few times when shutting the system down (after a driver installation I think. I am guessing that a new WEI assessment is run by the OS during shut down after graphics driver install so may be thats why?)
I do beleive that the error occurred at least once during a mundane task, but in general I have had no stability problems during usual tasks such as surfing the web, using office software etc.
Yes, I have noticed that all of these tasks involve graphics so that is where my hunch lies. I have done my best to eliminate other possibilities (I will explain), but right now I believe I am down to the MOBO, CPU, and the PSU.
This is my second custom build (first for myself). Here's my specs:
(New Build - just over a month)
Windows 7 Pro
Intel 3570k CPU
MSI Z77 MPOWER MOBO
8 GB (2x4GB) GSkill Ripjaws Z DDR3 @ 2400 Mhz (PC3 19200)
Mushkin Chronos Deluxe 240 GB SSD
Rosewill HIVE-650W PSU
Rosewill BLACKHAWK Case
Using Intel HD Graphics 4000 Integrated Graphics (for now)
Stock Intel CPU Fan/Heatsink (for now)
5 stock case fans
Dell 1702FP @ 1280/1024
Removed overclocking (for now).
Temps typical in the 40's C, w/ spikes up to the low 60's. According to my research and RealTemp, TJMax is 105. When I tried a mild overclock prime 95 got it up to 80C so I decided to wait on overclocking until I got a better CPU heatsink/fan
TROUBLE HISTORY:
After I initially installed the OS, I used the MSI Live Update software to update all the drivers, downloaded all the Windows 7 updates, etc, and I started using the system. The BSOD problem may have occured ONCE early on but was disregarded as a one time glitch, which never really happened again until much later when I decided to download and install a game - SWTOR.
The system always starts up and runs just fine, until I start playing the game.
I tried reinstalling the game a couple of times. Still BSOD.
I tried removing any overclock (just the mild auto-overclock from MSI's OC Genie software) just in case it was some stability issue. Still BSOD.
Some message boards from others w/ BSOD problems seemed to indicate memory, so I tried checking all the memory BIOS settings. After the initial build I had some trouble figuring out how to manipulate the BIOS options to get the RAM to run at 2400 Mhz (the "Click BIOS" interface was new to me), but I ended up disabling the Intel XMP memory setting, and just leaving it on "auto" so now the RAM I paid extra for is running at just 1600 Mhz until I figure out this BSOD. Still BSOD.
Then I just reset the BIOS to all default settings to ensure it was not some setting that was out of order. Still BSOD.
Eventually, I tried installing every driver listed on MSI's website in order to resolve the problem. I installed every other windows update that hadn't been installed yet (including the optional ones, just in case) Still intermittent BSOD during game.
Since it was a new install anyway and I have all my data backed up on an external I figured I should just reinstall the OS clean. I tried installing only the bare minimums for the game to run - the driver for the LAN, the graphics driver from MSI, and the game itself. Still BSOD.
I figured that this was now going to be really time consuming and it would be just worth it let a pro look at it for $39 at the local PC repair shop. He said he ran all these tests and what not but could not get it to BSOD. He also said he checked PSU voltages. He said the only thing he found was that there was a later driver for the GPU from intel (the generic drivers) and that I should try that. I pointed out to him that all the other drivers were not up to date because I had just tried a clean install to resolve the problem, but that I previously had all the drivers p to date. He also asked if I was using an old keyboard becuase "there was this one time" and gave me a story about an old keyboard. It just so happpened that I was actually using a 10 year old Dell PS2 keyboard, so I was open to this being a possibilty and tried using my new wireless keyboard. He felt the system was ok and that I should just try getting the latest driver, and use a different keyboard maybe. I also installed the latest intel driver. Still BSOD (within 10 minutes of getting it home!).
MEMORY:
Ran Windows memory tests - NO ERRORS.
I've tried running HCI Memtest overnight to 2000% (yes 2000) - NO ERRORS.
I've tried running the game with just one stick of RAM in, then switched to the other. BSOD w/ BOTH.
Also tried one stick of ram in the other mem slot (just in case it was the slot on the board). Still BSOD.
HD/SSD:
Ran Chkdsk - No ERRORS.
Called Mushkin. Confirmed firmware is the latest. Installed latest mobo/controller driver from intel. Installed Crystal Disk Info - Helath = Good 100%.
Still BSOD.
CPU:
Tried installing and running Intel's Processor Diagnostic Tool. Passed.
As of right now I have tried several clean installs with just one graphics driver installed at a time since there is the old one from MSI (on the disc), the newest one from MSI's website, and the generic ones from Intel. I was theorizing that installing them on top of one another, one was not being installed or uninstalled and somehow screwing things up. I have even tried all the drivers that "Driver Max" recommends in case there was something I had missed (or that MSI had missed).
I don't have alternate/spare components to swap out with and really physically eliminate anything 100% (or else I probably would have figured this out myself by now) so the best I can really offer is all this info and stop error codes and the file from the "SF Diag tool".
I really appreciate any help I can recieve here from those with greater experience than I, or really anyone that actually read this entire diatribe...