Random windows 7 64bit bsods!

[stevenlikesfish]

recently I noticed that my computer had 3 crashes while I wasnt around. all crashes lead to the kernel when I debugged the minidumps. my computer is a Gateway® NV5216u found on this page Gateway Official Site: Shop - NV52 Series, Notebooks. heres the full bugcheck. I have also done a chkdsk and a memtest86 both clean.



Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\windows\minidump\081810-33587-01.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: c:\windows\
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`08c4a000 PsLoadedModuleList = 0xfffff800`08e87e50
Debug session time: Wed Aug 18 19:05:24.137 2010 (GMT-5)
System Uptime: 0 days 5:04:11.852
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff80008c82ec0}

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

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

1: kd> !
No export found
1: 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: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80008c82ec0

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80008cb9ca9 to fffff80008cba740

STACK_TEXT:
fffff880`009f5c68 fffff800`08cb9ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009f5c70 fffff800`08cb8172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009f5db0 fffff800`08c82ec0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`02f1cab0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`08cb8172 90 nop

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

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

 

[KSoD]

This is a driver error. One of your drivers you are using is not compatible with Win7 64 Bit.

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

That is the problem itself. It is hooked into the svchost.exe process. You have to find updated drivers for Win7 64Bit for your system and components.

 

[stevenlikesfish]

alright is there a site or somthing that scans and updates drivers for me?

 

[KSoD]

No. Go to the PC Manufacturer's site and search or go directly to the device's manufacturer's website. Doing it manually is 410% better than relying on software to do it for you.

 

[stevenlikesfish]

is there a driver in particular? or should I just update all of them?

 

[Swam31]

You should work out which drivers are out of date by looking at the dates of the drivers in device manager, and comparing them to the dates of the drivers you can download from the manufacturer's website.

It's pretty difficult to work out which driver s causing the problem so just update any that are newer than the ones you have.

Also, there are a lot of program that offer to scan you computer for driver updates. I've never found one that lets you download the drivers for free, so don't be duped by any flashy adds...