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.

    Running Furmark + Prime95 At The Same Time on NP8230 (P151SM1)

    Discussion in 'Sager and Clevo' started by I'm Poor, Sep 14, 2013.

  1. I'm Poor

    I'm Poor Notebook Consultant

    Reputations:
    20
    Messages:
    135
    Likes Received:
    5
    Trophy Points:
    31
    It keeps switching to battery when I run both at the same time and the screen brightness is changing too (obviously because it''s switching to battery-only). Is this normal?

    Edit: BTW, after I did this, the 2nd mSATA dropped to SATA II. This system has so many strange issues.
     
  2. MrDJ

    MrDJ Notebook Nobel Laureate

    Reputations:
    2,594
    Messages:
    10,832
    Likes Received:
    363
    Trophy Points:
    501
    wowza. me thinks you are overloading it running two heavy stress tests at the same time.
    ive never heard this been done before so if its causing problems and you keep doing it me thinks it will end in tears and expensive tears at that.
     
  3. baii

    baii Sone

    Reputations:
    1,420
    Messages:
    3,925
    Likes Received:
    201
    Trophy Points:
    131
    The psu is overloaded.
     
  4. I'm Poor

    I'm Poor Notebook Consultant

    Reputations:
    20
    Messages:
    135
    Likes Received:
    5
    Trophy Points:
    31
    I read it here that people were doing it to stress test. I've been getting BSOD at random for light games. Wanted to see what's going on.
     
  5. MrDJ

    MrDJ Notebook Nobel Laureate

    Reputations:
    2,594
    Messages:
    10,832
    Likes Received:
    363
    Trophy Points:
    501
    really, first ive heard of it.

    download who crashed from my sig below and copy/post the bsod dump reports on here.

    also when was the last time you cleaned your vents and fans out with compressed air. what temps are you getting for cpu/gpu
     
  6. Meaker@Sager

    Meaker@Sager Company Representative

    Reputations:
    9,436
    Messages:
    58,194
    Likes Received:
    17,909
    Trophy Points:
    931
    Also does your charger behave oddly when these crashes happen? Does the power LED go off on it?
     
  7. I'm Poor

    I'm Poor Notebook Consultant

    Reputations:
    20
    Messages:
    135
    Likes Received:
    5
    Trophy Points:
    31
    I clean everything regularly. I last cleaned it two days ago. My temps are solid, even under stress tests. GPU around 79 max running Furmark at 1920x1080 and CPU around 84 degrees running Prime95. I've had all different kinds of BSOD's since I got this new motherboard. I've reinstalled so many times though so I don't have all the dumps. But every BSOD has had a completely different message.

    This was the last one that was recorded:

    Code:
    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    CPU: GenuineIntel Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Intel586, level: 6
    8 logical processors, active mask: 255
    RAM: 17096249344 total
    VM: 2147352576, free: 1935200256
    
    
    
    
    --------------------------------------------------------------------------------
    Crash Dump Analysis
    --------------------------------------------------------------------------------
    
    Crash dump directory: C:\Windows\Minidump
    
    Crash dumps are enabled on your computer.
    
    On Sat 9/14/2013 4:06:30 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\091413-4929-01.dmp
    This was probably caused by the following module: usbport.sys (USBPORT+0x15D68)
    Bugcheck code: 0xD1 (0xFFFFFFFFC88B084A, 0x2, 0x1, 0xFFFFF88005373D68)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\usbport.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: USB 1.1 & 2.0 Port Driver
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    
    
    
    
    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------
    
    One crash dump has been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
    
    
    Read the topic general suggestions for troubleshooting system crashes for more information.
    
    Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
    
    The charger always made random electrical noises though, kind of whining, buzzing sound. But I had contacted Sager about it at least a month ago and they said it was normal to make some noise so I just sent in the laptop (requested motherboard swap along with some other issues I wanted resolved). I never noticed anything unusual from the power LED, but I never really observed it as it was crashing.
     
  8. Meaker@Sager

    Meaker@Sager Company Representative

    Reputations:
    9,436
    Messages:
    58,194
    Likes Received:
    17,909
    Trophy Points:
    931
    Have a look since if the LED goes out then I would blame the charger.

    You do tend to get electrical hum since they are analogue parts.
     
  9. I'm Poor

    I'm Poor Notebook Consultant

    Reputations:
    20
    Messages:
    135
    Likes Received:
    5
    Trophy Points:
    31
    BSOD again:

    Code:
    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    CPU: GenuineIntel Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Intel586, level: 6
    8 logical processors, active mask: 255
    RAM: 17096249344 total
    VM: 2147352576, free: 1932529664
    
    
    
    
    --------------------------------------------------------------------------------
    Crash Dump Analysis
    --------------------------------------------------------------------------------
    
    Crash dump directory: C:\Windows\Minidump
    
    Crash dumps are enabled on your computer.
    
    On Mon 9/16/2013 3:08:09 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\091513-5787-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
    Bugcheck code: 0xA (0xFFFFFA804D069C70, 0x2, 0x1, 0xFFFFF8000308F929)
    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 that cannot be identified at this time.
    
    
    
    On Sat 9/14/2013 4:06:30 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\091413-4929-01.dmp
    This was probably caused by the following module: usbport.sys (USBPORT+0x15D68)
    Bugcheck code: 0xD1 (0xFFFFFFFFC88B084A, 0x2, 0x1, 0xFFFFF88005373D68)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\usbport.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: USB 1.1 & 2.0 Port Driver
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    
    
    
    
    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------
    
    2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
    
    
    Read the topic general suggestions for troubleshooting system crashes for more information.
    
    Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
    
     
  10. Support.3@XOTIC PC

    Support.3@XOTIC PC Company Representative

    Reputations:
    1,268
    Messages:
    7,186
    Likes Received:
    1,002
    Trophy Points:
    331
    Definitely could be overloading the AC Adapter. This is the exact reason why you can get two of them on the NP9570, someone ran two intensive programs at the same time like Furmark and Prime95 which caused the AC Adapter to trip so the solution was to offer two of them.
     
  11. ajnindlo

    ajnindlo Notebook Deity

    Reputations:
    265
    Messages:
    1,357
    Likes Received:
    87
    Trophy Points:
    66
    Er, is this normal? I assume they can't all be overloaded this easily? As for the AC adaptor, I would think a 60Hz buzz is normal. Maybe some clicking some times.
     
  12. Meaker@Sager

    Meaker@Sager Company Representative

    Reputations:
    9,436
    Messages:
    58,194
    Likes Received:
    17,909
    Trophy Points:
    931
    No, if anything it should just throttle a bit.
     
  13. cavell219

    cavell219 Notebook Evangelist

    Reputations:
    37
    Messages:
    562
    Likes Received:
    338
    Trophy Points:
    76
    Most likely the laptop does try to throttle, but the AC adapter, lets say is 180 watts, if it pulls 185 and it cant handle it will send a kill signal to prevent overheating/frying a diode. Which is why he jumps to battery. If the PSU spikes like it does it could cause a blue screen if the motherboard can't handle it. It would be equivalent to unplugging your graphics card on a desktop if under high load. They may not have programmed a fail safe into the motherboard to account for this happening.

    OP try to unplug your laptop when under high load and see what happens, if it does not BSOD then the only other thing I can think is the PSU is spiking above tolerance causing issues.
     
  14. Meaker@Sager

    Meaker@Sager Company Representative

    Reputations:
    9,436
    Messages:
    58,194
    Likes Received:
    17,909
    Trophy Points:
    931
    Actually windows itself can't handle loosing the GPU anyway (one of the reasons why you don't get external GPUs at the moment).

    The spike would likely come from the battery not being able to maintain the load required for the instant it switches over but it should cope such as when you take the AC out during gameplay.