Hi, my computer keeps crashing even though i have already cleaned up the registry and fix it but the problem doesn't seem to go away. It crashes 2 or 3 times per week. Here is the most recent dump file that the crashes generated: "Windows has recovered from an unexpected shutdown" "Windows can check online for a solution to the problem" -> i did, but no result Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.4 Locale ID: 4105 Additional information about the problem: BCCode: 101 BCP1: 0000000000000018 BCP2: 0000000000000000 BCP3: FFFFF8800316A180 BCP4: 0000000000000007 OS Version: 6_1_7600 Service Pack: 0_0 Product: 256_1 Files that help describe the problem: C:\Windows\Minidump\041811-16281-01.dmp C:\Users\blau\AppData\Local\Temp\WER-99359-0.sysdata.xml Do you think it would be a driver problem? or MEM issue? Please help... Thanks alot!

Bug Check Code 0x101: http://msdn.microsoft.com/en-us/library/ff557211(VS.85).aspx Cause The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked. Check with your manufacturer to solve the problem with the processor or replace it. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

Hi, Please boot into Safe Mode to check if the issue occurs again. If so, it is likely the hardware issue such as processor. You should contact the manufacture to examine the issue. Also try to update BIOS and all devices' drivers from manufacture's site to check the result. To narrow down the issue, you could upload the Minidump to How to SkyDrive. Best Regards, NikiPlease remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Will do.. Thank you!

Hi, Please boot into Safe Mode to check if the issue occurs again. If so, it is likely the hardware issue such as processor. You should contact the manufacture to examine the issue. Also try to update BIOS and all devices' drivers from manufacture's site to check the result. To narrow down the issue, you could upload the Minidump to How to SkyDrive. Best Regards, Niki Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. here is the Minidump http://cid-24bc5a6d30bf6b57.skydrive.live.com/redir.aspx?resid=24BC5A6D30BF6B57!112 Thank you Niki!

******************************************************************************* * * * 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: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff8800316a180, The PRCB address of the hung processor. Arg4: 0000000000000007, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: d STACK_TEXT: fffff880`08793ea8 fffff800`02c7b453 : 00000000`00000101 00000000`00000018 00000000`00000000 fffff880`0316a180 : nt!KeBugCheckEx fffff880`08793eb0 fffff800`02cd5de7 : 00000000`00000000 fffff800`00000007 00000000`0002625a 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4dfe fffff880`08793f40 fffff800`02c28090 : 00000000`00000000 fffff880`087940f0 fffff800`02c43460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`08794040 fffff800`02cc9c33 : 00000000`1dad16ae fffff800`02c43460 fffff800`02e47e80 00000000`00000001 : hal!HalpRtcClockInterrupt+0x130 fffff880`08794070 fffff800`02cdb610 : fffffa80`00000000 fffff880`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163 fffff880`08794200 fffff800`02ce5881 : fffff8a0`11332000 00000000`00000002 00000000`00000001 00000000`00010000 : nt!KeFlushMultipleRangeTb+0x260 fffff880`087942d0 fffff800`02cf893b : 00000000`00000002 fffff880`08794440 fffff8a0`11332000 00000000`00000001 : nt!MiFlushTbAsNeeded+0x1d1 fffff880`087943e0 fffff800`02dfeceb : 00000000`00001190 00000000`00001190 00000000`00000001 fffff800`02fceefc : nt!MiAllocatePagedPoolPages+0x4bb fffff880`08794500 fffff800`02ce0050 : 00000000`00001190 fffffa80`06995000 00000000`00000001 00000000`00000000 : nt!MiAllocatePoolPages+0x8e2 fffff880`08794650 fffff800`02e01bfe : 00000000`00000000 00000000`00000000 fffffa80`00000000 fffffa80`06995000 : nt!ExpAllocateBigPool+0xb0 fffff880`08794740 fffff880`051d94cd : fffffa80`0920f4d0 fffffa80`0920f4d0 fffffa80`06c233a0 fffff880`08794820 : nt!ExAllocatePoolWithTag+0x82e fffff880`08794830 fffff880`051cee3a : fffffa80`0920f870 fffffa80`06c233a0 fffff880`00000009 fffff880`051cf23c : mrxsmb10!_SmbPseCreateOrdinaryExchange+0x239 fffff880`087948b0 fffff880`0517667c : fffff8a0`0f546ac0 fffff8a0`1144ad01 fffffa80`09231010 fffff8a0`10631dc0 : mrxsmb10!MRxSmbCloseSrvOpen+0x24a fffff880`08794920 fffff880`040a0daf : 00000000`00000000 fffff8a0`1144ad00 fffff880`02c2cab0 fffff8a0`1144aeb8 : mrxsmb!SmbShellCloseSrvOpen+0x68 fffff880`08794960 fffff880`02c36257 : fffffa80`09231010 00000000`00000000 fffff880`00000000 00000000`00000000 : csc!CscCloseSrvOpen+0x3eb fffff880`08794a70 fffff880`02c39702 : fffff8a0`1144aeb8 fffff880`02c2f101 fffff8a0`0f546ac0 00000000`00000000 : rdbss!RxCloseAssociatedSrvOpen+0x223 fffff880`08794ad0 fffff880`02c4aa5b : 00000000`00000001 fffff880`02c2f110 fffff8a0`1144ae78 00000000`00000000 : rdbss!RxFinalizeNetFobx+0x142 fffff880`08794b40 fffff880`02c3396d : fffff8a0`0f546ac0 fffffa80`08c01900 fffff8a0`1144aeb8 fffff880`02c33e01 : rdbss!RxScavengeRelatedFobxs+0x14b fffff880`08794bb0 fffff880`02c33f1a : fffffa80`00000001 fffffa80`08c017e0 00000000`00000001 00000000`00000201 : rdbss!RxScavengerFinalizeEntries+0x2c9 fffff880`08794c40 fffff880`02c151b1 : fffff880`02c305c0 00000000`00000080 fffff880`02c2f110 00000000`00000001 : rdbss!RxScavengerTimerRoutine+0x8a fffff880`08794c80 fffff800`02f71c06 : fffff880`02c305c0 fffff880`02c30900 00000000`00000000 fffff800`02cc5500 : rdbss!RxpWorkerThreadDispatcher+0x1a1 fffff880`08794d40 fffff800`02cabc26 : fffff880`02f64180 fffffa80`077b3b60 fffffa80`06cf0040 fffff880`01221534 : nt!PspSystemThreadStartup+0x5a fffff880`08794d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 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_8_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner --------- __________________________________________________ Like I said in my first reply, contact your manufacturer Technical Support or replace the processor. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

__________________________________________________ Like I said in my first reply, contact your manufacturer Technical Support or replace the processor. Hi, Like Mr X said, it should be hardware issue. You need to contact your manufacture to examine and solve the issue. Manufacture contacts http://windows.microsoft.com/en-us/windows/help/contact-support Regards, Niki Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks All... I did a BIOS update since the previous one was pretty outdated, 2 years old BIOS version. I doubt that this is the real cause but i tried it anyway. If the BIOS update didn't help out with the issue, then i will contact with the manufacturer for hardware replacement. Once again, thank you very much.

It turns out that the BIOS update does fix the BSOD crash!