hello guys just recently i have been getting random reboots,it happens quiet intermittant, i have my event viewer log can someone tell me what its telling me? thanks in advance Log Name: Security Source: Microsoft-Windows-Eventlog Date: 7/5/2012 6:47:08 PM Event ID: 1101 Task Category: Event processing Level: Error Keywords: Audit Success User: N/A Computer: POTC-PC Description: Audit events have been dropped by the transport. 0 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Eventlog" Guid="{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}" /> <EventID>1101</EventID> <Version>0</Version> <Level>2</Level> <Task>101</Task> <Opcode>0</Opcode> <Keywords>0x4020000000000000</Keywords> <TimeCreated SystemTime="2012-07-05T23:17:08.018800000Z" /> <EventRecordID>32235</EventRecordID> <Correlation /> <Execution ProcessID="968" ThreadID="468" /> <Channel>Security</Channel> <Computer>POTC-PC</Computer> <Security /> </System> <UserData> <AuditEventsDropped xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog"> <Reason>0</Reason> </AuditEventsDropped> </UserData> </Event>

also got a BSOD, this is the details - System - Provider [ Name] Microsoft-Windows-Kernel-Power [ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4} EventID 41 Version 2 Level 1 Task 63 Opcode 0 Keywords 0x8000000000000002 - TimeCreated [ SystemTime] 2012-07-05T23:58:14.722800000Z EventRecordID 116724 Correlation - Execution [ ProcessID] 4 [ ThreadID] 8 Channel System Computer POTC-PC - Security [ UserID] S-1-5-18 - EventData BugcheckCode 257 BugcheckParameter1 0x61 BugcheckParameter2 0x0 BugcheckParameter3 0xfffff880009b8180 BugcheckParameter4 0x1 SleepInProgress false PowerButtonTimestamp 0

sorry about all the info guys, here is the dump file Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\POTC\Desktop\070512-16426-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.17017.amd64fre.win7_gdr.120503-2030 Machine Name: Kernel base = 0xfffff800`02655000 PsLoadedModuleList = 0xfffff800`02891e70 Debug session time: Thu Jul 5 19:27:11.371 2012 (UTC - 5:30) System Uptime: 0 days 0:40:21.183 Loading Kernel Symbols ............................................................... ................................................................ .......................................................... Loading User Symbols Loading unloaded module list .......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {61, 0, fffff880009b8180, 1} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: 0000000000000061, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff880009b8180, The PRCB address of the hung processor. Arg4: 0000000000000001, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: bf3.exe CURRENT_IRQL: d STACK_TEXT: fffff880`11a46418 fffff800`02672993 : 00000000`00000101 00000000`00000061 00000000`00000000 fffff880`009b8180 : nt!KeBugCheckEx fffff880`11a46420 fffff800`026cd677 : 00000000`00000000 fffff800`00000001 00000000`00002710 fffff800`026deef0 : nt! ?? ::FNODOBFM::`string'+0x4d8e fffff880`11a464b0 fffff800`02616895 : fffff800`0263b460 fffff880`11a46660 fffff800`0263b460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`11a465b0 fffff800`026c1533 : 00000000`9f223d03 fffff800`0283ee80 fffff8a0`059ed958 00000000`00110dcd : hal!HalpHpetClockInterrupt+0x8d fffff880`11a465e0 fffff800`026d8580 : fffff880`11a467f0 fffff800`00000000 fffff880`11a467f0 00000000`00260000 : nt!KiInterruptDispatchNoLock+0x163 fffff880`11a46770 fffff800`026f87aa : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`01d80f80 : nt!KiIpiSendRequestEx+0xb0 fffff880`11a467b0 fffff800`026f5c74 : 00000000`00000001 00000000`0027b000 80a00000`b6718c66 80a00000`b6718867 : nt!KeFlushTb+0xf6 fffff880`11a46830 fffff800`026f8159 : 00000000`00000000 00000000`0027bfff fffff880`00000000 fffffa80`095d4060 : nt!MiDeleteVirtualAddresses+0x9ab fffff880`11a469f0 fffff800`029d7dc0 : fffffa80`0644af80 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9 fffff880`11a46b10 fffff800`029d81cb : 00000980`00000000 00000000`00260000 fffffa80`00000001 00000000`04f0f101 : nt!MiUnmapViewOfSection+0x1b0 fffff880`11a46bd0 fffff800`026c4293 : 00000000`00000001 00000000`00260000 fffffa80`090da930 fffffa80`04b8eae0 : nt!NtUnmapViewOfSection+0x5f fffff880`11a46c20 00000000`7712f95a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`04f0e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7712f95a 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_2_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: 0000000000000061, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff880009b8180, The PRCB address of the hung processor. Arg4: 0000000000000001, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: bf3.exe CURRENT_IRQL: d STACK_TEXT: fffff880`11a46418 fffff800`02672993 : 00000000`00000101 00000000`00000061 00000000`00000000 fffff880`009b8180 : nt!KeBugCheckEx fffff880`11a46420 fffff800`026cd677 : 00000000`00000000 fffff800`00000001 00000000`00002710 fffff800`026deef0 : nt! ?? ::FNODOBFM::`string'+0x4d8e fffff880`11a464b0 fffff800`02616895 : fffff800`0263b460 fffff880`11a46660 fffff800`0263b460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`11a465b0 fffff800`026c1533 : 00000000`9f223d03 fffff800`0283ee80 fffff8a0`059ed958 00000000`00110dcd : hal!HalpHpetClockInterrupt+0x8d fffff880`11a465e0 fffff800`026d8580 : fffff880`11a467f0 fffff800`00000000 fffff880`11a467f0 00000000`00260000 : nt!KiInterruptDispatchNoLock+0x163 fffff880`11a46770 fffff800`026f87aa : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`01d80f80 : nt!KiIpiSendRequestEx+0xb0 fffff880`11a467b0 fffff800`026f5c74 : 00000000`00000001 00000000`0027b000 80a00000`b6718c66 80a00000`b6718867 : nt!KeFlushTb+0xf6 fffff880`11a46830 fffff800`026f8159 : 00000000`00000000 00000000`0027bfff fffff880`00000000 fffffa80`095d4060 : nt!MiDeleteVirtualAddresses+0x9ab fffff880`11a469f0 fffff800`029d7dc0 : fffffa80`0644af80 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9 fffff880`11a46b10 fffff800`029d81cb : 00000980`00000000 00000000`00260000 fffffa80`00000001 00000000`04f0f101 : nt!MiUnmapViewOfSection+0x1b0 fffff880`11a46bd0 fffff800`026c4293 : 00000000`00000001 00000000`00260000 fffffa80`090da930 fffffa80`04b8eae0 : nt!NtUnmapViewOfSection+0x5f fffff880`11a46c20 00000000`7712f95a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`04f0e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7712f95a 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_2_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: 0000000000000061, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff880009b8180, The PRCB address of the hung processor. Arg4: 0000000000000001, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: bf3.exe CURRENT_IRQL: d STACK_TEXT: fffff880`11a46418 fffff800`02672993 : 00000000`00000101 00000000`00000061 00000000`00000000 fffff880`009b8180 : nt!KeBugCheckEx fffff880`11a46420 fffff800`026cd677 : 00000000`00000000 fffff800`00000001 00000000`00002710 fffff800`026deef0 : nt! ?? ::FNODOBFM::`string'+0x4d8e fffff880`11a464b0 fffff800`02616895 : fffff800`0263b460 fffff880`11a46660 fffff800`0263b460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`11a465b0 fffff800`026c1533 : 00000000`9f223d03 fffff800`0283ee80 fffff8a0`059ed958 00000000`00110dcd : hal!HalpHpetClockInterrupt+0x8d fffff880`11a465e0 fffff800`026d8580 : fffff880`11a467f0 fffff800`00000000 fffff880`11a467f0 00000000`00260000 : nt!KiInterruptDispatchNoLock+0x163 fffff880`11a46770 fffff800`026f87aa : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`01d80f80 : nt!KiIpiSendRequestEx+0xb0 fffff880`11a467b0 fffff800`026f5c74 : 00000000`00000001 00000000`0027b000 80a00000`b6718c66 80a00000`b6718867 : nt!KeFlushTb+0xf6 fffff880`11a46830 fffff800`026f8159 : 00000000`00000000 00000000`0027bfff fffff880`00000000 fffffa80`095d4060 : nt!MiDeleteVirtualAddresses+0x9ab fffff880`11a469f0 fffff800`029d7dc0 : fffffa80`0644af80 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9 fffff880`11a46b10 fffff800`029d81cb : 00000980`00000000 00000000`00260000 fffffa80`00000001 00000000`04f0f101 : nt!MiUnmapViewOfSection+0x1b0 fffff880`11a46bd0 fffff800`026c4293 : 00000000`00000001 00000000`00260000 fffffa80`090da930 fffffa80`04b8eae0 : nt!NtUnmapViewOfSection+0x5f fffff880`11a46c20 00000000`7712f95a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`04f0e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7712f95a 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_2_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner ---------

Hi , It seems the reboots is caused by the BSOD. The dump file indicates the BSOD was caused by bf3.exe. Does the issue occur when playing game? You may check if there is any firmware updates for your hard drive or BIOS. I would suggest you to follow the steps in the link and check if the issue occurs: http://answers.microsoft.com/en-us/windows/forum/windows_7-system/bluescreen-101-clockwatchdogtimeout-need-help/4c892d81-17e8-4a73-bd38-35c513541c9fTracy Cai TechNet Community Support

Hi , It seems the reboots is caused by the BSOD. The dump file indicates the BSOD was caused by bf3.exe. Does the issue occur when playing game? You may check if there is any firmware updates for your hard drive or BIOS. I would suggest you to follow the steps in the link and check if the issue occurs: http://answers.microsoft.com/en-us/windows/forum/windows_7-system/bluescreen-101-clockwatchdogtimeout-need-help/4c892d81-17e8-4a73-bd38-35c513541c9fTracy Cai TechNet Community Support