BSOD while playing Tera

[wheelsonbus]

Brief summary, asus laptop 1 month old, Installed windows 7 because f wondows 8. Computer would just turn off at random. Fresh install, has stopped it from doing that.

Now when I play an online game (tera) dont judge me, I get the blue.

I have an extra 4 gig stick of a different brand, I have ran memest numerous times in different ways. etc.

first post, let me know if I didnt do something right.

 

[Arc]

Your crash dumps are not showing any finite probable cause.

In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
__________________________________________________________________________
BSOD ANALYSIS:

BugCheck D1, {fffffa800f36e534, 2, 1, fffff880105d1291}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_SetUSBDError+5 )

Followup: MachineOwner
--------------------------------------------------------------------------------------
BugCheck 50, {fffff900c26ba060, 1, fffff80002c9a09f, 0}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
-------------------------------------------------------------------------------------------
BugCheck 109, {a3a039d89f8925d7, 0, 839e585252652659, 101}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

 

[wheelsonbus]

Thanks for the reply I will try this and report back.

 

[wheelsonbus]

OK, so I enabled driver verifier twice and it failed to get to desktop twice. I have attached the updated zip.

 

[Arc]

Even the verifier enabled minidumps are silent about any driver that is causing the crash. So we have to search the reason in the hardware. Let us start testing the hardware.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results when done.

 

[wheelsonbus]

I just got it to boot into desktop after trying the verifier again. Shall I see how this plays out before testing the ram?. This forum is awesome btw.

 

[Arc]

OK, have another try.

 

[wheelsonbus]

just ran the cpu test, and got this message on core three


[Jun 6 17:18] Worker starting
[Jun 6 17:18] Setting affinity to run worker on logical CPU #3
[Jun 6 17:18] Beginning a continuous self-test to check your computer.
[Jun 6 17:18] Please read stress.txt. Choose Test/Stop to end this test.
[Jun 6 17:18] Test 1, 9000 Lucas-Lehmer iterations of M7998783 using AVX FFT length 400K, Pass1=320, Pass2=1280.
[Jun 6 17:19] Test 2, 9000 Lucas-Lehmer iterations of M7798785 using AVX FFT length 400K, Pass1=320, Pass2=1280.
[Jun 6 17:20] Test 3, 9000 Lucas-Lehmer iterations of M7798783 using AVX FFT length 400K, Pass1=320, Pass2=1280.
[Jun 6 17:21] Test 4, 11000 Lucas-Lehmer iterations of M7471105 using AVX FFT length 400K, Pass1=320, Pass2=1280.
[Jun 6 17:23] Test 5, 11000 Lucas-Lehmer iterations of M7471103 using AVX FFT length 400K, Pass1=320, Pass2=1280.
[Jun 6 17:24] Test 6, 11000 Lucas-Lehmer iterations of M7377889 using AVX FFT length 400K, Pass1=320, Pass2=1280.
[Jun 6 17:25] Test 7, 11000 Lucas-Lehmer iterations of M7277887 using AVX FFT length 400K, Pass1=320, Pass2=1280.
[Jun 6 17:26] Test 8, 11000 Lucas-Lehmer iterations of M7077889 using AVX FFT length 400K, Pass1=320, Pass2=1280.
[Jun 6 17:27] Test 9, 11000 Lucas-Lehmer iterations of M7077887 using AVX FFT length 400K, Pass1=320, Pass2=1280.
[Jun 6 17:29] Test 10, 11000 Lucas-Lehmer iterations of M6984673 using AVX FFT length 400K, Pass1=320, Pass2=1280.
[Jun 6 17:30] Test 11, 11000 Lucas-Lehmer iterations of M6884671 using AVX FFT length 400K, Pass1=320, Pass2=1280.
[Jun 6 17:31] Test 12, 11000 Lucas-Lehmer iterations of M6684673 using AVX FFT length 400K, Pass1=320, Pass2=1280.
[Jun 6 17:33] Test 13, 11000 Lucas-Lehmer iterations of M6684671 using AVX FFT length 400K, Pass1=320, Pass2=1280.
[Jun 6 17:34] Self-test 400K passed!
[Jun 6 17:34] Test 1, 34000 Lucas-Lehmer iterations of M2605473 using AVX FFT length 128K, Pass1=128, Pass2=1K.
[Jun 6 17:35] Test 2, 34000 Lucas-Lehmer iterations of M2584313 using AVX FFT length 128K, Pass1=128, Pass2=1K.
[Jun 6 17:36] Test 3, 34000 Lucas-Lehmer iterations of M2573917 using AVX FFT length 128K, Pass1=128, Pass2=1K.
[Jun 6 17:37] Test 4, 34000 Lucas-Lehmer iterations of M2540831 using AVX FFT length 128K, Pass1=128, Pass2=1K.
[Jun 6 17:38] Test 5, 34000 Lucas-Lehmer iterations of M2539613 using AVX FFT length 128K, Pass1=128, Pass2=1K.
[Jun 6 17:39] Test 6, 34000 Lucas-Lehmer iterations of M2495213 using AVX FFT length 128K, Pass1=128, Pass2=1K.
[Jun 6 17:39] FATAL ERROR: Rounding was 0.5, expected less than 0.4
[Jun 6 17:39] Hardware failure detected, consult stress.txt file.
[Jun 6 17:39] Torture Test completed 18 tests in 20 minutes - 1 errors, 0 warnings.
[Jun 6 17:39] Worker stopped.


all other cores are working still. What does this mean, should I send my laptop in for warranty service?


edit: 10 mins later core four did the same

 

[Arc]

all other cores are working still. What does this mean, should I send my laptop in for warranty service?


edit: 10 mins later core four did the same

The CPU is not functioning properly. So it is the best option to use the warranty