Constant freeze? Bsod? :(


  1. Posts : 12
    Windows 7 Enterpris x64
       #1

    Constant freeze? Bsod? :(


    It's been months from my last reply, but i finally bought a new video card installed it and removed the old one.
    I'm still getting the same bsod constantly

    Computer specs:

    Custom made, 1 year old
    windows 7 x64
    Full retail windows 7

    i switched from a nvidia geforce 260
    to a nvidia geforce 450.

    here is the problem in detail

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.4
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 124
    BCP1: 0000000000000000
    BCP2: FFFFFA8004B4C8F8
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    I've also did a ram test, and its not the ram.
      My Computer


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

    I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
    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: Free Online AntiMalware Scanners (read the details at the link)
    STOP 0x124 error troubleshooting here: Stop 0x124 - what it means and what to try

    Only running the 2011 memory dumps, there is a 2 month gap between the 2010 and 2011 memory dumps (Dec & Jan). Will post back with results

    Please visit Windows update and get all available updates. Then install SP1 (It'll be under the Important Updates).

    Here's my spiel about wireless USB devices:
    I do not recommend using wireless USB devices.
    These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
    An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.
    I do not recommend using wireless USB devices.
    These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
    An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.
    MSINFO32 report is missing. Please do the following:
    MSINFO32:
    Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
    Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.

    If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.
      My Computer


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

    16 memory dumps over a 17 day period
    15 are STOP 0x124, 1 is a STOP 0x116
    This is most probably a hardware issue associated with the video sub-system on your computer.
    The STOP 0x124 errors seem to point to a bus error, so I'd have to wonder about the motherboard in this case.

    Since you've replaced the video card, we can rule that out as a cause.
    Your nVidia chipset drivers are outdated (from 2009). I'd suggest updating them from the nVidia website here: NVIDIA DRIVERS 15.49 WHQL

    OLDER DRIVERS PRESENT IN THE DUMP FILES
    - Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system. Reference links included below.
    - DO NOT use Windows Update or the Update Drivers function of Device Manager.
    - Please feel free to post back about any drivers that you are having difficulty locating.
    - Windows Update exceptions may be noted below for Windows drivers:
    Code:
    
    nvrd64.sys        Tue Jun 30 20:21:14 2009 (4A4AABFA)
    nvstor64.sys      Tue Jun 30 20:21:51 2009 (4A4AAC1F)
    amdxata.sys       Tue May 19 13:56:59 2009 (4A12F2EB)
    dump_nvstor64.sys Tue Jun 30 20:21:51 2009 (4A4AAC1F)
    dump_storport.sys Mon Jul 12 23:32:05 2010 (4C3BDE35)
    MpFilter.sys      Tue Sep 14 20:19:28 2010 (4C901110)
    nvsmu.sys         Mon Jun 29 03:36:37 2009 (4A486F05)
    LMouFilt.Sys      Tue Nov 10 06:46:23 2009 (4AF9528F)
    LHidFilt.Sys      Tue Nov 10 06:46:17 2009 (4AF95289)
    GEARAspiWDM.sys   Mon May 18 08:17:04 2009 (4A1151C0)
    nvhda64v.sys      Thu Nov 11 18:10:36 2010 (4CDC77EC)
    RTKVHD64.sys      Tue Oct 06 06:51:17 2009 (4ACB2125)
    netr28ux.sys      Mon May 25 00:38:17 2009 (4A1A20B9)
    MpNWMon.sys       Tue Sep 14 20:19:30 2010 (4C901112)
    nvmf6264.sys      Thu Aug 12 07:46:06 2010 (4C63DEFE)
    NisDrvWFP.sys     Tue Sep 14 20:20:25 2010 (4C901149)
    
    http://www.carrona.org/dvrref.html#nvstor64.sys
    http://www.carrona.org/dvrref.html#amdxata.sys
    http://www.carrona.org/dvrref.html#dump_nvstor64.sys
    http://www.carrona.org/dvrref.html#MpFilter.sys
    http://www.carrona.org/dvrref.html#nvsmu.sys
    http://www.carrona.org/dvrref.html#LMouFilt.Sys
    http://www.carrona.org/dvrref.html#LHidFilt.Sys
    http://www.carrona.org/dvrref.html#GEARAspiWDM.sys
    http://www.carrona.org/dvrref.html#nvhda64v.sys
    http://www.carrona.org/dvrref.html#RTKVHD64.sys
    http://www.carrona.org/dvrref.html#netr28ux.sys
    http://www.carrona.org/dvrref.html#MpNWMon.sys
    http://www.carrona.org/dvrref.html#nvmf6264.sys
    http://www.carrona.org/dvrref.html#NisDrvWFP.sys
    Let us know how the above stuff works out.

    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Fri Mar  4 10:54:46.908 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:09.687
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`04b4c8f8 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Thu Mar  3 21:45:42.208 2011 (UTC - 5:00)
    System Uptime: 0 days 5:33:32.597
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+7b723c )
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    BUGCHECK_STR:  0x116
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    Bugcheck code 00000116
    Arguments fffffa80`048fd160 fffff880`1063623c ffffffff`c000009a 00000000`00000004
    BiosVersion = V1.1
    BiosReleaseDate = 09/28/2009
    SystemManufacturer = MSI
    SystemProductName = MS-7612
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Thu Mar  3 10:45:48.300 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:09.689
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`04b4a8f8 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Wed Mar  2 15:52:22.003 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:09.392
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`0554f4f8 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Mon Feb 28 21:42:45.738 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:09.127
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`054e04f8 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Mon Feb 28 18:09:31.598 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:08.987
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`055438f8 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Sun Feb 27 18:42:52.942 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:07.722
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`054cc8f8 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Sun Feb 27 08:17:36.958 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:08.347
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`0550a668 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Sun Feb 27 02:49:51.017 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:09.796
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`05571038 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Fri Feb 25 18:25:07.187 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:10.966
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`055a78f8 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Mon Feb 21 19:32:35.158 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:10.547
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`055a08f8 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Thu Feb 17 18:55:33.159 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:08.938
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`054731d8 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Thu Feb 17 18:34:25.220 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:10.609
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`04b368f8 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Wed Feb 16 22:44:57.317 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:08.706
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`054c68f8 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Feb 16 15:20:44.560 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:12.965
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`04b108f8 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Feb 16 14:37:17.827 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:11.606
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`056068f8 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      My Computer


  4. Posts : 12
    Windows 7 Enterpris x64
    Thread Starter
       #4

    sorry for the late reply here is my msinfo.32

    thank you for the help i've done a memtest and i've passed 7 test with no fails, i;ll give the hd diagnostic a try later.

    What do you think is the main problem?
      My Computer


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

    This is just a guess, but I think it's either your video card, the slot that the card plugs into on the motherboard, or some other component on the motherboard. The video card isn't as likely because you've replaced it - but we have to consider all possibilities. Don't forget that compatibility issues or malware can also cause these types of errors.

    A while back I had to install a huge video card into a small Dell case. That card gave me a STOP 0x124 error when I booted it up - so I removed and reseated the card and the error went away.

    And, there is a problem with a device on your motherboard named the Trusted Platform Module (from the MSINFO32 report).
    Trusted Platform Module 1.2 ACPI\IFX0102\1 This device cannot start.
    There is a setting in your BIOS that enables TPM support, and there's a set of pins on the motherboard to attach a TPM module (and it references a TPM security platform manual)
    Beyond that, I have no clue what this device does or if it's causing your problems. I'd first try disabling it in the BIOS to see if it goes away. It is a security device, so make sure that you're adequately protected before disabling it.

    MSINFO32 also shows a pile of STOP 0x116 and STOP 0x117 errors in the past - and they are related to your video drivers. But, they appear to have gone away since 04 Sep 2010 (when there were 24 BSOD's in the same day).

    After completing the above diagnostics, then we can start on the system stress tests:
    FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in 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).
    NOTE: Set the alarm to go off at 90║C. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
    - Click "Quit" to exit
    Prime95 download site: 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 please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
    - "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).
    This won't necessarily crash the system - but check the output in the test window for errors.
    The Test selection box and the stress.txt file describes what components that the program stresses.
    More details on the use of this test: Torture test your CPU with Prime95
    Two other video stress tests (may be more stressful than FurMark):
    Video Memory stress Test - ╨Ь╨Ш╨ NVIDIA / ╨г╤В╨╕╨╗╨╕╤В╤Л / VMT
    Artifact Locator - ╨Ь╨Ш╨ NVIDIA / ╨г╤В╨╕╨╗╨╕╤В╤Л / Artifact Locator
    Sorry, but I don't read the language that this website is made in.
    Another interesting test that just came to my attention: Download - OCCT Website english
    USE AT YOUR OWN RISK - program doesn't have a whole bunch of safety features to protect you from yourself!
      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 04:13.
Find Us