hi need help with window error Blue screen

Hi nommy; sorry you are having problems. I looked at your three most recent dumps. All gave a different error code. That usually indicates a hardware/hardware related problem. No specific causes are given. Two of the three dumps indicate memory corruption. One dump is error code 101, CLOCK_WATCHDOG_TIMEOUT. Read the following two articles for more information on Error 101:

https://www.sevenforums.com/crash-loc...tml#post567135

https://www.sevenforums.com/crashes-d...tml#post356791

Because of error code 101, I suggest you stop over clocking and return to default values while you are troubleshooting. You want to eliminate all possible causes of crashes.

Next I recommend that you uninstall Norton/Symantec using this removal tool: Tool. Norton is a known cause of BSOD's on some Win 7 systems. Download and install Microsoft Security Essentials and make sure Windows Firewall is turned on. After you know your system is stable, you can try Norton again; but I do not recommend doing so.

I find an outdated driver on your system. Out of date drivers can cause memory corruption and BSOD's. Update this driver.

AsIO.sys Mon Apr 06 03:21:08 2009 - Asus PCProbe Utility. ASUSTeK Computer Inc.-Support-. If you cannot update this driver, uninstall probe.

Stop overclocking and return to default values. Uninstall Norton nad update or eliminate the above driver. Reboot and see how your system does. Post back and let us know. If you get another BSOD, please upload it it and we will go from there.

Code:

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03853000 PsLoadedModuleList = 0xfffff800`03a90e50
Debug session time: Mon Dec 27 15:22:27.091 2010 (GMT-5)
System Uptime: 0 days 9:19:00.995
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff880030f9180, 6}

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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880030f9180, The PRCB address of the hung processor.
Arg4: 0000000000000006, 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:  
fffff800`04cd1938 fffff800`03871453 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`030f9180 : nt!KeBugCheckEx
fffff800`04cd1940 fffff800`038cbde7 : fffffa80`00000000 fffff800`00000006 00000000`00002710 fffff880`04405796 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff800`04cd19d0 fffff800`03814895 : fffff800`03839460 fffff800`04cd1b80 fffff800`03839460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`04cd1ad0 fffff800`038bfc33 : 00000000`00000000 fffff800`04cd1b80 00000000`00000000 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d
fffff800`04cd1b00 fffff880`045859c2 : fffff800`038d124a 00000000`003b9afa fffffa80`07b65578 fffff800`03a4bc40 : nt!KiInterruptDispatchNoLock+0x163
fffff800`04cd1c98 fffff800`038d124a : 00000000`003b9afa fffffa80`07b65578 fffff800`03a4bc40 00000000`00000001 : intelppm!C1Halt+0x2
fffff800`04cd1ca0 fffff800`038cbebc : fffff800`03a3de80 fffff800`00000000 00000000`00000000 fffff880`0150ec50 : nt!PoIdle+0x53a
fffff800`04cd1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


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
---------

Debug session time: Tue Dec 28 10:51:12.196 2010 (GMT-5)
System Uptime: 0 days 4:05:31.227
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F7, {9532bd0, 22be5a5c3e40, ffffdd41a5a3c1bf, 0}

Probably caused by : ntkrnlmp.exe ( nt!_report_gsfailure+25 )

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

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer.  This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned.  This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
variable(s).
Arguments:
Arg1: 0000000009532bd0, Actual security check cookie from the stack
Arg2: 000022be5a5c3e40, Expected security check cookie
Arg3: ffffdd41a5a3c1bf, Complement of the expected security check cookie
Arg4: 0000000000000000, zero

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


DEFAULT_BUCKET_ID:  GS_FALSE_POSITIVE_MISSING_GSFRAME

SECURITY_COOKIE:  Expected 000022be5a5c3e40 found 0000000009532bd0

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xF7

PROCESS_NAME:  BFBC2Game.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000396c4c5 to fffff800038d7740

STACK_TEXT:  
fffff880`0a458a08 fffff800`0396c4c5 : 00000000`000000f7 00000000`09532bd0 000022be`5a5c3e40 ffffdd41`a5a3c1bf : nt!KeBugCheckEx
fffff880`0a458a10 fffff800`038dc1fa : fffff880`0316a180 fffff800`038e4618 00000000`00000000 fffffa80`08b18870 : nt!_report_gsfailure+0x25
fffff880`0a458a50 fffff800`038825f4 : fffff800`03a51e00 fffffa80`060c0000 fffff880`0316a180 00000000`000000ff : nt!KiDeferredReadyThread+0x31a
fffff880`0a458ad0 fffff800`038db871 : fffffa80`0584b610 00000000`00000000 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0xc6c8
fffff880`0a458b50 fffff800`03bf4154 : fffff880`00000000 00000000`00000001 fffffa80`05506500 fffffa80`08d8a468 : nt!KeSetEvent+0x1e1
fffff880`0a458bc0 fffff800`038d6993 : fffffa80`099b0060 fffffa80`099b0060 fffff880`00000000 fffffa80`0584b610 : nt!NtSetEvent+0x90
fffff880`0a458c20 00000000`74a32dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008ebf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74a32dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!_report_gsfailure+25
fffff800`0396c4c5 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!_report_gsfailure+25

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0xF7_MISSING_GSFRAME_nt!_report_gsfailure+25

BUCKET_ID:  X64_0xF7_MISSING_GSFRAME_nt!_report_gsfailure+25

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

Debug session time: Wed Dec 29 11:09:07.575 2010 (GMT-5)
System Uptime: 0 days 0:49:10.479
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+5991952f01afdd94
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff88003121a38 -- (.exr 0xfffff88003121a38)
ExceptionAddress: fffff80003df76d7 (hal!KeQueryPerformanceCounter+0x00000000000000ff)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 00000000701de088
Attempt to execute non-executable address 00000000701de088

TRAP_FRAME:  fffff88003121ae0 -- (.trap 0xfffff88003121ae0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000002af07f663 rbx=0000000000000000 rcx=0000000000000001
rdx=00000abc00000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003df76d7 rsp=fffff88003121c70 rbp=0000000000000000
 r8=0000000000000000  r9=00000000003b9afa r10=0000000000000f43
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
hal!KeQueryPerformanceCounter+0xff:
fffff800`03df76d7 4885ff          test    rdi,rdi
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000387446e to fffff8000387c710

STACK_TEXT:  
fffff880`03120b28 fffff800`0387446e : 00000000`00000000 fffffa80`06594b38 fffff880`031212a0 fffff800`038a9668 : nt!KeBugCheck
fffff880`03120b30 fffff800`038a240d : fffff800`03a8aedc fffff800`039c3dac fffff800`0380c000 fffff880`03121a38 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`03120b60 fffff800`038a9a90 : fffff800`039cbb14 fffff880`03120bd8 fffff880`03121a38 fffff800`0380c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`03120b90 fffff800`038b69ef : fffff880`03121a38 fffff880`031212a0 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0x410
fffff880`03121270 fffff800`0387bd82 : fffff880`03121a38 00000000`00000000 fffff880`03121ae0 fffff880`030f9180 : nt!KiDispatchException+0x16f
fffff880`03121900 fffff800`0387a8fa : 00000000`00000008 00000000`00000000 fffff800`03889300 00000000`00000011 : nt!KiExceptionDispatch+0xc2
fffff880`03121ae0 fffff800`03df76d7 : 00000000`00000010 00000000`00000246 fffff880`03121c98 00000000`00000018 : nt!KiPageFault+0x23a
fffff880`03121c70 fffff800`0388a2c7 : 00000000`003b9afa 00000000`00000000 fffffa80`07bbb480 fffffa80`065ca8c0 : hal!KeQueryPerformanceCounter+0xff
fffff880`03121ca0 fffff800`03884ebc : fffff880`030f9180 fffff880`00000000 00000000`00000000 fffff880`05784480 : nt!PoIdle+0x5b7
fffff880`03121d80 00000000`00000000 : fffff880`03122000 fffff880`0311c000 fffff880`03121d40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`0387446e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

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

6: kd> lmtsmn
start             end                 module name
fffff880`04370000 fffff880`043ae000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00f03000 fffff880`00f5a000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02c00000 fffff880`02c8a000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`045c6000 fffff880`045dc000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`085e9000 fffff880`085f1000   ALSysIO64 ALSysIO64.sys Sun Apr 19 15:41:04 2009 (49EB7E50)
fffff880`01199000 fffff880`011a4000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`05611000 fffff880`05619000   ASACPI   ASACPI.sys   Wed Jul 15 23:31:29 2009 (4A5E9F11)
fffff880`044fb000 fffff880`04501000   AsIO     AsIO.sys     Mon Apr 06 03:21:08 2009 (49D9AD64)
fffff880`08420000 fffff880`0842b000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`01166000 fffff880`0116f000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0116f000 fffff880`01199000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`0124c000 fffff880`01253000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`0440e000 fffff880`044fb000   BHDrvx64 BHDrvx64.sys Mon Nov 15 18:11:35 2010 (4CE1BE27)
fffff880`0435f000 fffff880`04370000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`07355000 fffff880`07373000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff880`042c3000 fffff880`0435f000   ccHPx64  ccHPx64.sys  Fri Feb 05 16:05:45 2010 (4B6C8829)
fffff960`00730000 fffff960`00757000   cdd      cdd.dll      unavailable (00000000)
fffff880`00dc6000 fffff880`00df0000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00d06000 fffff880`00dc6000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01200000 fffff880`01230000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00ca8000 fffff880`00d06000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0155c000 fffff880`015cf000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`053ea000 fffff880`053fa000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`07271000 fffff880`0727a000   cpuz134_x64 cpuz134_x64.sys Fri Jul 09 07:16:58 2010 (4C37052A)
fffff880`06f34000 fffff880`06f42000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`04222000 fffff880`042a5000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`042a5000 fffff880`042c3000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`041ea000 fffff880`041f9000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`014c0000 fffff880`014d6000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`05da3000 fffff880`05dc5000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`06f4e000 fffff880`06f57000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`06f42000 fffff880`06f4e000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`06f57000 fffff880`06f6a000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`06f28000 fffff880`06f34000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`0563b000 fffff880`0572f000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`0572f000 fffff880`05775000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`04000000 fffff880`04076000   eeCtrl64 eeCtrl64.sys Fri May 21 17:44:45 2010 (4BF6FECD)
fffff880`08400000 fffff880`08420000   ENG64    ENG64.SYS    Mon Dec 13 20:47:30 2010 (4D06CCB2)
fffff880`04076000 fffff880`0409b000   EraserUtilRebootDrv EraserUtilRebootDrv.sys Fri May 21 17:44:45 2010 (4BF6FECD)
fffff880`0842f000 fffff880`085e9000   EX64     EX64.SYS     Mon Dec 13 20:55:48 2010 (4D06CEA4)
fffff880`0106e000 fffff880`01082000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`011a4000 fffff880`011f0000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`015e0000 fffff880`015ea000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01486000 fffff880`014c0000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`0179d000 fffff880`017e7000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`03de8000 fffff800`03e31000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`05775000 fffff880`05799000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`05d1b000 fffff880`05d34000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`05d34000 fffff880`05d3c080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`06ed2000 fffff880`06ee0000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`0728d000 fffff880`07355000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`01612000 fffff880`0161b000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`0416f000 fffff880`041ea000   IDSvia64 IDSvia64.sys Fri Nov 05 17:13:11 2010 (4CD47367)
fffff880`04527000 fffff880`0453d000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`040cc000 fffff880`040f3000   Ironx64  Ironx64.SYS  Tue Apr 27 20:48:23 2010 (4BD785D7)
fffff880`010fd000 fffff880`0111d000   jraid    jraid.sys    Mon May 31 01:44:28 2010 (4C034CBC)
fffff880`05c1b000 fffff880`05c2a000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`06ee0000 fffff880`06eee000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00bcd000 fffff800`00bd7000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`05c3b000 fffff880`05c7e000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`01542000 fffff880`0155c000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01772000 fffff880`0179d000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`05dc5000 fffff880`05dca200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`06fd9000 fffff880`06fee000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`06f95000 fffff880`06fb8000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c50000 fffff880`00c94000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`06f87000 fffff880`06f95000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`05c2a000 fffff880`05c39000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`06eee000 fffff880`06efb000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`0114c000 fffff880`01166000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`07373000 fffff880`0738b000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`0738b000 fffff880`073b8000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`07200000 fffff880`0724e000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`0724e000 fffff880`07271000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`00c12000 fffff880`00c1d000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00f63000 fffff880`00f6d000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`014e4000 fffff880`01542000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`04164000 fffff880`0416f000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01600000 fffff880`01612000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01620000 fffff880`01712000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0562e000 fffff880`0563a000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`043ae000 fffff880`043dd000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`05d02000 fffff880`05d17000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02dd1000 fffff880`02de0000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02c8a000 fffff880`02ccf000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01712000 fffff880`01772000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`00c1d000 fffff880`00c2e000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`04158000 fffff880`04164000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`0380c000 fffff800`03de8000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01255000 fffff880`013f8000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`01243000 fffff880`0124c000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`05c90000 fffff880`05ca8000   nusb3hub nusb3hub.sys Thu Apr 22 21:34:35 2010 (4BD0F92B)
fffff880`0453d000 fffff880`0456d000   nusb3xhc nusb3xhc.sys Thu Apr 22 21:34:36 2010 (4BD0F92C)
fffff880`053e8000 fffff880`053e9180   nvBridge nvBridge.kmd Tue Nov 09 11:30:43 2010 (4CD97733)
fffff880`05d3d000 fffff880`05d66000   nvhda64v nvhda64v.sys Tue Sep 07 16:08:40 2010 (4C869BC8)
fffff880`0480b000 fffff880`053e7f00   nvlddmkm nvlddmkm.sys Tue Nov 09 11:36:26 2010 (4CD9788A)
fffff880`02dab000 fffff880`02dd1000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00fad000 fffff880`00fc2000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f6d000 fffff880`00fa0000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`010e6000 fffff880`010ed000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`010ed000 fffff880`010fd000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`015cf000 fffff880`015e0000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`07880000 fffff880`07926000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`05d66000 fffff880`05da3000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00c94000 fffff880`00ca8000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`045dc000 fffff880`04600000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`043dd000 fffff880`043f8000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`04200000 fffff880`04221000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`02cd8000 fffff880`02cf2000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`04107000 fffff880`04158000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`04400000 fffff880`0440b000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`00df0000 fffff880`00df9000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`00c00000 fffff880`00c09000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`00c09000 fffff880`00c12000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`0144c000 fffff880`01486000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`06c00000 fffff880`06c18000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`0456f000 fffff880`045c6000   Rt64win7 Rt64win7.sys Mon Mar 22 05:57:14 2010 (4BA73EFA)
fffff880`06ca2000 fffff880`06ec8300   RTKVHD64 RTKVHD64.sys Fri Jan 29 01:48:35 2010 (4B6284C3)
fffff880`04800000 fffff880`0480a900   SaiBus   SaiBus.sys   Fri Apr 23 06:59:38 2010 (4BD17D9A)
fffff880`06efb000 fffff880`06f28000   SaiK0CCC SaiK0CCC.sys Fri Apr 23 06:59:33 2010 (4BD17D95)
fffff880`05d17000 fffff880`05d1ae80   SaiMini  SaiMini.sys  Fri Apr 23 06:59:38 2010 (4BD17D9A)
fffff880`06ec9000 fffff880`06ed1680   SaiU0CCC SaiU0CCC.sys Fri Apr 23 06:59:27 2010 (4BD17D8F)
fffff880`0111d000 fffff880`0114c000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`07926000 fffff880`07931000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`05619000 fffff880`05625000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`02de0000 fffff880`02dfd000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`017f7000 fffff880`017ff000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`07b17000 fffff880`07b9d000   SRTSP64  SRTSP64.SYS  Wed Feb 24 18:59:29 2010 (4B85BD61)
fffff880`040f3000 fffff880`04107000   SRTSPX64 SRTSPX64.SYS Wed Feb 24 18:59:48 2010 (4B85BD74)
fffff880`07a81000 fffff880`07b17000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`07978000 fffff880`079df000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`07931000 fffff880`0795e000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`0795e000 fffff880`07966000   SSPORT   SSPORT.sys   Thu Aug 11 19:07:32 2005 (42FBDA34)
fffff880`05c39000 fffff880`05c3a480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01000000 fffff880`0106e000   SYMDS64  SYMDS64.SYS  Mon Aug 17 19:35:30 2009 (4A89E942)
fffff880`00e00000 fffff880`00e3b000   SYMEFA64 SYMEFA64.SYS Wed Apr 21 17:47:39 2010 (4BCF727B)
fffff880`02d75000 fffff880`02dab000   SYMEVENT64x86 SYMEVENT64x86.SYS Thu Aug 13 18:28:21 2009 (4A849385)
fffff880`02cff000 fffff880`02d75000   SYMTDIV  SYMTDIV.SYS  Tue May 04 00:38:27 2010 (4BDFA4C3)
fffff880`01803000 fffff880`01a00000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`07966000 fffff880`07978000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`02cf2000 fffff880`02cff000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`00c2e000 fffff880`00c4c000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`040b8000 fffff880`040cc000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00530000 fffff960`0053a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`04501000 fffff880`04527000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`05c7e000 fffff880`05c90000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`06f6a000 fffff880`06f87000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`0456d000 fffff880`0456ef00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`05600000 fffff880`05611000   usbehci  usbehci.sys  Sat Oct 24 00:27:33 2009 (4AE28235)
fffff880`05ca8000 fffff880`05d02000   usbhub   usbhub.sys   Sat Oct 24 00:28:24 2009 (4AE28268)
fffff880`057a6000 fffff880`057fc000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`05799000 fffff880`057a6000   usbuhci  usbuhci.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00fa0000 fffff880`00fad000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`011f0000 fffff880`011fe000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`00fd7000 fffff880`00ffc000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`017e7000 fffff880`017f7000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00fc2000 fffff880`00fd7000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0108a000 fffff880`010e6000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01400000 fffff880`0144c000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`0409d000 fffff880`040b8000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`00e3b000 fffff880`00e4b000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e50000 fffff880`00ef4000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00ef4000 fffff880`00f03000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02ccf000 fffff880`02cd8000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00050000 fffff960`00360000   win32k   win32k.sys   unavailable (00000000)
fffff880`05625000 fffff880`0562e000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00f5a000 fffff880`00f63000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`06fb8000 fffff880`06fd9000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)

Unloaded modules:
fffff880`07a00000 fffff880`07a71000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`014d6000 fffff880`014e4000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`015ea000 fffff880`015f6000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`015f6000 fffff880`015ff000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01230000 fffff880`01243000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

Thank you i'll do the things you said asap, but i didnt overclock it my self i brought Overclocked 3XS Bundle from scan.co.uk, so how would u resit the overclock?

nommy said:

Thank you i'll do the things you said asap, but i didnt overclock it my self i brought Overclocked 3XS Bundle from scan.co.uk, so how would u resit the overclock?

You will need the hardware Gurus to answer that question. I think I know the answer; but I do not want to lead you wrong. I will ask one of them to look at this thread.

nommy said:

hi CarlTR6 i did what you told me to do and so far so good, just running stress test to see if my processor is over heating. just want to thank you again for your help .

You are welcome for the help. You want to know if you are overheating and if you have a bad component.

If the system was purchased that way, it is probably best to go back to the vendor for a replacement or repair. If it is out of warranty, then it might make sense to play around with bios settings. However, if it is overclocked and you are getting CPU interrupt lockups like this, it is something the vendor should be fixing for you as the hardware is not stable at the speed it is overclocked to and sold at. You can see an overclock in a dump file via "!sysinfo cpuinfo" for reference.

Agree with cluberti, if you bought an overclocked system they should check/repair it to work as sold.

If they won't help you for any reason then someone here can help get it running stable.

Overclocking can be very time consuming to get to run stable or to find and adjust settings to fix any issues.

Thank you, cluberti and Dave.

You're welcome Carl.

Never an issue for you, Carl.