BSOD trouble


  1. Posts : 2
    Windows 7 Ultimate
       #1

    BSOD trouble


    A copy of the DMP is included.

    I've been using windows 7 for quite a while now with no problems, however I recently installed a new GPU (Powercolor 5850) and everything was working perfectly fine until a few days ago.

    It's only happened twice but twice seems more than a slight hitch, the symptoms are as follows :

    The first time it happened I was using the map editor for Far Cry 2, out of nowhere the sound hitched and the pc froze up, the whole screen being covered in "streaks" of colour from the actual part of the game I was looking at, the streaks look liked a ribbed sweater all the way across the screen vertically.

    The second time I was playing Stalker Call of Pripyat, the same thing happened after about an hour the sound hitched, the screen was covered in the same vertial ribbed sweater pattern, this time again another colour of the game I was currently looking at ( in far cry 2 it was a brown sand colour in stalker a green swampy colour )

    I would hazard a guess that it's the GPU, but before this all happened I had gone into my bios to change some RAM timings, after the first BSOD however, I went back and set them all to default.

    Due to it happening a second time I don't think it could be that but I'm not so sure.
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    This appears to be a hardware issue (or a compatibility issue). It's a STOP 0x124 error (more info on solutions here: https://www.sevenforums.com/crash-loc...-what-try.html )

    How recently was the graphics card installed (a couple of days might be significant, a couple of weeks is probably not significant)?
    What changes have you made to the BIOS settings? Please revert to the default values (no overclocking) while trying to troubleshoot the BSOD's.

    As it looks like a video issue, please try this free, video stress test:
    Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
    FurMark Setup:
    - If you have more than one GPU, select Multi-GPU during setup
    - In the Run mode box, select "Stability Test" and "Log GPU Temperature"
    Click "Go" to start the test
    - Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
    - Click "Quit" to exit
    Summary of the BSOD:
    Code:
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Debug session time: Fri May 21 10:50:45.349 2010 (GMT-4)
    System Uptime: 0 days 0:00:17.128
    BugCheck 124, {0, 8649f8fc, 0, 0}
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_GenuineIntel
    PROCESS_NAME:  System
      My Computer


  3. Posts : 2
    Windows 7 Ultimate
    Thread Starter
       #3

    The card was installed literally 4 days ago, there were no problems until yesterday. All bios settings are back to default I made sure of that today.

    I ran the furmark test and the temperature wouldn't go higher than 70 degrees.
    Last edited by maso; 22 May 2010 at 15:23.
      My Computer


  4. Posts : 712
    Windows 7 x64, Windows XP SP3, Fedora
       #4

    Given the recentness of the GPU install I would suggest that you swap out the card and see what happens.
      My Computer


  5. Posts : 5,705
    Win7 x64 + x86
       #5

    Since ensuring that the settings were set to default, have you had any problems?
    The Furmark test stresses your video card - so it appears that the stress isn't related to that (unless changing the settings to default was done before running Furmark).

    Regardless, try this free system stress test to be sure:
    Try this free stress test: Free Software - GIMPS
    Prime95 Setup:
    - 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.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:31.
Find Us