BSOD playing TERA online, error 0x0000007e

Page 1 of 2 12 LastLast

  1. Posts : 8
    Windows 7 Ultimate x64
       #1

    BSOD playing TERA online, error 0x0000007e


    um, hello, this is the first post of mine here, so please go easy on me :)
    to the main point, i recently re-installed my windows into Windows 7 x64 and currently having a few times BSOD while playing TERA online, which is never happened before (using Windows 7 x86).

    First BSOD happened with error code 0x0000003b, and i try to resolve it myself by reading a similar thread here. From what i read the problem is caused by graphic driver, some of programs like MSI Afterburner and OC then i removed the program as the suggestion said, restore the default system, run disk check, executing command line sfc /scannow, also update the graphic driver.

    i thought everything is back to normal again, then suddenly approximately an hour, another BSOD come with code 0x0000007e when i was playing TERA, and that make me desperate and post here.

    please help me to resolve this problem, thank you for your time and attention :)




    Operating System : Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1(7601.win7sp1_gdr.110622-1506)
    Processor : Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz (8 CPUs), ~3.1GHz
    Memory : 4096MB RAM
    Card Name : NVIDIA GeForce GTX 460
    Manufacturer : NVIDIA
      My Computer


  2. Posts : 1,735
    Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
       #2

    So it appears that your graphics card/ graphics card river is at fault here:

    Code:
    fffff880`069ef008  fffff880`0491149dUnable 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
     nvlddmkm+0xb849d
    Driver Reference Table - nvlddmkm.sys


    It does indeed seem to have the latest driver so lets do some stress testing to make sure that the problem does not lie in the GPU its self, or that it is not over heating:

    Furmark:
    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" (BurnIn test in newer versions).
    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
    Keep an eye on the temperatures, and report them here if they go above 80c then chances are there is a heat issue, if the test simply causes a crash like you have been experiencing, then it may be a problem with the GPU simply having a hardware level error.

    If the Furmark test goes alright try running OCCT , start from the second part of the tutorial to test the dedicated memory on the GPU for defects, and post the graphs that the program generates here if it does not cause a crash:

    NVIDIA/AMD Video Card - Test with OCCT
      My Computer


  3. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #3

    thank you for your reply, i'll do what you suggest and give the result immediately :)
      My Computer


  4. Posts : 1,735
    Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
       #4

    I look forward to your resluts.
      My Computer


  5. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #5

    EDIT: another question, how long i must run the BurnInTest? and OCCT is? the second button beside the "Burn In" ?
    i tried to run it and the reached 80c + i added warning sounds to notify me about the temperature mark
    then should i link the log files here?
      My Computer


  6. Posts : 1,735
    Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
       #6

    For the furmark, run the test untill the tempearature maxes out, or untill you get errors. In OCCT you need to select GPU: memtest and then press the on button, set the passes to anywhere between 5 and 7 passes
      My Computer


  7. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #7

    Dsprague said:
    For the furmark, run the test untill the tempearature maxes out, or untill you get errors. In OCCT you need to select GPU: memtest and then press the on button, set the passes to anywhere between 5 and 7 passes
    i have run the test for 6minutes, and the temp did not pas 80c, it stop right at 80c.
    No problem during the test, i'll update you with the OCCT test in a few minutes
    thank you for your quick reply, i really appreciate that :)
      My Computer


  8. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #8

    UPDATE: i have tested with OCCT with 7 passes, and no problem too,
    here i link you the graph result, i'll try to play again tonight and tomorrow to test if there's still BSOD happen
    if not, i'll mark this problem as solved :)

    UPDATE 2: i have run the test again for 15minutes mark, no BSOD, the temperature reach 80c sometimes 81c but never went beyond there.
    Another information, i have un-installed few programs such as ROGCfospeed+GameBooster (active when the BSOD occured), Winamp, PowerISO after the 0x7e code BSOD happened. Any chance these programs are the main cause of BSOD? Because before everything (with x86) works smoothly, without any problem.
    Last edited by skycloud04; 17 May 2013 at 09:52.
      My Computer


  9. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #9

    UPDATE 3: the BSOD occur again, this time is 0x3B code here i link the dump files
    hope you can help, thank you for your time
      My Computer


  10. Posts : 1,735
    Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
       #10

    OK it looks like this dump is blaming memory corruption, so please do the following:

    Run memtest86+ for 7-9 passes (do this over night it can take a long time):

    RAM - Test with Memtest86+

    Reset your page file:

    Use this technique to "reset" your pagefile:
    a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
    -Then click on the Advanced tab,
    -then on the Performance Settings Button,
    -then on the next Advanced tab,
    -then on the Virtual Memory Change button.
    b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
    -Then click on the "No paging file" radio button, and
    - then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
    -Click OK to exit the dialogs.
    c ) Reboot (this will remove the pagefile from your system)
    d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
    e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.
    Run the system file checker to clear up any file system corruption:

    SFC.EXE /SCANNOW
    Go to Start and type in "cmd.exe" (without the quotes)
    At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
    In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
    IF the command finishes with anything other than "no integrity violations found" run the command two more times
    If after the third run of the command there are still messages about corrupt files follow this tutorial to run the command at boot: SFC /SCANNOW : Run in Command Prompt at Boot
      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 01:47.
Find Us