I have a Dell E6500 with Windows 7 Pro 64-bit (factory installed). It's been running fine since I got it, but suddenly within the last 48 hours I've had three BSOD's - all when the system was sitting idle (programs on the screen, but I hadn't physically been using the system for at least 15 minutes in each case). I contacted Dell, and their tech support had me run the built-in system diagnostics everything came up clean. I haven't installed any new hardware/drivers/etc. recently (although I can't speak for what Windows Update might have done, but there's no restore point in System Restore that suggests that it has). At first glance, the crashes all appear the same: Probably caused by : ntoskrnl.exe ( nt+71f00 ) Followup: MachineOwner--------- 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 kindthat the kernel isn't allowed to have/catch (bound trap) or thatis always instant death (double fault). The first number in thebugcheck params is the number of the trap (8 = double fault, etc)Consult an Intel x86 family manual to learn more about what thesetraps 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 valueElse .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)Endifkb will then show the corrected stack.Arguments:Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULTArg2: 0000000080050031Arg3: 00000000000406f8Arg4: fffff80002a52798 Debugging Details:------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. **************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** **************************************************************************** (repeats of the same box above omitted) ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information.If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: nt FAULTING_MODULE: fffff80002a18000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002a89469 to fffff80002a89f00 STACK_TEXT: fffff880`009f4c68 fffff800`02a89469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt+0x71f00fffff880`009f4c70 00000000`0000007f : 00000000`00000008 00000000`80050031 00000000`000406f8 fffff800`02a52798 : nt+0x71469fffff880`009f4c78 00000000`00000008 : 00000000`80050031 00000000`000406f8 fffff800`02a52798 00000000`00000000 : 0x7ffffff880`009f4c80 00000000`80050031 : 00000000`000406f8 fffff800`02a52798 00000000`00000000 00000000`00000000 : 0x8fffff880`009f4c88 00000000`000406f8 : fffff800`02a52798 00000000`00000000 00000000`00000000 00000000`00000000 : 0x80050031fffff880`009f4c90 fffff800`02a52798 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x406f8fffff880`009f4c98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x3a798 STACK_COMMAND: kb FOLLOWUP_IP: nt+71f00fffff800`02a89f00 48894c2408 mov qword ptr [rsp+8],rcx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt+71f00 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntoskrnl.exe BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner--------- 1: kd> lmvm ntstart end module namefffff800`02a18000 fffff800`02ff5000 nt T (no symbols) Loaded symbol image file: ntoskrnl.exe Image path: \SystemRoot\system32\ntoskrnl.exe Image name: ntoskrnl.exe Timestamp: Mon Jul 13 19:40:48 2009 (4A5BC600) CheckSum: 0054B487 ImageSize: 005DD000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 The crash files are available here: http://cid-4bc451f0e9b920a6.skydrive.live.com/self.aspx/crashData/crash.zip Any help would be greatly appreciated.

You may try the following general troubleshooting steps. 1. Please remove the antivirus and run the system with a period. If the issue does not occur, mainly focus on antivirus settings and compatibility. 2. Disable Automatic Restart and see detail information on the blue screen. 1).Click Start, in the Start Search box enter sysdm.cpl. 2).Click the tab Advanced. Under Startup and Recovery, click the Settings button. 3). Uncheck “Automatically restart”. 4). Click OK. When Blue Screen displays, try to find more information. 3. Download all the latest drivers from the following website and install. Drivers & Downloads for Latitude E6500 Important Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information. 4. If the above suggestions do not work, I suggest you contact Dell to check hardware problems. Dell - Contact UsArthur Xie - MSFT