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.
-
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. -
The psu is overloaded.
-
-
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 -
Meaker@Sager Company Representative
Also does your charger behave oddly when these crashes happen? Does the power LED go off on it?
-
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.
-
Meaker@Sager Company Representative
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. -
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.
-
Support.3@XOTIC PC Company Representative
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.
-
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.
-
Meaker@Sager Company Representative
No, if anything it should just throttle a bit.
-
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. -
Meaker@Sager Company Representative
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.
Running Furmark + Prime95 At The Same Time on NP8230 (P151SM1)
Discussion in 'Sager and Clevo' started by I'm Poor, Sep 14, 2013.