random bsod while playing games need help interprating dump files

Page 1 of 2 12 LastLast

  1. Posts : 5
    windows 7 64 bit
       #1

    random bsod while playing games need help interprating dump files


    while playing games, mainly skyrim in steam i get random bsod. somtimes after 5 mins somtimes after days? it is random. screen locks and sound goes crazy then bsod. i restart and then ok? just updated nvidia to latest drivers 1hr ago no bsod as of yet. but it was a very random bsod.

    evga 790i ultra
    e8600 @ 4.00 (has been running fine for months at this overclock, no change at default setting still bsod)
    gtx570 sli (gigabyte)
    corsair ddr3 4gig (checked with memtest, 7 passes ok)
    coolermaster 1000w gold (just updated from corsair hx750 as i thought it was psu related)
    ozc ssd 60g (os)
    wd green 1tb (steam games)

    cpu. gpu. all water cooled.. cpu max temp prime95 55c.. gpu max stress test 45-55c
    2x120mm radiator for cpu and 2x120mm radiator for gpu's 5x noctua fans 1x delta 120mm intake.. all on fan controller. heat is not and issue.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2


    These crashes were caused by memory corruption/exception (c0000005) probably your DirectX

    Also of note:: Related to RTCore64.sys MSI Afterburner from Micro-Star Int'l Co. Ltd. Yours is from 2005 and should be removed (best) or updated to a win 7 compliant version.
    .
    Please run these two tests to verify your memory and find which driver is causing the problem.


    * If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!

    * If you have raid update its Driver.




    Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    RAM - Test with Memtest86+



    Driver verifier

    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen.
    Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
    The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
    If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
      My Computer


  3. Posts : 5
    windows 7 64 bit
    Thread Starter
       #3

    still having same problem msi afterburner was on system before bsod. tried all the above still damn bsod. latest dump attached
      My Computer


  4. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #4

    Code:
    Loading Dump File [D:\Kingston\BSODDmpFiles\onaid\032812-5163-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`03413000 PsLoadedModuleList = 0xfffff800`03658e90
    Debug session time: Tue Mar 27 23:10:34.798 2012 (UTC - 6:00)
    System Uptime: 0 days 1:26:08.195
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Unable to load image \SystemRoot\system32\DRIVERS\nvmf6264.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvmf6264.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+54d14 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
    
    FAULTING_IP: 
    +3762316361366462
    00000000`00000000 ??              ???
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
    
    BUGCHECK_STR:  0x1E_0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  TESV.exe
    
    CURRENT_IRQL:  6
    
    EXCEPTION_RECORD:  fffff80000ba2248 -- (.exr 0xfffff80000ba2248)
    ExceptionAddress: fffff8800f255d14 (nvlddmkm+0x0000000000054d14)
       ExceptionCode: c000001d (Illegal instruction)
      ExceptionFlags: 00000000
    NumberParameters: 0
    
    TRAP_FRAME:  fffff80000ba22f0 -- (.trap 0xfffff80000ba22f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8004b73c68 rbx=0000000000000000 rcx=fffffa8004b73ca8
    rdx=00000000021353c0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800f255d14 rsp=fffff80000ba2480 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=fffffa8004b73c68 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz ac pe cy
    nvlddmkm+0x54d14:
    fffff880`0f255d14 ??              ???
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8000348affe to fffff80003493610
    
    STACK_TEXT:  
    fffff800`00ba1328 fffff800`0348affe : 00000000`00000001 fffffa80`06de4010 fffff800`00ba1aa0 fffff800`034bf2a0 : nt!KeBugCheck
    fffff800`00ba1330 fffff800`034bef6d : fffff800`0369aa10 fffff800`035d6c78 fffff800`03413000 fffff800`00ba2248 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff800`00ba1360 fffff800`034bdd45 : fffff800`035da028 fffff800`00ba13d8 fffff800`00ba2248 fffff800`03413000 : nt!RtlpExecuteHandlerForException+0xd
    fffff800`00ba1390 fffff800`034cedc1 : fffff800`00ba2248 fffff800`00ba1aa0 fffff800`00000000 fffffa80`00000004 : nt!RtlDispatchException+0x415
    fffff800`00ba1a70 fffff800`03492cc2 : fffff800`00ba2248 fffff800`00ba2620 fffff800`00ba22f0 fffffa80`04b72d28 : nt!KiDispatchException+0x135
    fffff800`00ba2110 fffff800`03490e1f : fffff800`00ba22f0 fffff880`0f2b9806 fffffa01`00000000 fffff880`00000000 : nt!KiExceptionDispatch+0xc2
    fffff800`00ba22f0 fffff880`0f255d14 : fffff800`00ba2620 fffff880`0ff2b0c4 00000000`00000000 fffff800`00ba2868 : nt!KiInvalidOpcodeFault+0x11f
    fffff800`00ba2480 fffff800`00ba2620 : fffff880`0ff2b0c4 00000000`00000000 fffff800`00ba2868 fffffa80`04b72000 : nvlddmkm+0x54d14
    fffff800`00ba2488 fffff880`0ff2b0c4 : 00000000`00000000 fffff800`00ba2868 fffffa80`04b72000 fffff880`0f2e721e : 0xfffff800`00ba2620
    fffff800`00ba2490 00000000`00000000 : fffff800`00ba2868 fffffa80`04b72000 fffff880`0f2e721e 00000000`00000000 : nvmf6264+0xc0c4
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+54d14
    fffff880`0f255d14 ??              ???
    
    SYMBOL_STACK_INDEX:  7
    
    SYMBOL_NAME:  nvlddmkm+54d14
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f4e68c4
    
    FAILURE_BUCKET_ID:  X64_0x1E_0_nvlddmkm+54d14
    
    BUCKET_ID:  X64_0x1E_0_nvlddmkm+54d14
    
    Followup: MachineOwner
    ---------
    Related to your graphics card driver.
    • Try re-installing DirectX using the http://www.microsoft.com/download/en...s.aspx?id=8109 and see how the system responds.

      Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

      1. Download the latest drivers for your display card(s)
      2. Click Start Menu
      3. Click Control Panel
      4. Click Uninstall a program
      5. For NVIDIA:
        • Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
        • Restart your computer
        • Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
        • If any remain of the above, uninstall one at a time
        • If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
      6. For AMD:
        • Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
        • If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
          1. Download the latest drivers for your display card(s)
          2. Click Start Menu
          3. Right Click My Computer/Computer
          4. Click Manage
          5. Click Device Manager from the list on the left
          6. Expand Display adapters
          7. Do the following for each adapter (in case you have multiple display cards)
            • Right click the adapter
            • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
            • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
          8. Restart your computer after uninstalling drivers for all display cards
          9. Install the latest driver for the display cards once Windows starts


          Alternatively:
          1. Login as an adminstrative user
          2. Download the latest drivers for your display card(s)
          3. Click Start Menu
          4. Click Control Panel
          5. Click Hardware and Sound
          6. Click Device Manager (the last link under Devices and Printers)
          7. Expand Display adapters
          8. Do the following for each adapter (in case you have multiple display cards)
            • Right click the adapter
            • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
            • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
      7. Restart your computer after uninstalling drivers for all display cards
      8. Install the latest driver for the display cards once Windows starts
    Last edited by writhziden; 02 Apr 2012 at 07:38.
      My Computer


  5. Posts : 5
    windows 7 64 bit
    Thread Starter
       #5

    ok, i formatted hdd and fresh install because after doing the above windows would not boot even in safe mode. reset bios to default, installed drivers and directx as described, about a hour into skyrim and bang bsod. help me !
      My Computer


  6. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #6

    Please follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with your full crash reports and logs. The more information we have, the better we will be able to assist you.

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [D:\Kingston\BSODDmpFiles\onaid\033012-10826-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`03457000 PsLoadedModuleList = 0xfffff800`0369ce90
    Debug session time: Fri Mar 30 07:24:05.756 2012 (UTC - 6:00)
    System Uptime: 0 days 4:34:10.239
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff800037af4a8, fffff880085d0f80, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!ObpQueryNameString+288 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff800037af4a8, Address of the instruction which caused the bugcheck
    Arg3: fffff880085d0f80, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nt!ObpQueryNameString+288
    fffff800`037af4a8 48393a          cmp     qword ptr [rdx],rdi
    
    CONTEXT:  fffff880085d0f80 -- (.cxr 0xfffff880085d0f80)
    rax=fffff8a00451e4a0 rbx=fffff8a00451e4a0 rcx=fffff8a00451e4a0
    rdx=0000075ffbb6fb20 rsi=0000000000000001 rdi=0000000000000000
    rip=fffff800037af4a8 rsp=fffff880085d1960 rbp=fffff880085d1c60
     r8=0000000000000210  r9=fffff880085d1ab8 r10=0000000000000000
    r11=000000000000000f r12=0000000000000011 r13=fffff80003457000
    r14=000000000008dfc0 r15=fffff8a00451ea20
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210202
    nt!ObpQueryNameString+0x288:
    fffff800`037af4a8 48393a          cmp     qword ptr [rdx],rdi ds:002b:0000075f`fbb6fb20=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  GameOverlayUI.
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800037af4a8
    
    STACK_TEXT:  
    fffff880`085d1960 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpQueryNameString+0x288
    
    
    FOLLOWUP_IP: 
    nt!ObpQueryNameString+288
    fffff800`037af4a8 48393a          cmp     qword ptr [rdx],rdi
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!ObpQueryNameString+288
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a
    
    STACK_COMMAND:  .cxr 0xfffff880085d0f80 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpQueryNameString+288
    
    BUCKET_ID:  X64_0x3B_nt!ObpQueryNameString+288
    
    Followup: MachineOwner
    ---------

    If a clean install did not resolve the problem, it is likely hardware related.
    • Monitor temperatures during the following tests.
      Use the following programs to monitor the temperatures.


    • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

      If you swap any memory components, follow these steps for ESD safety:
      1. Shut down and turn off your computer.
      2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
      3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
      4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.

      Once these steps have been followed, it is safe to remove and replace components within your computer.



    I also see a possible out of date driver:
    Code:
    nvm62x64	fffff880`03f94000	fffff880`03ff7d80	Fri Oct 17 15:01:06 2008 (48f8fd12)	0006f977		nvm62x64.sys
    nvm62x64.sys


    Again: Please follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with your full crash reports and logs. The more information we have, the better we will be able to assist you.
      My Computer


  7. Posts : 5
    windows 7 64 bit
    Thread Starter
       #7

    ok here we go.....
    memtest86... 8 passes ok. no error reported..
    furmark.. 1/12 hrs 57c max gpu temp solid. i have always monitored gpu temps.
    gpu memtest.. both cards passed. wich is what i expected, but when running prime95 in the first 20mins i got hardware error test stopped see stress.txt but i could not find the file? cpu temp max 56c then after closing prime95 and opening internet explorer BANG bsod.... aaaaarrrrrrgggghhhhh i have attatched system report, html, and latest dump.

    note, bsod happend after all the testing just while browsing in internet explorer.
      My Computer


  8. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #8

    stress.txt (Overclockers Australia Forums - View Single Post - Prime95 stress.txt file ???)

    STRESS TESTING YOUR COMPUTER

    BACKGROUND
    ----------

    Today's computers are not perfect. Even brand new systems from major
    manufacturers can have hidden flaws. If any of several key components such
    as CPU, memory, cooling, etc. are not up to spec, it can lead to incorrect
    calculations and/or unexplained system crashes.

    Overclocking is the practice of increasing the speed of the CPU and/or
    memory to make a machine faster at little cost. Typically, overclocking
    involves pushing a machine past its limits and then backing off just a
    little bit.

    For these reasons, both non-overclockers and overclockers need programs
    that test the stability of their computers. This is done by running
    programs that put a heavy load on the computer. Though not originally
    designed for this purpose, this program is one of a few programs that
    are excellent at stress testing a computer.


    RESOURCES
    ---------

    This program is a good stress test for the CPU, memory, L1 and L2 caches,
    CPU cooling, and case cooling. The torture test runs continuously, comparing
    your computer's results to results that are known to be correct. Any
    mismatch and you've got a problem! Note that the torture test sometimes
    reads from and writes to disk but cannot be considered a stress test for
    hard drives.

    You'll need other programs to stress video cards, PCI bus, disk access,
    networking and other important components. In addition, this is only one
    of several good programs that are freely available. Some people report
    finding problems only when running two or more stress test programs
    concurrently. You may need to raise prime95's priority when running two
    stress test programs so that each gets about 50% of the CPU time.

    Forums are a great place to learn about available stability test programs
    and to get advice on what to do when a problem is found.

    The currently popular stability test programs are (sorry, I don't have
    web addresses for these):
    Prime95 (this program's torture test)
    3DMark2001
    CPU Stability test
    Sisoft sandra
    Quake and other games
    Folding@Home
    Seti@home
    Genome@home

    Several useful websites for help (look for overclocking community or forum):
    Overclockers: The Performance Computing Community for Overclocking Hardware and How to Overclock Information
    Ars Technica
    HARDOCP - HardOCP Computer Hardware Reviews and News
    AnandTech
    Tom's Hardware: Hardware News, Tests and Reviews
    PC Overclocking, Modding and Building | Sharky Extreme
    Also try the alt.comp.hardware.overclocking Usenet newsgroup.

    Utility programs you may find useful (I'm sure there are others - look around):
    Motherboard monitor from livewiredev.com - dowload music Resources and Information.
    Memtest86 from Memtest86.com - Memory Diagnostic
    Cpuburn by redelm: http://pages.sbcglobal.net/redelm/
    TaskInfo2002 from Iarsn - High Quality System Software


    WHAT TO DO IF A PROBLEM IS FOUND?
    ---------------------------------

    The exact cause of a hardware problem can be very hard to find.

    If you are not overclocking, the most likely cause is an overheating CPU
    or memory DIMMs that are not quite up to spec. Another possibility is
    you might need a better power supply. Try running MotherBoard monitor
    and browse the forums above to see if your CPU is running too hot.
    If so, make sure the heat sink is properly attached, fans are operational,
    and air flow inside the case is good. For isolating memory problems, try
    swapping memory DIMMs with a co-worker's or friend's machine. If the errors
    go away, then you can be fairly confidant that memory was the cause of
    the trouble. A power supply problem can often be identified by a significant
    drop in the voltages when prime95 starts running. Once again the overclocker
    forums are a good resource for what voltages are acceptable.

    If you are overclocking then try increasing the core voltage, reduce the
    CPU speed, reduce the front side bus speed, or change the memory timings
    (CAS latency). Also try asking for help in one of the forums above - they
    may have other ideas to try.


    CAN I IGNORE THE PROBLEM?
    -------------------------

    Ignoring the problem is a matter of personal preference. There are
    two schools of thought on this subject.

    Most programs you run will not stress your computer enough to cause a
    wrong result or system crash. If you ignore the problem, then video games
    may stress your machine resulting in a system crash. Also, stay away from
    distributed computing projects where an incorrect calculation might cause
    you to return wrong results. Bad data will not help these projects!
    In conclusion, if you are comfortable with a small risk of an occasional
    system crash then feel free to live a little dangerously! Keep in mind
    that the faster prime95 finds a hardware error the more likely it is that
    other programs will experience problems.

    The second school of thought is, "Why run a stress test if you are going
    to ignore the results?" These people want a guaranteed 100% rock solid
    machine. Passing these stability tests gives them the ability to run
    CPU intensive programs with confidence.


    FREQUENTLY ASKED QUESTIONS
    --------------------------

    Q) My machine is not overclocked. If I'm getting an error, then there must
    be a bug in the program, right?

    A) The torture test is comparing your machines results against
    KNOWN CORRECT RESULTS. If your machine cannot generate correct
    results, you have a hardware problem. HOWEVER, if you are failing
    the torture test in the SAME SPOT with the SAME ERROR MESSAGE
    every time, then ask for help at mersenneforum.org - it is
    possible that a recent change to the torture test code may have
    introduced a software bug.

    Q) How long should I run the torture test?

    A) I recommend running it for somewhere between 6 and 24 hours.
    The program has been known to fail only after several hours and in
    some cases several weeks of operation. In most cases though, it will
    fail within a few minutes on a flaky machine.

    Q) Prime95 reports errors during the torture test, but other stability
    tests don't. Do I have a problem?

    A) Yes, you've reached the point where your machine has been
    pushed just beyond its limits. Follow the recommendations above
    to make your machine 100% stable or decide to live with a
    machine that could have problems in rare circumstances.

    Q) A forum member said "Don't bother with prime95, it always pukes on me,
    and my system is stable!. What do you make of that?"

    or

    "We had a server at work that ran for 2 MONTHS straight, without a reboot
    I installed Prime95 on it and ran it - a couple minutes later I get an error.
    You are going to tell me that the server wasn't stable?"

    A) These users obviously do not subscribe to the 100% rock solid
    school of thought. THEIR MACHINES DO HAVE HARDWARE PROBLEMS.
    But since they are not presently running any programs that reveal
    the hardware problem, the machines are quite stable. As long as
    these machines never run a program that uncovers the hardware problem,
    then the machines will continue to be stable.

    Do you have security software installed? If not, recommend one of these two:
    Run a full scan with your security software after getting the updates for it.


    Your .dmp file is pointing to a hardware issue. What were the error messages from Prime95?
      My Computer


  9. Posts : 5
    windows 7 64 bit
    Thread Starter
       #9

    cant find log file (stress.txt) that prime95 said to veiw after hardware fault found? did a search no result? where dose prime95 store this file
      My Computer


  10. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #10

    Prime95 has to be fully installed on the system for stress.txt to be created. All stress.txt contains is information about what to do if a hardware fault is found. I included the information it gives in the Quote in my previous post.
      My Computer


 
Page 1 of 2 12 LastLast

  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 17:01.
Find Us