Solved Windows Freezes

[MvdB]

I just learned I have to start my own thread even though my issue seems to be identical to an existing one. Hope I'm doing this right....

The system is <2weeks old, everything new. Please see spec's in signature.

It has random freezes, sometimes after > 12 hours, sometimes within 4 hours.
I call it a freeze because that's exactly what happens. The screen remains exactly as it was when freezing, including the clock (and at the exact time of the freeze). The IR LED of the mouse is turned off at the instant of the freeze and the UTP/LAN leds flash crazily (and this seems to block the swith in the LAN).

I've turned automatic updates off, no difference. I've turned off all powersaving modes, including on BIOS. Firmware/motherboard new and fully up to date.

I've even had a freeze happen overnight whilst (only) running W7 resource-usage. Nothing to see there...

Thanks for any help!

 

[SledgeDG]

I took a look at your files. A dump file wasn't there and I must say my Dutch is a little rusty but I couldn't help noticing that your system has a problems with a PnPDriver

22-4-2011 21:42	Windows Error Reporting	Foutbucket , type 0
Naam van gebeurtenis: PnPDriverNotFound
Antwoord: Niet beschikbaar&#x000d

What Plug'nPlay Device had you added before the freezing started? Check with the manufacturer for appropriate drivers .
-DG

 

[MvdB]

SledgeDG, thx for your help! The only device(s) added after initial configuration of the total system, (just 2 weeks ago), are:

- a PS/2 keyboard that I still had and didn't buy with this build
- a Predator (Trust) Game mouse, USB

And I tried to get a Maxtor USB2 500Mb external drive to work. If the Maxtor had been cleanly removed from one of the other systems (Vista 32b) then it would be recognized ok on this W7 64b. However, it happened a few times that it was not recognized, specially after a freeze and subsequent restart on this W7 system.

I've since then removed the Maxtor and not connected it since last friday but continue to have the problems mentioned.

I can't pinpoint IF a device (the keyboard, mouse or the Maxtor) triggered anything. The keyboard and mouse were added immediately upon arrival (as they are needed for anything to happen on a system ) and I probably tried the external Maxtor (for file transport) within a day.

Any test I can do to pinpoint which pnp driver is missing? My Dutch is ok ...

PS... there is no dump file... it is not a BSOD but a real freeze where I can only do a hard restart.

 

[mgorman87]

--------------
System Devices
--------------
     Name: Renesas Electronics USB 3.0 Host Controller
Device ID: PCI\VEN_1033&DEV_0194&SUBSYS_84131043&REV_04\4&DDEC341&0&00E1
   Driver: n/a

     Name: Intel(R) 82801 PCI Bridge - 244E
Device ID: PCI\VEN_8086&DEV_244E&SUBSYS_844D1043&REV_B5\3&11583659&0&E6
   Driver: n/a

     Name: Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 5 - 1C18
Device ID: PCI\VEN_8086&DEV_1C18&SUBSYS_844D1043&REV_B5\3&11583659&0&E4
   Driver: n/a

     Name: 2nd generation Intel® Core™ processor family DRAM Controller - 0100
Device ID: PCI\VEN_8086&DEV_0100&SUBSYS_844D1043&REV_09\3&11583659&0&00
   Driver: n/a

     Name: Renesas Electronics USB 3.0 Host Controller
Device ID: PCI\VEN_1033&DEV_0194&SUBSYS_84131043&REV_04\4&108ABD8A&0&00E4
   Driver: n/a

     Name: Intel(R) P67 Express Chipset Family LPC Interface Controller - 1C46
Device ID: PCI\VEN_8086&DEV_1C46&SUBSYS_844D1043&REV_05\3&11583659&0&F8
   Driver: n/a

     Name: Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 4 - 1C16
Device ID: PCI\VEN_8086&DEV_1C16&SUBSYS_844D1043&REV_B5\3&11583659&0&E3
   Driver: n/a

     Name: Marvell 91xx SATA 6G Controller
Device ID: PCI\VEN_1B4B&DEV_9172&SUBSYS_84771043&REV_11\4&16B16BD2&0&00E7
   Driver: n/a

     Name: Intel(R) Management Engine Interface
Device ID: PCI\VEN_8086&DEV_1C3A&SUBSYS_844D1043&REV_04\3&11583659&0&B0
   Driver: n/a

     Name: Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 3 - 1C14
Device ID: PCI\VEN_8086&DEV_1C14&SUBSYS_844D1043&REV_B5\3&11583659&0&E2
   Driver: n/a

     Name: PCI standard PCI-to-PCI bridge
Device ID: PCI\VEN_1B21&DEV_1080&SUBSYS_10801B21&REV_01\4&2B6CC657&0&00E6
   Driver: n/a

     Name: Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C2D
Device ID: PCI\VEN_8086&DEV_1C2D&SUBSYS_844D1043&REV_05\3&11583659&0&D0
   Driver: n/a

     Name: Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 2 - 1C12
Device ID: PCI\VEN_8086&DEV_1C12&SUBSYS_844D1043&REV_B5\3&11583659&0&E1
   Driver: n/a

     Name: Standaard Dual Channel PCI IDE Controller
Device ID: PCI\VEN_197B&DEV_2362&SUBSYS_84601043&REV_10\4&20221DEA&0&00E3
   Driver: n/a

     Name: Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C26
Device ID: PCI\VEN_8086&DEV_1C26&SUBSYS_844D1043&REV_05\3&11583659&0&E8
   Driver: n/a

     Name: Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 1 - 1C10
Device ID: PCI\VEN_8086&DEV_1C10&SUBSYS_844D1043&REV_B5\3&11583659&0&E0
   Driver: n/a

     Name: VIA 1394 OHCI Compliant Host Controller
Device ID: PCI\VEN_1106&DEV_3044&SUBSYS_81FE1043&REV_C0\5&D93DF5B&0&0800E6
   Driver: n/a

     Name: Intel(R) 6 Series/C200 Series Chipset Family SMBus Controller - 1C22
Device ID: PCI\VEN_8086&DEV_1C22&SUBSYS_844D1043&REV_05\3&11583659&0&FB
   Driver: n/a

     Name: Intel(R) 6 Series/C200 Series Chipset Family 6 Port SATA AHCI Controller - 1C02
Device ID: PCI\VEN_8086&DEV_1C02&SUBSYS_844D1043&REV_05\3&11583659&0&FA
   Driver: n/a

     Name: NVIDIA GeForce GTX 570
Device ID: PCI\VEN_10DE&DEV_1081&SUBSYS_25511462&REV_A1\4&80E7924&0&0008
   Driver: n/a

     Name: High Definition Audio-besturing
Device ID: PCI\VEN_8086&DEV_1C20&SUBSYS_84361043&REV_05\3&11583659&0&D8
   Driver: n/a

     Name: Intel(R) 82579V Gigabit Network Connection
Device ID: PCI\VEN_8086&DEV_1503&SUBSYS_849C1043&REV_05\3&11583659&0&C8
   Driver: n/a

     Name: High Definition Audio-besturing
Device ID: PCI\VEN_10DE&DEV_0E09&SUBSYS_25511462&REV_A1\4&80E7924&0&0108
   Driver: n/a

     Name: Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 8 - 1C1E
Device ID: PCI\VEN_8086&DEV_1C1E&SUBSYS_844D1043&REV_B5\3&11583659&0&E7
   Driver: n/a

     Name: 2nd generation Intel® Core™ processor family PCI Express Controller - 0101
Device ID: PCI\VEN_8086&DEV_0101&SUBSYS_844D1043&REV_09\3&11583659&0&08
   Driver: n/a

It looks like your missing drivers for all your system devices. I compared to another persons file and there's shows drivers listed under all the devices where yours says N/A. I would go into device manager and see if there are devices with the yellow /!\.

 

[SledgeDG]

I know why there was no dump So I had to dig through the different system reports.
OK, as a fast shot from the hip: There is a Microsoft Hotfix available for Windows 7 systems that suffer from random freezes. That we should try first (as far as I know that fix is language neutral and not yet applied to your system)

A computer that is running Windows Server 2008 R2 or Windows 7 stops responding randomly

Be sure to reboot after applying that fix. In case that doesn't help we need to cover all bases and go from there.
Next step would be:
If you boot into safe mode, does the freezing still occur?
http://www.sevenforums.com/tutorials/69585-safe-mode.html

-DG

 

[MvdB]

Thanks all!

@Mgorman: You're right, that looks strange but all my devices work fine and no warnings in the device manager...

@SledgeDG: Thanks... however, I doubt this would fix it, I don't see evidence of lsass problems... but I'll give it a try if my current solution test fails...

What I'm trying now is (as a result of another posting in Crashes-Debugging) is that I've set my Asus Sabretooth in the high(est)speed mode instead of the 'balanced default'. That seems to have worked for others with a similar problem and has worked for me for 6 hours now...keeping fingers crossed.

 

[MvdB]

Thanks all!

@Mgorman: You're right, that looks strange but all my devices work fine and no warnings in the device manager...

@SledgeDG: Thanks... however, I doubt this would fix it, I don't see evidence of lsass problems... but I'll give it a try if my current solution test fails...

What I'm trying now is (as a result of another posting in Crashes-Debugging) is that I've set my Asus Sabretooth in the high(est)speed mode instead of the 'balanced default'. That seems to have worked for others with a similar problem and has worked for me for 6 hours now...keeping fingers crossed.

Ok... That wasn't it. Took longer this time but it still freezes...
i'll try SledgeDG' link now.... it appears to not be for my system. Which sounds reasonable as I'm not using the server software the fix is meant for.

Back to 0...

 

[MvdB]

update

Found a setting in the ethernet driver that tries to do some powersaving. Turned that off and haven been ok now for >15 hours.... fingers crossed.:huh:


Ok... again a freeze, this time it took much longer for it to happen though, > 30hours


It frooze around 0300 in the morning, about the time it W7 updates would be checked, were it not that I disabled automatic updates...? Again, the freeze is complete, including the clock. However, the ethernet connection flashes crazily. Not sure if that's polling from the other side as my PC does seem to really freeze...

 

[MvdB]

no improvement yet

Anybody any ideas? I still get random freezes, when idle... all energy settings (as far as I can tell) are off....

 

[SledgeDG]

OK these are some things I stumbled over when I checked your System information logs again.
They might not cause your problems but they don't necessarily promote a stable system:
#1:

28-4-2011 19:23	Application Error	Naam van toepassing met fout: setup.exe_ASUS AI Suite II, versie: 1.1.6.4, tijdstempel: 0x4d061d9b
Naam van module met fout: KERNELBASE.dll, versie: 6.1.7601.17514, tijdstempel: 0x4ce7bafa
Uitzonderingscode: 0x0eedfade
Foutoffset: 0x0000b727
Id van proces met fout: 0x758
Starttijd van toepassing met fout: 0x01cc05d9af60dc57
Pad naar toepassing met fout: X:\Software\AISuite_II\setup.exe
Pad naar module met fout: C:\Windows\syswow64\KERNELBASE.dll
Rapport-id: 0751f69d-71cd-11e0-b3b9-f46d0496aa76

Do you overclock? If so, take it back to the default settings until we're sure that's not it. Uninstall the ASUS AI-Booster. The very same goes for the MSI Afterburner (which is known to cause problems as well.) Remember: Overclocking is evil you operate system components under conditions they weren't made/certified for!!
#2: I found traces of Norton/Symantec software. I suggest you de-install it with the appropriate tools and get either MSE or Avast for the time being. (Once we can confirm that those are "innocent" you may re-install Symantec if you so desire.

Norton uninstaller
Symantec uninstaller

MSE

Avast

-DG

 

[MvdB]

Thanks SledgeDG, I had just de-installed AI Suite that came with the ASUS Sabertooth motherboard. I liked the temp checks it reported....

I'm not overclocking on the cores... however, my GTX is slightly pumped up, I didn't do it, it was bought and installed that way. If AISuite de-install doesn't help I'll try your suggestions one by one....

 

[SledgeDG]

That's the spirit We'll get to the bottom of this one way or another. And when all is sorted out and we've found the real culprit you just re install whatever you think you need of those tools.

-DG

 

[MvdB]

last two days I ran a sort of interim test: I let the computer run SETI@home calculations when idle. The pc ran stable for an incredible 2 days... however, just now after 10 mins of surfing on internet and then leaving it alone (SETI kicks in within 15 mins of idleness) it froze again.... within 5 minutes of idle Chrome screen.... Now to analyse what it tried to do in those 5 min's..

 

[SledgeDG]

Computer only freezes when idle...that rings a bell...

It might be a long-shot but it can't hurt to try:
Sabertooth has AMI BIOS, right?
Go in your BIOS in the Power settings and switch Suspend Mode from "AUTO" to "S1(POS) only"

-DG

 

[MvdB]

update - not getting anywhere yet

After trying loads of stuff, nothing really works. I'm nearly out of options.
I thought I had it when, after disabeling all automatic updates, things seemed a bit more stable (ie a clean run for a little more that 24 hours). However I've never had >2 days stability. Even though I can't really see what causes it (as there are no dumps with a freeze) I still get the impression that background update processes are responsible. For example, after half a day of ok running, it will freeze and after restart, the first thing that comes up is an Adobe update screen... that probably checked for updates just before.

I'm now looking for possible settings within W7 that might cause freezes (from a security standpoint?) when an application or W7 itself, tries to check for, get, and/or install, an update. Could there be a problem (as an example) that the update process is run with the authorisation of a 'normal' user and that it freezes up when some part of the process might need admin rights? Any idea on how to check these perm's generically? Or do I have to go through all software update porcesses to check?

Thx,
Mark

 

[SledgeDG]

I don't think that's the issue. If a regular update causes freeze in your comp while it works for millions of other users, the issue lies deeper. Switch off all (if any) screensavers. They're known to overflow buffers at times.
You can try to run in safe mode with network (I know it's a pain in the rear). But if that works, it's certain that a 3rd party driver is responsible. In that case uninstall with
Guru3D - Driver Sweeper or Phyxion.net - Driver Sweeper
and get the newest drivers for your installation
Other major causes could be corrupted memory
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
or even a corrupted installation
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Another thing you could try: go into msconfig and uncheck everything that is not firewall or Antivirus related. and see how that plays out...most of that stuff that gets written into autostart doesn't have to be there.

As another idea..check your harddrive with this test (short test and then long test...even brand new HDDs can be faulty)
SeaTools for DOS | Seagate

Keep me posted
-DG

 

[MvdB]

finally a dmp file....

Today I got a mini dump file. In a bit of a strange way though. After running multiple succesful memtest passes and pressing escape to exit that and reboot, it rebooted with a BSOD notification and the rebooted again, fine.

But I dit get a dmp file that time... see attached

 

[MvdB]

Update - latency checker - networkadapter

I found out I had peaks in cpu interrupts. As a check I started DPC LAtency checker and disabled devices one by one as something is causing great peaks. A bad driver somewhere. Looks like the ethernetcard (on board on the ASUS Sabretooth) has something to do with it. The snip attached is what happened when i turned the driver on again.

I get similar peaks when swithching from one internet (or chrome) tab to the next.

I have the newest driver on it so I have no idea how to continue...

 

[SledgeDG]

The crash was blamed on your video driver

nvlddmkm.sys Fri May 13 23:55:21 2011 (4DCDFD29)

which you just recently updated. If that's an isolated incident, I would write it off as a glitch.
Otherwise roll back to the previous version or remove driver with one of the aforementioned driver sweepers and try again.
As for your spike problem check this and cross reference with that latency checker
Download What's My Computer Doing? 1.02 Free - It shows all programs that are accessing your hard disk or using the CPU - Softpedia
The on board chip doesn't do anything on its own. So uninstall whatever causes the spikes and you're golden

-DG

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


Loading Dump File [C:\Users\David\Desktop\MvdB\060911-19609-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 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03014000 PsLoadedModuleList = 0xfffff800`03259650
Debug session time: Thu Jun  9 09:11:14.735 2011 (GMT-4)
System Uptime: 0 days 0:00:10.578
Loading Kernel Symbols
...............................................................
..................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8000308a8b4, fffff8800375a6e8, fffff88003759f40}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+aa274 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8000308a8b4, The address that the exception occurred at
Arg3: fffff8800375a6e8, Exception Record Address
Arg4: fffff88003759f40, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!memcpy+204
fffff800`0308a8b4 488b040a        mov     rax,qword ptr [rdx+rcx]

EXCEPTION_RECORD:  fffff8800375a6e8 -- (.exr 0xfffff8800375a6e8)
ExceptionAddress: fffff8000308a8b4 (nt!memcpy+0x0000000000000204)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 000000010fbeea58
Attempt to read from address 000000010fbeea58

CONTEXT:  fffff88003759f40 -- (.cxr 0xfffff88003759f40)
rax=fffff8a000df7ff0 rbx=0000000000000008 rcx=fffff8a000df7ff0
rdx=000007610edf6a68 rsi=fffff8a000df7ff0 rdi=0000000000000008
rip=fffff8000308a8b4 rsp=fffff8800375a928 rbp=fffff8800375acf0
 r8=0000000000000008  r9=0000000000000001 r10=fffffa80066a0148
r11=fffff8a000df7ff0 r12=000000000000000a r13=fffff8800375aa68
r14=000000010fbeea58 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!memcpy+0x204:
fffff800`0308a8b4 488b040a        mov     rax,qword ptr [rdx+rcx] ds:002b:00000001`0fbeea58=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  000000010fbeea58

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c3100
 000000010fbeea58 

FOLLOWUP_IP: 
nvlddmkm+aa274
fffff880`0f4ac274 ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8000338f7c2 to fffff8000308a8b4

STACK_TEXT:  
fffff880`0375a928 fffff800`0338f7c2 : fffffa80`00000001 00000000`00000008 00000000`00000000 00000000`000007ff : nt!memcpy+0x204
fffff880`0375a930 fffff800`0338ce2b : fffffa80`09da3d60 fffff880`0375ada0 00000000`00000001 fffff880`0375ad30 : nt!ObpCaptureObjectName+0x102
fffff880`0375a9b0 fffff800`0338cee5 : fffffa80`066aca60 fffffa80`067284a0 00000000`0000006c 00000000`00000000 : nt!ObpCaptureObjectCreateInformation+0x279
fffff880`0375aa30 fffff800`0332a50e : fffffa80`0672b040 fffff880`0375abb0 fffff880`0375ad30 00000000`00000000 : nt!ObCreateObject+0x75
fffff880`0375aaa0 fffff800`03092f93 : fffffa80`0672b040 00000000`c000009a 00000000`00000000 fffffa80`08ba6000 : nt!NtCreateSymbolicLinkObject+0xbe
fffff880`0375ab30 fffff800`0308f530 : fffff800`034027b6 00000000`000090de fffffa80`0a7c8080 fffff980`2f418fa0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0375acc8 fffff800`034027b6 : 00000000`000090de fffffa80`0a7c8080 fffff980`2f418fa0 fffffa80`0a7c8080 : nt!KiServiceLinkage
fffff880`0375acd0 fffff880`0f4ac274 : 00000000`00000000 fffffa80`0a7c8080 00000000`c000009a fffff800`03421ed1 : nt!IoCreateSymbolicLink+0x46
fffff880`0375ad30 00000000`00000000 : fffffa80`0a7c8080 00000000`c000009a fffff800`03421ed1 fffff980`00000100 : nvlddmkm+0xaa274


SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  nvlddmkm+aa274

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dcdfd29

STACK_COMMAND:  .cxr 0xfffff88003759f40 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+aa274

BUCKET_ID:  X64_0x7E_nvlddmkm+aa274

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

4: kd> lmntsm
start             end                 module name
fffff880`00f6e000 fffff880`00fc5000   ACPI     ACPI.sys     Sat Nov 20 04:19:16 2010 (4CE79294)
fffff880`04678000 fffff880`04701000   afd      afd.sys      Sat Nov 20 04:23:27 2010 (4CE7938F)
fffff880`01237000 fffff880`01242000   amdxata  amdxata.sys  Fri Mar 19 12:18:18 2010 (4BA3A3CA)
fffff880`05726000 fffff880`0572c000   AsIO     AsIO.sys     Mon Aug 23 21:53:02 2010 (4C7325FE)
fffff880`0571f000 fffff880`05726000   AsUpIO   AsUpIO.sys   Mon Aug 02 22:47:59 2010 (4C57835F)
fffff880`013aa000 fffff880`013b3000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`013b3000 fffff880`013dd000   ataport  ataport.SYS  Sat Nov 20 04:19:15 2010 (4CE79293)
fffff880`041d4000 fffff880`041db000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`05607000 fffff880`0571f000   BHDrvx64 BHDrvx64.sys Wed Apr 13 20:16:01 2011 (4DA63CC1)
fffff880`0494e000 fffff880`0495f000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`041a1000 fffff880`041cb000   cdrom    cdrom.sys    Sat Nov 20 04:19:20 2010 (4CE79298)
fffff880`00cfc000 fffff880`00dbc000   CI       CI.dll       Sat Nov 20 08:12:36 2010 (4CE7C944)
fffff880`01d94000 fffff880`01dc4000   CLASSPNP CLASSPNP.SYS Sat Nov 20 04:19:23 2010 (4CE7929B)
fffff880`00c9e000 fffff880`00cfc000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0145e000 fffff880`014d0000   cng      cng.sys      Sat Nov 20 05:08:45 2010 (4CE79E2D)
fffff880`01dc4000 fffff880`01dd2000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`04930000 fffff880`0494e000   dfsc     dfsc.sys     Sat Nov 20 04:26:31 2010 (4CE79447)
fffff880`04921000 fffff880`04930000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01d7e000 fffff880`01d94000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0418e000 fffff880`041a1000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`040fa000 fffff880`04186000   dump_mv91xx dump_mv91xx.sys Fri Aug 27 05:49:22 2010 (4C778A22)
fffff880`04186000 fffff880`0418e000   dump_mvxxmm dump_mvxxmm.sys Fri Aug 27 05:49:03 2010 (4C778A0F)
fffff880`01dd2000 fffff880`01ddc000   dump_scsiport dump_scsiport.sys Fri Apr 22 16:04:32 2011 (4DB1DF50)
fffff880`100b5000 fffff880`101a9000   dxgkrnl  dxgkrnl.sys  Sat Nov 20 04:50:50 2010 (4CE799FA)
fffff880`101a9000 fffff880`101ef000   dxgmms1  dxgmms1.sys  Sat Nov 20 04:49:53 2010 (4CE799C1)
fffff880`04882000 fffff880`048fb000   eeCtrl64 eeCtrl64.sys Tue May 03 00:23:25 2011 (4DBF833D)
fffff880`048fb000 fffff880`04921000   EraserUtilRebootDrv EraserUtilRebootDrv.sys Tue May 03 00:23:25 2011 (4DBF833D)
fffff880`01242000 fffff880`01256000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01000000 fffff880`0104c000   fltmgr   fltmgr.sys   Sat Nov 20 04:19:24 2010 (4CE7929C)
fffff880`0162c000 fffff880`01636000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01d44000 fffff880`01d7e000   fvevol   fvevol.sys   Sat Nov 20 04:24:06 2010 (4CE793B6)
fffff880`01c51000 fffff880`01c9b000   fwpkclnt fwpkclnt.sys Sat Nov 20 04:21:37 2010 (4CE79321)
fffff800`035fd000 fffff800`03646000   hal      hal.dll      Sat Nov 20 08:00:25 2010 (4CE7C669)
fffff880`01d3b000 fffff880`01d44000   hwpolicy hwpolicy.sys Sat Nov 20 04:18:54 2010 (4CE7927E)
fffff880`01256000 fffff880`013aa000   iaStor   iaStor.sys   Sat Nov 06 03:44:52 2010 (4CD50774)
fffff880`04807000 fffff880`04882000   IDSvia64 IDSvia64.sys Fri Mar 11 21:15:42 2011 (4D7AD74E)
fffff880`047d0000 fffff880`047fd000   Ironx64  Ironx64.SYS  Fri Nov 12 18:06:50 2010 (4CDDC88A)
fffff800`00ba6000 fffff800`00bb0000   kdcom    kdcom.dll    Sat Feb 05 11:52:49 2011 (4D4D8061)
fffff880`01600000 fffff880`0161b000   ksecdd   ksecdd.sys   Sat Nov 20 04:21:15 2010 (4CE7930B)
fffff880`01860000 fffff880`0188b000   ksecpkg  ksecpkg.sys  Sat Nov 20 05:10:34 2010 (4CE79E9A)
fffff880`00c3b000 fffff880`00c8a000   mcupdate mcupdate.dll Sat Nov 20 08:03:51 2010 (4CE7C737)
fffff880`01154000 fffff880`0116e000   mountmgr mountmgr.sys Sat Nov 20 04:19:21 2010 (4CE79299)
fffff880`013dd000 fffff880`013e8000   msahci   msahci.sys   Sat Nov 20 05:33:58 2010 (4CE7A416)
fffff880`04050000 fffff880`0405b000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00fce000 fffff880`00fd8000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01400000 fffff880`0145e000   msrpc    msrpc.sys    Sat Nov 20 04:21:56 2010 (4CE79334)
fffff880`040e7000 fffff880`040f2000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01d29000 fffff880`01d3b000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`0116e000 fffff880`011fa000   mv91xx   mv91xx.sys   Fri Aug 27 05:49:22 2010 (4C778A22)
fffff880`0122f000 fffff880`01237000   mvxxmm   mvxxmm.sys   Fri Aug 27 05:49:03 2010 (4C778A0F)
fffff880`018e0000 fffff880`019d3000   ndis     ndis.sys     Sat Nov 20 04:23:30 2010 (4CE79392)
fffff880`04775000 fffff880`04784000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`04701000 fffff880`04746000   netbt    netbt.sys    Sat Nov 20 04:23:18 2010 (4CE79386)
fffff880`01800000 fffff880`01860000   NETIO    NETIO.SYS    Sat Nov 20 04:23:13 2010 (4CE79381)
fffff880`0405b000 fffff880`0406c000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`04666000 fffff880`04672000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`03014000 fffff800`035fd000   nt       ntkrnlmp.exe Sat Apr 09 00:15:23 2011 (4D9FDD5B)
fffff880`01652000 fffff880`017f5000   Ntfs     Ntfs.sys     Thu Mar 10 22:39:39 2011 (4D79997B)
fffff880`041cb000 fffff880`041d4000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`100b0000 fffff880`100b5000   nvBridge nvBridge.kmd Fri May 13 23:47:37 2011 (4DCDFB59)
fffff880`0f402000 fffff880`100b0000   nvlddmkm nvlddmkm.sys Fri May 13 23:55:21 2011 (4DCDFD29)
fffff880`0474f000 fffff880`04775000   pacer    pacer.sys    Sat Nov 20 05:52:18 2010 (4CE7A862)
fffff880`00e40000 fffff880`00e55000   partmgr  partmgr.sys  Sat Nov 20 04:20:00 2010 (4CE792C0)
fffff880`00e00000 fffff880`00e33000   pci      pci.sys      Sat Nov 20 04:19:11 2010 (4CE7928F)
fffff880`0113d000 fffff880`01144000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`01144000 fffff880`01154000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`0161b000 fffff880`0162c000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00c8a000 fffff880`00c9e000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`0188b000 fffff880`018dc000   rdbss    rdbss.sys    Sat Nov 20 04:27:51 2010 (4CE79497)
fffff880`04035000 fffff880`0403e000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`0403e000 fffff880`04047000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`04047000 fffff880`04050000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`01cef000 fffff880`01d29000   rdyboost rdyboost.sys Sat Nov 20 04:43:10 2010 (4CE7982E)
fffff880`01200000 fffff880`0122f000   SCSIPORT SCSIPORT.SYS Sat Nov 20 05:34:01 2010 (4CE7A419)
fffff880`04784000 fffff880`047a1000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`01ce7000 fffff880`01cef000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`040d1000 fffff880`040e7000   SRTSPX64 SRTSPX64.SYS Tue Mar 29 22:46:18 2011 (4D92997A)
fffff880`0104c000 fffff880`010bd000   SYMDS64  SYMDS64.SYS  Tue Dec 07 19:16:58 2010 (4CFECE7A)
fffff880`014de000 fffff880`015c2000   SYMEFA64 SYMEFA64.SYS Sun Mar 13 23:20:58 2011 (4D7D899A)
fffff880`0409b000 fffff880`040d1000   SYMEVENT64x86 SYMEVENT64x86.SYS Thu Mar 24 19:02:36 2011 (4D8BCD8C)
fffff880`04600000 fffff880`04666000   SYMNETS  SYMNETS.SYS  Thu Mar 17 23:24:33 2011 (4D82D071)
fffff880`01a4d000 fffff880`01c51000   tcpip    tcpip.sys    Sat Nov 20 04:25:52 2010 (4CE79420)
fffff880`0408e000 fffff880`0409b000   TDI      TDI.SYS      Sat Nov 20 04:22:06 2010 (4CE7933E)
fffff880`0406c000 fffff880`0408e000   tdx      tdx.sys      Sat Nov 20 04:21:54 2010 (4CE79332)
fffff880`047bc000 fffff880`047d0000   termdd   termdd.sys   Sat Nov 20 06:03:40 2010 (4CE7AB0C)
fffff880`0572c000 fffff880`05752000   tunnel   tunnel.sys   Sat Nov 20 05:51:50 2010 (4CE7A846)
fffff880`00e33000 fffff880`00e40000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`041db000 fffff880`041e9000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`04000000 fffff880`04025000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00e55000 fffff880`00e6a000   volmgr   volmgr.sys   Sat Nov 20 04:19:28 2010 (4CE792A0)
fffff880`010e1000 fffff880`0113d000   volmgrx  volmgrx.sys  Sat Nov 20 04:20:43 2010 (4CE792EB)
fffff880`01c9b000 fffff880`01ce7000   volsnap  volsnap.sys  Sat Nov 20 04:20:08 2010 (4CE792C8)
fffff880`047a1000 fffff880`047bc000   wanarp   wanarp.sys   Sat Nov 20 05:52:36 2010 (4CE7A874)
fffff880`04025000 fffff880`04035000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00ebb000 fffff880`00f5f000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f5f000 fffff880`00f6e000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`04746000 fffff880`0474f000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`00fc5000 fffff880`00fce000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)

 

[MvdB]

Thanks!

The 'what's my computer doing' doesn't show anything out of the ordinary nor can I link it's output to the spikes in the latency checker. Would you be worried by perfmon saying, as a warning, that you have too many CPU interrupts?