Bluescreen/Computer keeps crashing every couple hours everyday
ล็อกแล้ว
-
Monday, August 20, 2012 7:51 PM
Hi all,
My windows server 2008 R2 machine has been crashing a few times everyday lately.
I have attached a link to all the files needed to described the issues. Any helps would be much appreciated.
https://skydrive.live.com/?cid=CEEC9F80BC03B6F6&id=CEEC9F80BC03B6F6%21114&sc=documents
- Changed Type Cheers ZHANGMicrosoft Contingent Staff, Moderator Friday, August 31, 2012 6:36 AM
All Replies
-
Monday, August 20, 2012 9:31 PM
Run WhoCrashed on it possibly? I can't seem to pull up your files.
http://download.cnet.com/WhoCrashed/3000-2094_4-75205821.html
-
Tuesday, August 21, 2012 2:32 AMModerator
Hello,
You may update BIOS and hardware drivers
Uninstall new software installed before BSOD (if any)
Run chkdsk /r /f and sfc /scannow
Run RAM diagnosis and other hardware checks
If none of the above helps, please open a ticket with Microsoft Support to help analyze the dump files. You can contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently. http://support.microsoft.com/contactus/. If you are outside the US please http://www.microsoft.com/worldwide/ for regional support phone numbers.
Thanks
Zhang- Marked As Answer by Cheers ZHANGMicrosoft Contingent Staff, Moderator Friday, August 31, 2012 6:36 AM
-
Tuesday, August 21, 2012 12:24 PMThanks for fast response. I will let you know what I found out.
skong
-
Tuesday, August 21, 2012 12:55 PM
Hi abrrymnvette,
Below is the results after running WhoCrashed.
Welcome to WhoCrashed (HOME EDITION) v 3.06
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
Home Edition Notice
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
System Information (local)
computer name: ALXFSERVE
windows version: Windows Server 2008 R2 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8588353536 total
VM: 2147352576, free: 1987465216
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 8/21/2012 10:13:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082112-21294-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x74E01)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8000169A601, 0x2, 0xFFFFF80001852000)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Tue 8/21/2012 10:13:30 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8000169A601, 0x2, 0xFFFFF80001852000)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 8/20/2012 7:43:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082012-21980-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80001B97A54, 0xFFFFF88004FA7770, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 8/20/2012 6:24:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082012-23462-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFFA800800EA30, 0xFFFFF88005373B10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 8/20/2012 5:43:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082012-22011-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 8/19/2012 4:58:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081912-22261-01.dmp
This was probably caused by the following module: srv2.sys (srv2+0x4109B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF8800569809B, 0xFFFFF88005C603E8, 0xFFFFF88005C5FC50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\srv2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Smb 2.0 Server driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sun 8/19/2012 4:57:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081912-21481-01.dmp
This was probably caused by the following module: hal.dll (hal+0x133EC)
Bugcheck code: 0xA (0x40, 0xD, 0x1, 0xFFFFF80001DF33EC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sun 8/19/2012 4:39:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081912-21684-01.dmp
This was probably caused by the following module: hal.dll (hal+0x133EC)
Bugcheck code: 0xA (0x40, 0xD, 0x1, 0xFFFFF80001DF33EC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Wed 8/15/2012 2:55:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081512-22401-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 8/13/2012 8:26:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081312-21403-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xD1 (0x1001, 0x2, 0x0, 0xFFFFF880012D4919)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 8/12/2012 3:20:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081212-21294-01.dmp
This was probably caused by the following module: vid.sys (Vid+0x4DA0)
Bugcheck code: 0xBE (0xFFFFF88003004DA0, 0x2208A4121, 0xFFFFF88006959810, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\vid.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hyper-V Infrastructure Driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sun 8/12/2012 1:04:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081212-21496-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xD1 (0x1001, 0x2, 0x0, 0xFFFFF88000C77919)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 8/12/2012 12:50:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081212-21855-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70710)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 8/12/2012 8:58:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081212-21590-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF8000187DB41)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 8/11/2012 4:13:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081112-21340-01.dmp
This was probably caused by the following module: ndis.sys (NDIS+0x956A)
Bugcheck code: 0xD1 (0x1, 0x2, 0x1, 0xFFFFFA8007269A90)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
Conclusion
32 crash dumps have been found and analyzed. Only 15 are included in this report. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
skong
-
Tuesday, August 21, 2012 1:12 PM
This forum is meant for General Toubleshooting for Windows Server. Analyzing the crash dump is a different task and Microsoft has its dedicated team to deal with this issue. You can contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently. http://support.microsoft.com/contactus/. If you are outside the US please http://www.microsoft.com/worldwide/ for regional support phone numbers.
Hopeyour problem will be resolved soon.http://www.arabitpro.com
-
Tuesday, August 21, 2012 5:39 PM
Hi Is it crashing on main Machine or you use Microsot Virtual Machine or Vm to use server 2008. If It has been happning on main Machine I mean
on host. first of all make sure you have not installed any software or hardware recently and update the BIOS and if the BIOS is already updated
then check the hard disk space and run the chkdsk I would advice you to use chkdsk /r /f after it run sfc /scannow command in command line
update the driver you can check the driver by typing in run box sigverif you will get a box with three option you need to click on start and wait
unless it checkes all the signed drivers , once the process is complete click on advance option and view the log . It will open a txt file you need
to check all the drivers are signed driver . you can run the Memory check as well for the confirmation . if you don't get the solution of this issue
unplug all the external devices you have connected to the Machine and attach them one by one restart your computer . Check all the device by one. I believe you will get the solution of this issue.
Thanks & best Regards
Ankit Tyagi
-
Tuesday, August 21, 2012 6:57 PM
Hi tyagiankit36,
Thanks for suggestions. I have windows server 2008 R2 on main machine and I am running Windows 7 64 bit on the hyper-v VM. I didn't install any software or drivers lately. I will see if BIOS update is available for this since it is a custom built machine. (Need to find out the model of the motherboard). I will follow the suggestions and let you know what I find out.
Thanks you very much for your time!
Jaden
- Edited by Jaden Kong Tuesday, August 21, 2012 7:06 PM
-
Tuesday, August 21, 2012 7:41 PM
Hi
tyagiankit36,All my drivers are signed. I've tried updating BIOS it says it it's not compatible with my Windows version.
http://www.gigabyte.us/products/product-page.aspx?pid=2740&dl=1#bios
GA-EP35C-DS3R
I had F3 version installed. I download F4 but the BIOS won't let me run it.
********************************
Microsoft Signature Verification
Log file generated on 8/21/2012 at 3:36 PM
OS Platform: Windows (x64), Version: 6.1, Build: 7600, CSDVersion:
Scan Results: Total Files: 105, Signed: 105, Unsigned: 0, Not Scanned: 0
File Modified Version Status Catalog Signed By
------------------ ------------ ----------- ------------ ----------- -------------------
[c:\windows\system32]
batt.dll 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
clfs.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
storprop.dll 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
streamci.dll 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
sysfxui.dll 7/13/2009 2:5.1 Signed Microsoft-Windows-SeMicrosoft Windows
vid.dll 7/13/2009 2:5.1 Signed Package_1_for_KB9778Microsoft Windows
vmbuspipe.dll 7/13/2009 2:5.1 Signed Package_2_for_KB2345Microsoft Windows
vmbusres.dll 7/13/2009 2:5.1 Signed Package_2_for_KB2345Microsoft Windows
wmalfxgfxdsp.dll 7/13/2009 2:5.1 Signed Microsoft-Windows-SeMicrosoft Windows
[c:\windows\system32\drivers]
3waredrv.sys 11/19/2009 2:5.2 Signed amccdrv9.cat Microsoft Windows Hardware Compatibility Publisher
acpi.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
afd.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
agilevpn.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
asyncmac.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
atapi.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
ataport.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
blbdrive.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
cng.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
compositebus.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-SeMicrosoft Windows
discache.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
disk.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
drmk.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-SeMicrosoft Windows
fdc.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
flpydisk.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
hdaudbus.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-SeMicrosoft Windows
hdaudio.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-SeMicrosoft Windows
http.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
hwpolicy.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
i8042prt.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
intelppm.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
kbdclass.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
ksecdd.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
ksecpkg.sys 12/11/2009 2:5.1,2:5.2,2:6.0,2:Signed Package_2_for_KB9804Microsoft Windows
lltdio.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
monitor.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-SeMicrosoft Windows
mouclass.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
mountmgr.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
mpsdrv.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
msahci.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
msisadrv.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
mskssrv.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
mssmbios.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
mstee.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
ndis.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
ndistapi.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
ndiswan.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
netbt.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
nfssvr.sys 7/13/2009 2:5.1,2:5.2,2:6.0,2:Signed Microsoft-Windows-NFMicrosoft Windows
nsiproxy.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
pacer.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
parport.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
passthruparser.sys 7/13/2009 2:5.1 Signed Package_4_for_KB2345Microsoft Windows
pci.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
pciide.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
pciidex.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
pcw.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
peauth.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
portcls.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-SeMicrosoft Windows
portmap.sys 7/13/2009 2:5.1,2:5.2,2:6.0,2:Signed Microsoft-Windows-NFMicrosoft Windows
rasl2tp.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
raspppoe.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
raspptp.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
rassstp.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
rdpbus.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-SeMicrosoft Windows
rdpcdd.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
rdpdr.sys 7/13/2009 2:5.1,2:5.2,2:6.0,2:Signed Microsoft-Windows-SeMicrosoft Windows
rdpencdd.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
rdprefmp.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
rpcxdr.sys 7/13/2009 2:5.1,2:5.2,2:6.0,2:Signed Microsoft-Windows-NFMicrosoft Windows
rspndr.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
rt64win7.sys 6/10/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
serenum.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
serial.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
sermouse.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
storvsp.sys 11/9/2010 2:5.1 Signed Package_4_for_KB2345Microsoft Windows
swenum.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
tcpip.sys 6/14/2010 2:5.1,2:5.2,2:6.0,2:Signed Package_2_for_KB9788Microsoft Windows
tcpipreg.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
tdtcp.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
tdx.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
termdd.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
tssecsrv.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
tunnel.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
umbus.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
usbd.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
usbehci.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
usbhub.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
usbport.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
usbuhci.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
vdrvroot.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
vga.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
vgapnp.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-SeMicrosoft Windows
vhdmp.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
vhdparser.sys 7/13/2009 2:5.1 Signed Package_4_for_KB2345Microsoft Windows
vid.sys 12/2/2009 2:5.1 Signed Package_1_for_KB9778Microsoft Windows
vmbus.sys 11/10/2010 2:5.1 Signed Package_2_for_KB2345Microsoft Windows
vmstorfl.sys 7/13/2009 2:5.1,2:5.2,2:6.0,2:Signed Microsoft-Hyper-V-GuMicrosoft Windows
vmswitch.sys 11/9/2010 2:5.1,2:5.2,2:6.0,2:Signed Package_6_for_KB2345Microsoft Windows
volmgr.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
volmgrx.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
volsnap.sys 7/13/2009 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows
wanarp.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
wdf01000.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
wfplwf.sys 7/13/2009 2:6.1 Signed nt5.cat Microsoft Windows
winhv.sys 7/13/2009 2:5.1 Signed Package_2_for_KB2345Microsoft Windows
skong
.png)
