The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Blue Screen of Death!

    Discussion in 'Gaming (Software and Graphics Cards)' started by Haxed, May 17, 2013.

  1. Haxed

    Haxed Notebook Consultant

    Reputations:
    1
    Messages:
    180
    Likes Received:
    0
    Trophy Points:
    30
    Hey guys, I've got a MSI GT60 and everytime I try to play a game e.g. starcraft, LoL, Knight Online the game has these black lines running across the screen and eventually crashes. I was just playing Starcraft II and it suddenly gave me a Pagefault in Nonpaged Area BSOD. When I go on to Windows 8 problem detection it gives me the following message. Anybody any ideas? I have a GTX 675MX no overclocking or anything Laptops only about two weeks old!

    Description
    A problem with your video hardware caused Windows to stop working correctly.

    Problem signature
    Problem Event Name: LiveKernelEvent
    OS Version: 6.2.9200.2.0.0.768.101
    Locale ID: 1033

    Files that help describe the problem
    WD-20130517-2212.dmp
    sysdata.xml
    WERInternalMetadata.xml

    View a temporary copy of these files
    Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

    Extra information about the problem
    BCCode: 141
    BCP1: FFFFFA8007AE14D0
    BCP2: FFFFF88005622AB8
    BCP3: 0000000000000000
    BCP4: 0000000000000930
    OS Version: 6_2_9200
    Service Pack: 0_0
    Product: 768_1
     
  2. Haxed

    Haxed Notebook Consultant

    Reputations:
    1
    Messages:
    180
    Likes Received:
    0
    Trophy Points:
    30
    I've also noticed that in GPU-Z and System Information it says my GTX 675MX only has 1024MB of RAM,when its supposed to be 2GB of ram. Could this be the problem?
     
  3. MrDJ

    MrDJ Notebook Nobel Laureate

    Reputations:
    2,594
    Messages:
    10,832
    Likes Received:
    363
    Trophy Points:
    501
    hi
    could you load and run Resplendence Software - WhoCrashed, automatic crash dump analyzer and post the dump report on here.
    also is there any chance you can get a picture of the lines on the screen as lines to us rings alarm bells of dying graphics card but as its only 2 weeks old im guessing its not that and could just be a bad or corrupt driver.

    what sort of temperatures are you getting with gpu/cpu

    if i were you i would download hwinfo64 from my signature below and that will give the best information about your gpu and the 1024mb ram. it will also show temperatures.
     
  4. ryzeki

    ryzeki Super Moderator Super Moderator

    Reputations:
    6,547
    Messages:
    6,410
    Likes Received:
    4,085
    Trophy Points:
    431
    Use monitoring software and update drivers. It can be a bad GPU that is dying. I had one that worked for about 5 mins before crashing, freezing screen then recovered. Days later the GPU died completely and could no longer see its device or use monitoring software.
     
  5. Haxed

    Haxed Notebook Consultant

    Reputations:
    1
    Messages:
    180
    Likes Received:
    0
    Trophy Points:
    30
    CPU & GPU Temps are never high. Not sure about the corrupt driver thing, it happened from day 1 of getting the laptop, and has had multiple fresh installs, fresh installations of three difference types of drivers, and I've tried turning every nvidia setting on and off to see if anything changes but nothing ever happens.

    Below are two videos of the problem

    League of Legends GFX ERROR - YouTube
    GFX ERROR In 3D Game - YouTube

    Here is the crash dump as well
    Crash Dump.png
     
  6. MrDJ

    MrDJ Notebook Nobel Laureate

    Reputations:
    2,594
    Messages:
    10,832
    Likes Received:
    363
    Trophy Points:
    501
    off the top of my head, im not sure. hopefully others can come up with things to try.

    that crash dump doesnt mean a thing to me so thats why i asked could you rum who crashed as that gives a much more detailed report.
     
  7. Haxed

    Haxed Notebook Consultant

    Reputations:
    1
    Messages:
    180
    Likes Received:
    0
    Trophy Points:
    30
    That dump was from that program you told me to use :/
     
  8. MrDJ

    MrDJ Notebook Nobel Laureate

    Reputations:
    2,594
    Messages:
    10,832
    Likes Received:
    363
    Trophy Points:
    501
    really, this is what it should look like

    On Sun 05/05/2013 18:41:37 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\050513-18392-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
    Bugcheck code: 0xA (0x1, 0x2, 0x0, 0xFFFFF8000309BA55)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    what you posted is this http://forum.notebookreview.com/att...2d1368881662-blue-screen-death-crash-dump.png
     
  9. Haxed

    Haxed Notebook Consultant

    Reputations:
    1
    Messages:
    180
    Likes Received:
    0
    Trophy Points:
    30
    Now I get you! Thanks! here it is

    On Fri 17-May-13 9:12:58 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\051713-12656-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
    Bugcheck code: 0x50 (0xFFFFFAA127002710, 0x0, 0xFFFFF8028830A3D4, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Fri 17-May-13 9:12:58 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x50 (0xFFFFFAA127002710, 0x0, 0xFFFFF8028830A3D4, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 12-May-13 2:40:57 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\051213-13000-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
    Bugcheck code: 0x50 (0xFFFFFAC218002440, 0x0, 0xFFFFF801FD6A31F4, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 11-May-13 11:50:37 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\051113-11390-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
    Bugcheck code: 0x19 (0x3, 0xFFFFF8A006491E00, 0x5F53360062583C, 0xFFFFF8A006491E00)
    Error: BAD_POOL_HEADER
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a pool header is corrupt.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
     
  10. MrDJ

    MrDJ Notebook Nobel Laureate

    Reputations:
    2,594
    Messages:
    10,832
    Likes Received:
    363
    Trophy Points:
    501
  11. Haxed

    Haxed Notebook Consultant

    Reputations:
    1
    Messages:
    180
    Likes Received:
    0
    Trophy Points:
    30

    Tried all of that already, I think its something to do with the GPU RAM. I guess I'll just send it back for repair and see what they say...just hoping they don't overlook it as its quite a hard problem to find unless you actually use the computer for a while