10 BSOD in a week with new laptop. Y? (debug log attached)

J

jjkrogs

New Member
First post (hi). I'll buy a coffee to anyone who can fix this problem...

New laptop, Sager NP 9280 i7 950, 6g ram, 280m GPU, Vista Home Premium x64 SP2

First thing I did was update GPU driver and make sure all other drivers and windows updates were current with x64 compatability.

I've had this thing a week and have had at least 10 BSOD with the following debugger log:


Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\####\Documents\Crash Data\Mini061709-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0xfffff800`02419000 PsLoadedModuleList = 0xfffff800`025dddd0
Debug session time: Wed Jun 17 13:32:49.343 2009 (GMT-5)
System Uptime: 0 days 0:05:00.063
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050033, 6f8, fffff800024d3719}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b8 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000006f8
Arg4: fffff800024d3719

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800024731ee to fffff80002473450

STACK_TEXT:
fffffa60`019dda68 fffff800`024731ee : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
fffffa60`019dda70 fffff800`02471a38 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffffa60`019ddbb0 fffff800`024d3719 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb8
fffffa60`019f9ff0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2c0d5


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b8
fffff800`02471a38 90 nop

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiDoubleFaultAbort+b8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 49e0237f

FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b8

BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b8

Followup: MachineOwner
 
Last edited:

My Computer

System One

Sorry, but the analysis doesn't tell us much. The error is a relatively common one, and there are additional commands that we can run that'll help narrow it down some more.

Could you zip up the contents of the C:\Windows\Minidump folder (even the one's that you moved out) and upload them with your next post?

FYI - here's some more info about performing analysis' - and I've added a link at the bottom that briefly describes the procedure that I go through when looking at them.
Diagnosing Bsod's (originally posted 02Oct08) - Vox
 

My Computer

System One

Mouse and keyboard drivers appear a bit out of date:
fffffa60`07fc1000 fffffa60`07fd4000 LHidFilt LHidFilt.Sys Fri Sep 21 07:05:39 2007 (46F3A583)
fffffa60`07fd4000 fffffa60`07fe7000 LMouFilt LMouFilt.Sys Fri Sep 21 07:05:43 2007 (46F3A587)
Click to expand...

The errors occurred during memory accesses, and appear to involve both network drivers and USB drivers.

Do you have anything plugged into the USB ports? If so, what? Does it BSOD when the devices are unplugged?

Download new drivers for your chipset (the USB drivers are in there) and for your wireless networking card.
Then uninstall the current drivers through Control Panel...Programs...Uninstall a program.
Then install the freshly downloaded ones and see if that fixes it.

I'm also concerned about device compatibility, as HAL.DLL shows in the stack trace. While this isn't a definite cause, it's presence raises the question about compatibility.

Finally, as most of the errors occurred while accessing memory, run the built in Vista memory diagnostic: BC - Vista Memory Diagnostic
A summary of the BSOD's:
Code: 
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Thu Jun 11 23:59:00.273 2009 (GMT-4)
System Uptime: 0 days 0:00:05.992
BugCheck 1000007E, {ffffffffc0000005, fffff80001e7c1ca, fffffa6001da0d18, fffffa6001da06f0}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_StartDevice+f3d )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Sat Jun 13 10:37:38.320 2009 (GMT-4)
System Uptime: 0 days 0:08:22.024
BugCheck 1000007E, {ffffffffc0000005, fffff80001ea8421, fffffa6001f32978, fffffa6001f32350}
Probably caused by : ntkrnlmp.exe ( nt!ExpScanGeneralLookasideList+51 )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Mon Jun 15 10:12:40.382 2009 (GMT-4)
System Uptime: 0 days 0:00:06.116
BugCheck 1000007E, {ffffffffc0000005, fffff80001e3b1ca, fffffa6001daed18, fffffa6001dae6f0}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_StartDevice+f3d )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Mon Jun 15 11:36:24.937 2009 (GMT-4)
System Uptime: 0 days 0:32:35.651
BugCheck D1, {ff, 2, 1, fffffa6003dc2622}
*** WARNING: Unable to verify timestamp for NETw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5v64.sys
Probably caused by : NETw5v64.sys ( NETw5v64+1b8622 )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Mon Jun 15 12:40:04.753 2009 (GMT-4)
System Uptime: 0 days 0:19:30.347
BugCheck 3B, {c000001d, fffff80001ec6a88, fffffa600614f2e0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeDelayExecutionThread+3f8 )
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Mon Jun 15 21:53:14.086 2009 (GMT-4)
System Uptime: 0 days 0:00:05.804
BugCheck 1000007E, {ffffffffc0000005, fffff80001e701ca, fffffa6001da0d18, fffffa6001da06f0}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_StartDevice+f3d )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Tue Jun 16 11:20:57.837 2009 (GMT-4)
System Uptime: 0 days 0:43:10.728
BugCheck 7F, {8, 80050033, 6f8, fffff800024bced0}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b8 )
PROCESS_NAME:  iexplore.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Wed Jun 17 12:05:00.256 2009 (GMT-4)
System Uptime: 0 days 0:00:06.990
BugCheck 1000007E, {ffffffffc0000005, fffff800024721ca, fffffa6001dc3d18, fffffa6001dc36f0}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_StartDevice+f3d )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Wed Jun 17 14:07:04.533 2009 (GMT-4)
System Uptime: 0 days 1:02:00.487
BugCheck 19, {20, fffffa8007634630, fffffa8007634690, 4060005}
Probably caused by : win32k.sys ( win32k!UserDeleteW32Thread+58 )
PROCESS_NAME:  iexplore.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Wed Jun 17 14:13:57.055 2009 (GMT-4)
System Uptime: 0 days 0:06:13.818
BugCheck 7F, {8, 80050033, 6f8, fffffa600380e57f}
*** WARNING: Unable to verify timestamp for NETw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5v64.sys
Probably caused by : NETw5v64.sys ( NETw5v64+457f )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Wed Jun 17 14:32:49.343 2009 (GMT-4)
System Uptime: 0 days 0:05:00.063
BugCheck 7F, {8, 80050033, 6f8, fffff800024d3719}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b8 )
PROCESS_NAME:  System
 

My Computer

System One

Yeah, the first few BSODs on that list I'm pretty sure were mouse/keyboard-related, and I've since upgraded. It's the last 3-5 that really have me guessing-- the ones from the last few days.

Currently plugged into my USB ports:

Flash drive
Rocketfish notebook cooler (power only)
Logitech VX nano cordless mouse
...and recently (after the crashes) Logitech chordless desktop.

I'll run the memory diagnostic tool immediately after posting this and will report if there are any errors.

As for updating the chipset-- how does one do that for a brand new Sager NP 9280? I've gone through EVERY piece of hardware listed on my hardware profile and pushed the 'check for updates' on each driver, but none were found for anything. I get the "you currently have the best available driver" or something like that. That goes for the network card, as well.
 

My Computer

System One

Here's this morning's blue screen...

Wow, first Vista experience. Nice upgrade MS came up with from XP. :sarc: Figured I'd wait a few years so they could work out the kinks. LOL
 

My Computer

System One

Here's a link for the specs of your laptop: custom gaming laptops - Welcome to Sager Notebooks

So, you have an Intel® X58 Chipset + ICH10R
Going to the Intel website.....
Nothing easily accessible there (I'm just not sure enough about the X58 chipset in a laptop to fiddle with it).
I'd contact Sager and explain that we think that there's a corruption in the USB drivers and would like to reinstall the chipset - could they please point you at the drivers to use?

Don't forget to replace the network drivers also.

Good luck!
 

My Computer

System One

Alright, thanks for your help. Seriously, tho-- is Vista really an upgrade from XP? I rarely had problems with XP in over 4 years, and the few that I did never caused blue screens OR a visit to the MS forums.

It's like Windows ME all over again.
 

My Computer

System One

XP was a mature OS - it had been worked on for years. Vista was a significant change internally from XP, and it has had it's share of growing pains. FWIW - the majority of users don't have problems - but there's enough users that problems will pop up.

Vista does quite well for most folks at the SP1 level, and there aren't many issues with SP2. Do you recall the problems that came about with XP's SP2?

But in this case you're using a laptop that's on the leading edge of technology - so the use of the X58 chipest on a laptop is something that needs an expert touch (the Sager tech support people would have the most experience with this).
 

My Computer

System One

You must log in or register to reply here.
Back
Top