Random BSOD on my MSI GT70 2OC


  1. Posts : 3
    Windows Pro 64bit
       #1

    Random BSOD on my MSI GT70 2OC


    Hello !

    I have my computer since January, it's a MSI GT70 2OC : MSI Global GT70 2OC

    And I have a lot of random BSOD since that time =/
    I've tried a lot of things about my drivers and memory test but I would like to check everything from the beginning with you please.

    Here's some information about my actual conf :

    OS : Windows 7 Professionnel (X64) (build 7601) Service Pack 1
    Core : Intel Core i7 4700MQ 2.40 GHz (Haswell)
    Motherboard : Micro-Star International Co., Ltd. MS-1763 REV:0.C
    GPU : NVIDIA GeForce GTX 770M
    Chipset : Intel HM87 Chipset

    Thank you very much.

    PS: I will do a memtest before going to bed.
    Last edited by Linkinou; 19 Apr 2014 at 11:44. Reason: upload informations
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Various alternative error codes.

    This one indicates to a driver bug, but difficult to say which driver is bugging out.
    Code:
    BugCheck C4, {91, 0, fffff8000304ccc0, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4884 )
    
    Followup: MachineOwner
    ---------
    This one indicates that some USB drivers are failing.
    Code:
    BugCheck D1, {161c31c7, 2, 0, fffff88005211986}
    
    Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_UsbDoneDpc_Worker+266 )
    
    Followup: MachineOwner
    ---------
    A hint of memory corruption is there.... not necessarily the physical RAM.
    Code:
    BugCheck A, {2758, d, 0, fffff80002ce53fe}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
    
    Followup: MachineOwner
    ---------
    And, hardware issue, though which part of hardware is issuing is not detected.
    Code:
    BugCheck A, {ffffffffffffff8f, d, 0, fffff80002ce663d}
    
    Probably caused by : hardware ( nt!KiPageFault+260 )
    
    Followup: MachineOwner
    ---------
    So better we start with hardware testing.

    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.
    If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

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

    Stress test the CPU.
    Hardware - Stress Test With Prime95

    Do one more thing.


    Because it is failing, too.

    Code:
    fffff800`00b9c788  fffff880`06b9a623Unable to load image \SystemRoot\system32\DRIVERS\Ak27x64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Ak27x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Ak27x64.sys
     Ak27x64+0x2a1623
    Let us know the results.
      My Computer


  3. Posts : 3
    Windows Pro 64bit
    Thread Starter
       #3

    Hello !

    Thank you for answering.

    Memtest86+
    Got errors during the first 5 seconds of the test.

    GPU test
    Worked for 10 minutes, no artifacts and the temperature was stuck around 88C.

    CPU test
    Running in progress but I have to work on my computer so I will do it again during the night. For now, it has been 1 hour and I've already got one error in the worker 5 : "FATAL ERROR: Rounding was 0.5, expected less than 0.4"

    And I'm installing the driver just after that.

    Thank you again
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    Linkinou said:
    Hello !

    Thank you for answering.

    Memtest86+
    Got errors during the first 5 seconds of the test.
    Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

    Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

    How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
    How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

    No code has to be inserted here.
    It is a RAM, a bad RAM.

    But if you have got a result like that:

    No code has to be inserted here.
    It is a motherboard issue. The particular slot is bad.

    Linkinou said:
    GPU test
    Worked for 10 minutes, no artifacts and the temperature was stuck around 88C.
    No problem with the GPU then. :)

    Linkinou said:
    CPU test
    Running in progress but I have to work on my computer so I will do it again during the night. For now, it has been 1 hour and I've already got one error in the worker 5 : "FATAL ERROR: Rounding was 0.5, expected less than 0.4"
    Sounds bad. It seems that the CPU is failing, too. Does it hehave the same even in the other run?

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

    Linkinou said:
    And I'm installing the driver just after that.

    Thank you again
    Welcome. But I am not very happy seeing the hardware failures.
      My Computer


  5. Posts : 3
    Windows Pro 64bit
    Thread Starter
       #5

    Arc said:
    Sounds bad. It seems that the CPU is failing, too. Does it behave the same even in the other run?
    I will do it again tonight and will let him work for more hours. And I will let you know.

    Arc said:
    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .
    No, the computer is not hot at all, even when I'm playing video games, which is pretty cool comparing to my last computer. But I will give you a screenshoot of Speccy just in case

    Arc said:
    Welcome. But I am not very happy seeing the hardware failures.
    So do I haha, hopefully it's a new computer I will use my guarantee and send it back to MSI when I will go back to France.

    Something strange for me is that, according to BlueScreenView, I had no blue screens between 26/03/2014 and 07/04/2014 which was fantastic for me x) But I started updating my graphic cards drivers on the 26 and the blue screens strike again... =/

    Anyway, since I have hardware failures, I should send it back :'(.
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    If you can send the computer back and get a replacement, that will be the best!

    And, BluescreenView is not a very trustworthy program, when you can use Debugging tools for windows.
      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 08:18.
Find Us