Computer instantly shut off mid-use.

[Twilit Soul]

Is Windows 7 . . .
- x86 (32-bit) or x64 ?
x64
- the original installed OS on the system?
No
- an OEM or full retail version?
Full retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)?
Two years just about.
- What is the age of OS installation (have you re-installed the OS?)
Ah...about a month? Between 0 and 2 months, for sure.

 

[zigzag3143]

Is Windows 7 . . .
- x86 (32-bit) or x64 ?
x64
- the original installed OS on the system?
No
- an OEM or full retail version?
Full retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)?
Two years just about.
- What is the age of OS installation (have you re-installed the OS?)
Ah...about a month? Between 0 and 2 months, for sure.

These were probably caused by your rfcomm.sys bluetooth driver. Re-install with newest version to test.

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\050711-18595-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a0d000 PsLoadedModuleList = 0xfffff800`02c52e90
Debug session time: Sat May  7 16:31:28.377 2011 (GMT-4)
System Uptime: 0 days 21:03:13.140
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
...............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, 0, fffff88002fe7428, fffff88002fe6c80}

[COLOR=Red][B]Probably caused by : rfcomm.sys [/B][/COLOR]( rfcomm!RefObj_ReleaseEx+14a )

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

Old drivers needing updating

CtClsFlt.sys       3/11/2009 11:47:44 PM    fffff880`024d5080    0x0002a080    0x49b885e0    fffff880`024ab000                            
netw5v64.sys    3/26/2009 12:21:24 PM    fffff880`04db5000    0x0053b000    0x49cbab84    fffff880`0487a000                            
k57nd60a.sys    4/26/2009 07:23:05 AM    fffff880`04dfd000    0x00048000    0x49f44419    fffff880`04db5000                            
spldr.sys           5/11/2009 12:56:27 PM    fffff880`018f4000    0x00008000    0x4a0858bb    fffff880`018ec000                            
GEARAspiWDM.sys 5/18/2009 08:17:04 AM    fffff880`03d2f000    0x0000d000    0x4a1151c0    fffff880`03d22000                            
btwrchid.sys    6/25/2009 01:51:37 AM    fffff880`06359880    0x00003880    0x4a431069    fffff880`06356000                            
rimspx64.sys    6/25/2009 03:13:43 AM    fffff880`03c9e000    0x00017000    0x4a4323a7    fffff880`03c87000                            
rixdpx64.sys    6/25/2009 03:38:50 AM    fffff880`03cf5000    0x00057000    0x4a43298a    fffff880`03c9e000                            
rimmpx64.sys    6/25/2009 04:04:18 AM    fffff880`04874000    0x00016000    0x4a432f82    fffff880`0485e000

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[Twilit Soul]

Thanks!

I appreciate it. I'm guessing that Windows fails at actually detecting if I have the latest driver or not...so I'll start looking for manual updates and let you know if I need help!

 

[zigzag3143]

I appreciate it. I'm guessing that Windows fails at actually detecting if I have the latest driver or not...so I'll start looking for manual updates and let you know if I need help!

Windows driver updates may be as far as a year behind. Always go to the mfr. Dont use driver updater like programs.

Let us know if you need help


Ken J