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.

    A new XPS15 L502X user needes help!

    Discussion in 'Dell XPS and Studio XPS' started by secret365, Apr 23, 2011.

  1. secret365

    secret365 Newbie

    Reputations:
    0
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    5
    Hello All,

    I have received my new laptop few days ago.

    Whenever I run Windows Experience Index & after awhile my laptop will power down by itself.

    Anyone just received their laptop recently having this problem?

    I suspect it might be due to some driver problem & have tried various solution suggested on the web (run sf/scan, delete content in WinSAT\DataStore etc).

    I have the following specification:

    BIOS: A04
    CPU: i7-2720m
    Graphics: Nvidia GT 540M
    RAM: 8GB
    & with all drivers up to date.



    Here is my winsat log:

    6761192 (4924) - winsat\logging.cpp:0815: --- START 2011\4\24 10:18:11 AM ---
    6761192 (4924) - winsat\main.cpp:4301: Command Line = winsat formal
    6761192 (4924) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured
    6761223 (4924) - winsat\main.cpp:4474: > IsFormal=TRUE IsMoobe=FALSE.
    6761270 (4924) - winsat\main.cpp:4585: Watch dog system enabled
    6761270 (4924) - winsat\main.cpp:4600: Main watch dog timer set to 600.0 seconds
    6762752 (4924) - winsat\main.cpp:2490: > DWM Running.
    6763470 (4924) - winsat\main.cpp:2497: > turning off DWM.
    6763470 (4924) - winsat\main.cpp:2470: > EMD service will be restored on exit.
    6763485 (4924) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e'
    6763485 (4924) - winsat\main.cpp:2793: > power policy saved.
    6763563 (4924) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
    6763563 (4924) - winsat\main.cpp:2814: > power policy set to maximum.
    6765170 (4924) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance
    6765170 (4924) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE
    6765170 (4924) - winsat\main.cpp:1775: > Run Assessment features
    6765451 (4924) - winsat\main.cpp:1775: > Run Assessment dwm -aname DWM -time 10 -fbc 10 -disp off -normalw 12 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock
    6781425 (4924) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 8124640
    6781425 (4924) - winsat\main.cpp:2037: > DWM Assessment results processing SUCCESS
    6781425 (4924) - winsat\main.cpp:1775: > Run Assessment d3d -aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)
    6790052 (4924) - winsat\main.cpp:1775: > Run Assessment d3d -aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)
    6798523 (4924) - winsat\main.cpp:1775: > Run Assessment d3d -aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3
    6807634 (4924) - winsat\main.cpp:1775: > Run Assessment d3d -aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3
    6816962 (4924) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)
    6825714 (4924) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)
    6834450 (4924) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3
    6843607 (4924) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3

    Thank you for reading.
     
  2. namaiki

    namaiki "basically rocks" Super Moderator

    Reputations:
    3,905
    Messages:
    6,116
    Likes Received:
    89
    Trophy Points:
    216
    Have you tried checking CPU, GPU and other temperatures? You can use a program called HWMonitor to check
     
  3. secret365

    secret365 Newbie

    Reputations:
    0
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    5
    Hi,

    Thanks for the reply.

    I have AIDA64 on this laptop & the temperature readings are pretty normal.

    Temperatures:
    Motherboard 58 °C (136 °F)
    CPU 58 °C (136 °F)
    CPU Package 60 °C (140 °F)
    CPU IA Cores 60 °C (140 °F)
    CPU GT Cores 60 °C (140 °F)
    CPU #1 / Core #1 57 °C (135 °F)
    CPU #1 / Core #2 57 °C (135 °F)
    CPU #1 / Core #3 52 °C (126 °F)
    CPU #1 / Core #4 56 °C (133 °F)
    GPU 61 °C (142 °F)
    ST9750420AS 47 °C (117 °F)
     
  4. namaiki

    namaiki "basically rocks" Super Moderator

    Reputations:
    3,905
    Messages:
    6,116
    Likes Received:
    89
    Trophy Points:
    216
    What temperature might be reached when you run WEI?
     
  5. secret365

    secret365 Newbie

    Reputations:
    0
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    5
    Still running the test now, will crash anytime now.

    Seems normal also.

    Temperatures:
    Motherboard 77 °C (171 °F)
    CPU 77 °C (171 °F)
    CPU Package 76 °C (169 °F)
    CPU IA Cores 76 °C (169 °F)
    CPU GT Cores 76 °C (169 °F)
    CPU #1 / Core #1 72 °C (162 °F)
    CPU #1 / Core #2 75 °C (167 °F)
    CPU #1 / Core #3 76 °C (169 °F)
    CPU #1 / Core #4 66 °C (151 °F)
    GPU 65 °C (149 °F)
    ST9750420AS 47 °C (117 °F)
     
  6. DakkonA

    DakkonA Notebook Evangelist

    Reputations:
    30
    Messages:
    448
    Likes Received:
    0
    Trophy Points:
    30
    Is anything reported in Windows' Reliability Monitor for an error at the time this happens? Or failing that, in the event logs?
     
  7. secret365

    secret365 Newbie

    Reputations:
    0
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    5
    Nothing, just shows not shutdown properly.
     
  8. secret365

    secret365 Newbie

    Reputations:
    0
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    5
    I tried selecting "Integrated graphics" instead of "Auto-select" in Nvidia Control Panel & I managed to run the test for awhile before hitting this error:

    The Windows Experience Index for your system could not be computed.

    Could not measure storage performance.

    Error: Failed to properly assess the disk. The parameter is incorrect.

    An update: Contacted Dell Technical Support, will have a technician over to change the motherboard as I have no problem running Custom Hard disk Test.

    Thanks namaiki & DakkonA for the help.
    :)