Sager NP8760 initial startup problem

I have a Sager NP8760 laptop that's been giving me weird problems at startup ever since I bought it.

Every evening, without fail, when I start my laptop, it will randomly give me a blue screen error of varying reasons (notably Memory Management error), sometimes it occurs before Windows have loaded and sometimes during loading. After I shutdown the laptop (since its the only thing I can do when a BSOD error shows up) and press the power button again, only then it will boot up properly. But not after I shutdown the laptop first.

Anyone have any ideas why? It will happen without fail every evening when I reach home from work and startup my laptop. I also noticed if the laptop has been turned off for about 8 hours, this problem is 100% guaranteed to appear.

Could this be a power issue? Any Sager NP8760 owners having same problems? I live in Singapore and since Sager laptops are built in the USA, I'm not sure if my household power supply rating is sufficient. I am running Windows 7 64-bit. Any advice is greatly appreciated.

 

Hi
firstly download Who Crashed
what spec have you got especially graphics card drivers as certain ones have been known to cause bsod on a regular basis.
as soon as you get a blue screen and reboot run who crashed and post the full text for us to analize.

 

Here are my Sager NP8760 specs:

OS: Windows 7 64-Bit
CPU: Intel Core i7-720QM
RAM: 4.0GB Dual-Channel DDR3
Graphics Card: ATI Mobility Radeon HD 5870
Hard Disk: 500GB Seagate SATA HDD
Audio Card: Realtek High Definition Audio

All drivers were installed using the original Sager CD.

Below are the analysis of WhoCrashed:

--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 5/8/2010 10:54:47 AM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003346588, 0xFFFFF88003345DF0, 0xFFFFF80002CB0B7C)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\080510-18392-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 3/8/2010 11:01:51 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x5002, 0xFFFFF70001080000, 0x662, 0x4000663FFFFFFFE)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\080310-21372-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 19/7/2010 10:42:43 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8002184630, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\071910-25896-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 15/7/2010 11:16:17 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80021865B0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\071510-26457-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 14/7/2010 12:30:36 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F720CC, 0xFFFFF88009FC2D30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\071410-14071-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 13/7/2010 11:14:08 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800023BF4FC, 0xFFFFF88002190988, 0xFFFFF880021901F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\071310-19780-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 13/7/2010 11:13:15 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80021AA580, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\071310-24850-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 8/7/2010 10:54:56 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80021AA5B0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\070810-18267-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 6/7/2010 12:24:59 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002DBE0F3, 0xFFFFF88003377918, 0xFFFFF88003377180)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\070610-20997-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 1/7/2010 11:40:32 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8001B6CC00, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\070110-28251-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 30/6/2010 11:20:13 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFF6FE50012EF8, 0x0, 0xFFFFF80002CD3018, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\063010-20779-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 29/6/2010 12:16:19 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CBF8AA, 0xFFFFF88008834680, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\062910-23946-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 28/6/2010 11:51:10 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800217AD00, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\062810-26426-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 23/6/2010 3:31:37 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFF6FE5000A770, 0x0, 0xFFFFF80002C91018, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\062310-19983-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 23/6/2010 3:26:32 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002FC0AF4, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\062310-20358-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 23/6/2010 3:21:03 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8001A4CA80, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\062310-22167-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

16 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.

 

Bump. Based on the above analysis from WhoCrashed in my previous post, is there anyone who can advice what is wrong with my Sager?

 

My friend had a similar problem with the memory management BSOD. Turned out he had bad RAM. Try booting up with one stick of RAM at a time. That could probably isolate the problem.

 

Memory management issues seem to be the recurring theme, but you might also check the integrity of your system files. Open an elevated command prompt (Start|Run, enter "cmd" and select run as Administrator). At the prompt, enter "sfc /scannow" (no quotes). System File Checker scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed, or damaged versions with the correct versions if possible.

 

Ok I've done a couple of swaps to test my RAM modules but the results really puzzles me.

I've tried booting up my laptop with one RAM module (2GB) at a time and on different memory slots. Result: No BSOD error. System appears stable.

I can conclude that my RAM modules are ok. But what it is really weird, is that when using all 4GB RAM modules after at least 6 hours of non-usage of my laptop, the BSOD error will appear. Can someone pls explain why this is happening?? Are Windows 7 64-bit OS having any known issues with 4GB memory?

Thanks, I'll try that once I get home from work. I'm desperate for answers.

 

can you run memtest and see if that spits out any errors?

You will have to burn the iso and boot from cd

Memtest86+ - Advanced Memory Diagnostic Tool

 

you certainly have had a few bsod havnt you LordVenus

tbh as its a new computer i think you should contact tech support at sager with a full report of what youve posted above as this defo should not be happening and ruining your experience of owning a new clevo. yes the members of this great forum will sooner or later get to the bottom of the problem but if it happens once then sadly it could happen again and you deserve better than that as a customer of sager.
good luck

 

Have both the memsticks in and run memtest over night (around 8-10 hours is recommended to let it sit).

If that doesn't report any errors it could be a software issue.
If you can be bothered, reinstall win 7. Preferably with only the necessary drivers and maybe an AV.

 

LordVenus,

Please post any updates or possible resolution to the issue. I should be receiving my new Sager NP8760 very soon and I would like to make a complete system check to make sure everything is good and my investment is satisfying.

It would be wonderful if you would take photos of the BSOD. The displayed error might give a hint of what is caussing the issue.

Possibly doing a CPU burn-in may be suggested, however I do not have any suggested tools for this.

Thanks for the Memtest86+ link.