help with BSOD

just uninstalled the blue soleil dont use bluetooth anymore, now i must go an meet the girlfriend:)

BTHidMgr.sys Mar 05 2007 - Bluetooth

elrawdsk.sys Jul 26 20087 - RawDisk Driver. Allows write-access to raw disk sectors for user mode applications in Windows 2000, or RawDisk Driver. Allows write access to raw disk sectors for user mode applications in Windows 2000, belongs to the software ElRawDisk by EldoS Corporation.

LVUSBS64.sys Jul 26 2008 - Logitech QuickCam driver

PxHlpa64.sys Mar 12 2008 - Px Engine Device Driver for 64-bit Windows or PxHlpa belongs to the software PxHelp or PxHlpa by Sonic Solutions (www.sonic.com). I think this relates to your DVD-RW? Try to update the software and driver.

speedfan.sys Sep 24 2006 - SpeedFan Device Driver belongs to the software Windows (R) 2000 DDK driver by Windows (R) 2000 DDK provider (www.microsoft.com). This is an XP driver for monitoring fan speed and temperature. It is able to change fan speeds according to system temperatures. SpeedFan can read S.M.A.R.T. values (and temperatures) from your hard disks and change the FSB speed.

vbtenum.sys Mar 05 2007 - belongs to the software Bluetooth HID Enumerator or BlueSoleil by IVT Corporation.

VComm.sys Mar 05 2007 - Bluetooth Serial Port Driver. Manufacturer: IVT Corporation www.ivtcorporation.com

VcommMgr.sys Mar 05 2007 - Bluetooth VcommMgr driver belongs to the software Bluetooth VComm Manager Service by IVT Corporation.

whfltr2k.sys Jan 26 2007 - Whfltr2k.sys with description USB Mouse Lower filter driver is a driver file from an unknown company belonging to an unknown product. If you cannot find an updated driver for your mouse, it may be time for a new mouse.

All of the above drivers need updating. I am not sure about Speedfan. I will ask Jonathan about that one.

Edited to add - I see you have taken care of the Bluetooth drivers by uninstalling Bluetooth. Very good. We will work on the remaining when you get back.

had another bsod waiting for me when i got back

I suspect CPU. See this article on your bugcheck 101: https://www.sevenforums.com/crash-loc...oubleshtg.html

Code:

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_062110-27440-01.zip\062110-27440-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`04413000 PsLoadedModuleList = 0xfffff800`04650e50
Debug session time: Mon Jun 21 13:40:59.698 2010 (UTC - 4:00)
System Uptime: 0 days 1:04:31.774
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88002f64180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

It is another error 101.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88002f64180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f64180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  StartMenu7.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`09f7f0b8 fffff800`04431443 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f64180 : nt!KeBugCheckEx
fffff880`09f7f0c0 fffff800`0448bcf7 : 00000000`00000000 fffff800`00000002 00000000`000030d5 fffff880`04108077 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff880`09f7f150 fffff800`049f9895 : fffff800`04a1e3c0 fffff880`09f7f300 fffff800`04a1e3c0 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`09f7f250 fffff800`0447faf3 : 00000000`8972b752 fffff800`045fde80 fffff800`045fde80 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d
fffff880`09f7f280 fffff800`044914f0 : fffffa80`00000000 fffff880`00000001 00000000`00000000 fffff6fc`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`09f7f410 fffff800`0449b761 : fffff900`c07c7000 00000000`00000002 00000000`00000001 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x250
fffff880`09f7f4e0 fffff800`044ae7fb : 00000000`00000002 fffff880`09f7f640 fffff900`c07c7000 00000000`00000000 : nt!MiFlushTbAsNeeded+0x1d1
fffff880`09f7f5f0 fffff800`045b4ceb : 00000000`00001130 00000000`00001130 00000000`00000021 fffff800`04478d0b : nt!MiAllocatePagedPoolPages+0x4bb
fffff880`09f7f710 fffff800`04495f60 : 00000000`00001130 fffff880`052b9cc0 00000000`00000021 fffff800`045b434f : nt!MiAllocatePoolPages+0x8e2
fffff880`09f7f860 fffff800`045b7bfe : 00000000`00000000 00000000`00000000 fffffa80`00000020 fffff880`052b9cc0 : nt!ExpAllocateBigPool+0xb0
fffff880`09f7f950 fffff960`000b4a78 : fffff900`c2041000 00000000`00000000 00000000`6c777355 00000000`00000001 : nt!ExAllocatePoolWithTag+0x82e
fffff880`09f7fa40 fffff960`000cd992 : fffff900`c2041000 fffff900`00000000 00000000`00000000 fffff900`00000000 : win32k!InternalRebuildHwndListForIMEClass+0x38
fffff880`09f7fab0 fffff960`000b4791 : 00000000`00000000 fffff880`09f7fc60 00000000`00000000 fffff780`00000008 : win32k!BuildHwndList+0xb2
fffff880`09f7fae0 fffff800`04482853 : fffffa80`0a83a060 00000000`00000000 00000000`003de7d8 fffff880`09f7fb88 : win32k!NtUserBuildHwndList+0x19d
fffff880`09f7fb70 00000000`74befd8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`003de7b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74befd8a


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner

Joanthan beat me to it. Go ahead, Jonathan and thanks.

got rid of speed fan

the pc is just over 6 months old my mouses are microsoft trust and labtech just checking drivers

windows says the mouse drivers are up to date

Brian, do read through the thread that Jonathan suggested above in post #84.

start menu 7 shall i uninstall? im just reading the other link