Unsolved
This post is more than 5 years old
1 Rookie
•
29 Posts
0
165208
September 29th, 2013 04:00
BSOD, Driver Wdf01000.sys
Hello,
My vostro 2521 with win 7 pro recently has some Blue Screen of Death.
I just use whocrashed to get the Crash Dump Analysis:
Crash dumps are enabled on your computer.
On Sat 28/09/2013 18:49:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092913-19406-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x1C028)
Bugcheck code: 0x1000007E (0xFFFFFFFF80000003, 0xFFFFF80002E77990, 0xFFFFF8800A6813F8, 0xFFFFF8800A680C50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
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 that cannot be identified at this time.
On Sat 28/09/2013 18:49:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x1C028)
Bugcheck code: 0x7E (0xFFFFFFFF80000003, 0xFFFFF80002E77990, 0xFFFFF8800A6813F8, 0xFFFFF8800A680C50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 that cannot be identified at this time.
Thanks for helping me to resolve that!
DELL-Shrikanth G
2 Intern
•
618 Posts
0
September 29th, 2013 05:00
Hi bnour,
These BSOD errors are due to corrupt drivers installed on your computer. I would request you to uninstall the drivers and install it in the right order. Please follow this order while installing.
Link: http://dell.to/XMJsNP
Video: http://dell.to/1bc4L1J (Note: Please install the dell system software before installing the other softwares)
To install drivers please go to this link, enter your system service tag and download the necessary drivers.
http://dell.to/19zbTzI
bnour
1 Rookie
•
29 Posts
0
September 30th, 2013 08:00
Hi,
Thank you for your help!
I downloaded all the necessary drivers, now I want to know how must I proceed to uninstall the drivers, I do it in "Programs and Features" or in "Device Manager", and in "Device Manager" how to know which drivers are concerned?
bnour
1 Rookie
•
29 Posts
0
September 30th, 2013 08:00
Hi,
Thank you for your help!
I downloaded all the necessary drivers, now I want to know how must I proceed to uninstall the drivers, I do it in "Programs and Features" or in "Device Manager", and in "Device Manager" how to know which drivers are concerned?
bnour
1 Rookie
•
29 Posts
0
September 30th, 2013 08:00
Hi,
Thank you for your help!
I downloaded all the necessary drivers, now I want to know how must I proceed to uninstall the drivers, I do it in "Programs and Features" or in "Device Manager", and how to know which drivers are concerned?
DELL-Shrikanth G
2 Intern
•
618 Posts
0
September 30th, 2013 09:00
Hi bnour,
I would suggest you to reinstall the operating system just to make sure there are no conflicts. Once you reinstall the operating system then install the drivers in the right order.
(Note: Please back up your data (pictures, videos, files etc.) before reinstalling the operating system)
Follow this link to reinstall the operating system.
http://dell.to/Wj9o0m
bnour
1 Rookie
•
29 Posts
0
September 30th, 2013 10:00
ok thank you!
bnour
1 Rookie
•
29 Posts
0
October 12th, 2013 04:00
Hello,
Ive reinstalled my system,but I cant find the dell system software
compatible with my laptop vostro 2521, dell system detect is the new dss?
and i must install the dss before drivers,or just before the software.
Thank u!
bnour
1 Rookie
•
29 Posts
0
October 12th, 2013 04:00
Hello,
Ive reinstalled my system,but I cant find the dell system software
compatible with my laptop.
And i must install the dss before drivers,or just before the software.
Thank u!
DELL-Shrikanth G
2 Intern
•
618 Posts
0
October 13th, 2013 04:00
Hi bnour,
Thank you for the update. There is no DSS for your system. You can verify by using this link. You can also go ahead and install MY DELL which is a new version of Dell Support Center.
DSS link ( you would find all the drivers here)
http://dell.to/1fu83hS
My Dell
http://dell.to/GV0ouV
bnour
1 Rookie
•
29 Posts
0
October 15th, 2013 08:00
Hi Shrikanth,
I reinstalled the operating system then install the drivers in the right order, but still have a bsod problem.
The bsod occurs when I try to put my pc in sleep mode, and I noticed that this problem can have relation with my cellphone HTC one s, because when I try to put it in sleep mode with the cellphone branched I had this problem, but when I try without the cellphone branched there is no bsod, but maybe it's not exactly the cell cause also sometimes the sleep mode is successful with the cell branched.
Just below the dump file contains, I used windbg to get that:
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\101513-44335-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02e1a000 PsLoadedModuleList = 0xfffff800`0305d6d0
Debug session time: Tue Oct 15 04:05:14.276 2013 (UTC + 8:00)
System Uptime: 0 days 7:25:33.619
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
.............
************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*** WARNING: Unable to verify timestamp for Wdf01000.sys
*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffff80000003, fffff80002e879d0, fffff880009e33f8, fffff880009e2c50}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : Wdf01000.sys ( Wdf01000+18790 )
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\101513-28610-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02e00000 PsLoadedModuleList = 0xfffff800`030436d0
Debug session time: Tue Oct 15 06:21:44.497 2013 (UTC + 8:00)
System Uptime: 0 days 2:14:26.839
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.............................................................
Loading User Symbols
Loading unloaded module list
........
************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*** WARNING: Unable to verify timestamp for Wdf01000.sys
*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffff80000003, fffff80002e6d9d0, fffff88002db83f8, fffff88002db7c50}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : Wdf01000.sys ( Wdf01000+18790 )
Followup: MachineOwner
---------
2: kd> g
^ No runnable debuggees error in 'g'
bnour
1 Rookie
•
29 Posts
0
October 15th, 2013 08:00
After reinstalled all, I also get a bsod when trying "to use my PC's speaker to listen stereo audio playing on remote device" it is Bluetooth option for my HTC. Just below the dump file:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1036
Additional information about the problem:
BCCode: 50
BCP1: FFFFF880047B9D24
BCP2: 0000000000000000
BCP3: FFFFF880047800B3
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\101313-49452-01.dmp
C:\Users\Nour\AppData\Local\Temp\WER-95238-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\101313-49452-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`02e5d000 PsLoadedModuleList = 0xfffff800`030a0670
Debug session time: Sun Oct 13 19:15:13.296 2013 (UTC + 8:00)
System Uptime: 0 days 3:14:59.639
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
....................................
************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff880047b9d24, 0, fffff880047800b3, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\btath_rcp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for btath_rcp.sys
*** ERROR: Module load completed but symbols could not be loaded for btath_rcp.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : btath_rcp.sys ( btath_rcp+c0b3 )
Followup: MachineOwner
---------
----------------------
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\101313-49452-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`02e5d000 PsLoadedModuleList = 0xfffff800`030a0670
Debug session time: Sun Oct 13 19:15:13.296 2013 (UTC + 8:00)
System Uptime: 0 days 3:14:59.639
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
....................................
************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff880047b9d24, 0, fffff880047800b3, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\btath_rcp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for btath_rcp.sys
*** ERROR: Module load completed but symbols could not be loaded for btath_rcp.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : btath_rcp.sys ( btath_rcp+c0b3 )
Followup: MachineOwner
---------
2: kd> analyze -v
Couldn't resolve error at 'nalyze -v'
2: kd> lm tn
start end module name
fffff800`00bbc000 fffff800`00bc6000 kdcom kdcom.dll Sun Feb 06 00:52:49 2011 (4D4D8061)
fffff800`02e14000 fffff800`02e5d000 hal hal.dll Sat Nov 20 21:00:25 2010 (4CE7C669)
fffff800`02e5d000 fffff800`03443000 nt ntoskrnl.exe Tue Mar 19 11:21:42 2013 (5147D9C6)
fffff880`00c00000 fffff880`00cc0000 CI CI.dll Sat Nov 20 21:12:36 2010 (4CE7C944)
fffff880`00cc0000 fffff880`00cd4000 winhv winhv.sys Sat Nov 20 17:20:02 2010 (4CE792C2)
fffff880`00cd4000 fffff880`00cdd000 atapi atapi.sys Tue Jul 14 07:19:47 2009 (4A5BC113)
fffff880`00cdd000 fffff880`00ced000 PCIIDEX PCIIDEX.SYS Tue Jul 14 07:19:48 2009 (4A5BC114)
fffff880`00cfb000 fffff880`00d4a000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Nov 20 21:03:51 2010 (4CE7C737)
fffff880`00d4a000 fffff880`00d5e000 PSHED PSHED.dll Tue Jul 14 09:32:23 2009 (4A5BE027)
fffff880`00d5e000 fffff880`00dbc000 CLFS CLFS.SYS Tue Jul 14 07:19:57 2009 (4A5BC11D)
fffff880`00dbc000 fffff880`00de6000 ataport ataport.SYS Sat Nov 20 17:19:15 2010 (4CE79293)
fffff880`00de6000 fffff880`00df1000 msahci msahci.sys Sat Nov 20 18:33:58 2010 (4CE7A416)
fffff880`00e00000 fffff880`00e5c000 volmgrx volmgrx.sys Sat Nov 20 17:20:43 2010 (4CE792EB)
fffff880`00e5c000 fffff880`00e76000 mountmgr mountmgr.sys Sat Nov 20 17:19:21 2010 (4CE79299)
fffff880`00e76000 fffff880`00eb2000 vmbus vmbus.sys Sat Nov 20 17:57:29 2010 (4CE79B89)
fffff880`00eb5000 fffff880`00f77000 Wdf01000 Wdf01000.sys Thu Jul 26 10:25:13 2012 (5010AA89)
fffff880`00f77000 fffff880`00f87000 WDFLDR WDFLDR.SYS Thu Jul 26 10:29:04 2012 (5010AB70)
fffff880`00f87000 fffff880`00fba000 pci pci.sys Sat Nov 20 17:19:11 2010 (4CE7928F)
fffff880`00fba000 fffff880`00fcf000 partmgr partmgr.sys Sat Mar 17 13:06:09 2012 (4F641BC1)
fffff880`00fcf000 fffff880`00fd8000 compbatt compbatt.sys Tue Jul 14 07:31:02 2009 (4A5BC3B6)
fffff880`00fd8000 fffff880`00fe4000 BATTC BATTC.SYS Tue Jul 14 07:31:01 2009 (4A5BC3B5)
fffff880`00fe4000 fffff880`00ff9000 volmgr volmgr.sys Sat Nov 20 17:19:28 2010 (4CE792A0)
fffff880`01000000 fffff880`0100a000 msisadrv msisadrv.sys Tue Jul 14 07:19:26 2009 (4A5BC0FE)
fffff880`0100a000 fffff880`01017000 vdrvroot vdrvroot.sys Tue Jul 14 08:01:31 2009 (4A5BCADB)
fffff880`01017000 fffff880`01021000 iusb3hcs iusb3hcs.sys Fri Feb 22 20:36:29 2013 (5127664D)
fffff880`01025000 fffff880`01199000 sptd sptd.sys Sun Aug 19 05:05:38 2012 (503003A2)
fffff880`01199000 fffff880`011f0000 ACPI ACPI.sys Sat Nov 20 17:19:16 2010 (4CE79294)
fffff880`011f0000 fffff880`011f9000 WMILIB WMILIB.SYS Tue Jul 14 07:19:51 2009 (4A5BC117)
fffff880`01200000 fffff880`0124c000 fltmgr fltmgr.sys Sat Nov 20 17:19:24 2010 (4CE7929C)
fffff880`0124c000 fffff880`01260000 fileinfo fileinfo.sys Tue Jul 14 07:34:25 2009 (4A5BC481)
fffff880`01260000 fffff880`01290000 CLASSPNP CLASSPNP.SYS Sat Nov 20 17:19:23 2010 (4CE7929B)
fffff880`01296000 fffff880`01561000 iaStorA iaStorA.sys Tue Nov 20 04:09:40 2012 (50AA9204)
fffff880`01561000 fffff880`015c4000 storport storport.sys Fri Mar 11 12:30:23 2011 (4D79A55F)
fffff880`015c4000 fffff880`015cf000 amdxata amdxata.sys Sat Mar 20 00:18:18 2010 (4BA3A3CA)
fffff880`015cf000 fffff880`015e8000 HIDCLASS HIDCLASS.SYS Sat Nov 20 18:43:49 2010 (4CE7A665)
fffff880`015e8000 fffff880`01600000 rspndr rspndr.sys Tue Jul 14 08:08:50 2009 (4A5BCC92)
fffff880`01600000 fffff880`0164c000 volsnap volsnap.sys Sat Nov 20 17:20:08 2010 (4CE792C8)
fffff880`0164c000 fffff880`01686000 fvevol fvevol.sys Thu Jan 24 11:11:24 2013 (5100A65C)
fffff880`01686000 fffff880`01692000 amdkmpfd amdkmpfd.sys Tue Mar 20 19:18:58 2012 (4F6867A2)
fffff880`01692000 fffff880`016a5000 ndisuio ndisuio.sys Sat Nov 20 18:50:08 2010 (4CE7A7E0)
fffff880`016a7000 fffff880`016e4000 MpFilter MpFilter.sys Sat Jun 08 07:01:11 2013 (51B26637)
fffff880`016e4000 fffff880`01742000 msrpc msrpc.sys Sat Nov 20 17:21:56 2010 (4CE79334)
fffff880`01742000 fffff880`017b4000 cng cng.sys Sat Jun 02 11:25:51 2012 (4FC987BF)
fffff880`017b4000 fffff880`017fd000 fwpkclnt fwpkclnt.sys Thu Jan 03 11:06:48 2013 (50E4F5C8)
fffff880`01800000 fffff880`01816000 disk disk.sys Tue Jul 14 07:19:57 2009 (4A5BC11D)
fffff880`0181e000 fffff880`019c0000 Ntfs Ntfs.sys Fri Apr 12 19:54:36 2013 (5167F5FC)
fffff880`019c0000 fffff880`019db000 ksecdd ksecdd.sys Sat Jun 02 10:50:23 2012 (4FC97F6F)
fffff880`019db000 fffff880`019ec000 pcw pcw.sys Tue Jul 14 07:19:27 2009 (4A5BC0FF)
fffff880`019ec000 fffff880`019f6000 Fs_Rec Fs_Rec.sys Thu Mar 01 11:41:06 2012 (4F4EEFD2)
fffff880`01a00000 fffff880`01a60000 NETIO NETIO.SYS Wed Aug 22 23:11:28 2012 (5034F6A0)
fffff880`01a60000 fffff880`01a8a000 ksecpkg ksecpkg.sys Sat Jun 02 11:27:11 2012 (4FC9880F)
fffff880`01a8a000 fffff880`01a9a000 vmstorfl vmstorfl.sys Sat Nov 20 17:57:30 2010 (4CE79B8A)
fffff880`01a9a000 fffff880`01aa2000 spldr spldr.sys Tue May 12 00:56:27 2009 (4A0858BB)
fffff880`01aa2000 fffff880`01ab4000 mup mup.sys Tue Jul 14 07:23:45 2009 (4A5BC201)
fffff880`01ab4000 fffff880`01abf000 iaStorF iaStorF.sys Tue Nov 20 04:09:43 2012 (50AA9207)
fffff880`01abf000 fffff880`01ac8000 hwpolicy hwpolicy.sys Sat Nov 20 17:18:54 2010 (4CE7927E)
fffff880`01acc000 fffff880`01bbf000 ndis ndis.sys Sat Nov 20 17:23:30 2010 (4CE79392)
fffff880`01bbf000 fffff880`01bf9000 rdyboost rdyboost.sys Sat Nov 20 17:43:10 2010 (4CE7982E)
fffff880`01c00000 fffff880`01e00000 tcpip tcpip.sys Thu Jan 03 11:11:48 2013 (50E4F6F4)
fffff880`02800000 fffff880`02819000 WudfPf WudfPf.sys Thu Jul 26 10:26:45 2012 (5010AAE5)
fffff880`02819000 fffff880`0282e000 lltdio lltdio.sys Tue Jul 14 08:08:50 2009 (4A5BCC92)
fffff880`0282e000 fffff880`02881000 nwifi nwifi.sys Tue Jul 14 08:07:23 2009 (4A5BCC3B)
fffff880`02881000 fffff880`02888000 TurboB TurboB.sys Thu May 31 04:10:44 2012 (4FC67EC4)
fffff880`0288b000 fffff880`028b5000 btath_avdt btath_avdt.sys Mon May 21 14:53:16 2012 (4FB9E65C)
fffff880`028b5000 fffff880`0291e000 btath_a2dp btath_a2dp.sys Mon May 21 14:53:06 2012 (4FB9E652)
fffff880`0291e000 fffff880`02978000 btath_hcrp btath_hcrp.sys Wed Jul 20 10:59:43 2011 (4E26449F)
fffff880`02978000 fffff880`02987000 btath_flt btath_flt.sys Tue Mar 06 13:01:05 2012 (4F559A11)
fffff880`02987000 fffff880`0299d000 btath_lwflt btath_lwflt.sys Wed Jun 20 11:13:55 2012 (4FE13FF3)
fffff880`0299d000 fffff880`029ca280 usbvideo usbvideo.sys Sat Nov 20 18:44:34 2010 (4CE7A692)
fffff880`029cb000 fffff880`029ee000 luafv luafv.sys Tue Jul 14 07:26:13 2009 (4A5BC295)
fffff880`03000000 fffff880`03014000 termdd termdd.sys Sat Nov 20 19:03:40 2010 (4CE7AB0C)
fffff880`03014000 fffff880`03065000 rdbss rdbss.sys Sat Nov 20 17:27:51 2010 (4CE79497)
fffff880`03065000 fffff880`03071000 nsiproxy nsiproxy.sys Tue Jul 14 07:21:02 2009 (4A5BC15E)
fffff880`03071000 fffff880`0307c000 mssmbios mssmbios.sys Tue Jul 14 07:31:10 2009 (4A5BC3BE)
fffff880`0307c000 fffff880`0308b000 discache discache.sys Tue Jul 14 07:37:18 2009 (4A5BC52E)
fffff880`0308b000 fffff880`030a8000 usbccgp usbccgp.sys Fri Mar 25 11:29:14 2011 (4D8C0C0A)
fffff880`030b7000 fffff880`03140000 afd afd.sys Wed Dec 28 11:59:20 2011 (4EFA9418)
fffff880`03140000 fffff880`03185000 netbt netbt.sys Sat Nov 20 17:23:18 2010 (4CE79386)
fffff880`03185000 fffff880`0318e000 wfplwf wfplwf.sys Tue Jul 14 08:09:26 2009 (4A5BCCB6)
fffff880`0318e000 fffff880`031b4000 pacer pacer.sys Sat Nov 20 18:52:18 2010 (4CE7A862)
fffff880`031b4000 fffff880`031ca000 vwififlt vwififlt.sys Tue Jul 14 08:07:22 2009 (4A5BCC3A)
fffff880`031ca000 fffff880`031d9000 netbios netbios.sys Tue Jul 14 08:09:26 2009 (4A5BCCB6)
fffff880`031d9000 fffff880`031f4000 wanarp wanarp.sys Sat Nov 20 18:52:36 2010 (4CE7A874)
fffff880`04400000 fffff880`0440e000 vga vga.sys Tue Jul 14 07:38:47 2009 (4A5BC587)
fffff880`0440e000 fffff880`04433000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 07:38:51 2009 (4A5BC58B)
fffff880`04433000 fffff880`04443000 watchdog watchdog.sys Tue Jul 14 07:37:35 2009 (4A5BC53F)
fffff880`04443000 fffff880`0444c000 RDPCDD RDPCDD.sys Tue Jul 14 08:16:34 2009 (4A5BCE62)
fffff880`0444c000 fffff880`04455000 rdpencdd rdpencdd.sys Tue Jul 14 08:16:34 2009 (4A5BCE62)
fffff880`04455000 fffff880`0445e000 rdprefmp rdprefmp.sys Tue Jul 14 08:16:35 2009 (4A5BCE63)
fffff880`0445e000 fffff880`04469000 Msfs Msfs.SYS Tue Jul 14 07:19:47 2009 (4A5BC113)
fffff880`04469000 fffff880`0447a000 Npfs Npfs.SYS Tue Jul 14 07:19:48 2009 (4A5BC114)
fffff880`0447a000 fffff880`0449c000 tdx tdx.sys Sat Nov 20 17:21:54 2010 (4CE79332)
fffff880`0449c000 fffff880`044a9000 TDI TDI.SYS Sat Nov 20 17:22:06 2010 (4CE7933E)
fffff880`044a9000 fffff880`04774000 dump_iaStorA dump_iaStorA.sys Tue Nov 20 04:09:40 2012 (50AA9204)
fffff880`04774000 fffff880`047b7e00 btath_rcp btath_rcp.sys Mon Aug 27 13:51:46 2012 (503B0AF2)
fffff880`047ba000 fffff880`047e4000 cdrom cdrom.sys Sat Nov 20 17:19:20 2010 (4CE79298)
fffff880`047e4000 fffff880`047ed000 Null Null.SYS Tue Jul 14 07:19:37 2009 (4A5BC109)
fffff880`047ed000 fffff880`047f4000 Beep Beep.SYS Tue Jul 14 08:00:13 2009 (4A5BCA8D)
fffff880`04e00000 fffff880`04e61000 atikmpag atikmpag.sys Thu Aug 02 12:09:28 2012 (5019FD78)
fffff880`04e61000 fffff880`04e7c000 raspppoe raspppoe.sys Tue Jul 14 08:10:17 2009 (4A5BCCE9)
fffff880`04e7c000 fffff880`04e9d000 raspptp raspptp.sys Sat Nov 20 18:52:31 2010 (4CE7A86F)
fffff880`04e9d000 fffff880`04eb7000 rassstp rassstp.sys Tue Jul 14 08:10:25 2009 (4A5BCCF1)
fffff880`04eb7000 fffff880`04ec9000 umbus umbus.sys Sat Nov 20 18:44:37 2010 (4CE7A695)
fffff880`04ed0000 fffff880`04f53000 csc csc.sys Sat Nov 20 17:27:12 2010 (4CE79470)
fffff880`04f53000 fffff880`04f71000 dfsc dfsc.sys Sat Nov 20 17:26:31 2010 (4CE79447)
fffff880`04f71000 fffff880`04f82000 blbdrive blbdrive.sys Tue Jul 14 07:35:59 2009 (4A5BC4DF)
fffff880`04f82000 fffff880`04fa8000 tunnel tunnel.sys Sat Nov 20 18:51:50 2010 (4CE7A846)
fffff880`04fa8000 fffff880`04feb000 ks ks.sys Sat Nov 20 18:33:23 2010 (4CE7A3F3)
fffff880`04feb000 fffff880`04ff8000 btath_bus btath_bus.sys Mon May 21 14:52:53 2012 (4FB9E645)
fffff880`05000000 fffff880`05077000 SynTP SynTP.sys Fri Dec 21 13:59:33 2012 (50D3FAC5)
fffff880`05077000 fffff880`05086000 mouclass mouclass.sys Tue Jul 14 07:19:50 2009 (4A5BC116)
fffff880`05086000 fffff880`05093000 Smb_driver_Intel Smb_driver_Intel.sys Fri Dec 21 14:01:11 2012 (50D3FB27)
fffff880`05093000 fffff880`050df000 arz7oro8 arz7oro8.SYS Wed Dec 28 17:10:52 2011 (4EFADD1C)
fffff880`050df000 fffff880`050f5000 intelppm intelppm.sys Tue Jul 14 07:19:25 2009 (4A5BC0FD)
fffff880`050f5000 fffff880`051a8000 Rt64win7 Rt64win7.sys Tue Jun 12 22:00:29 2012 (4FD74B7D)
fffff880`051a8000 fffff880`051c6000 i8042prt i8042prt.sys Tue Jul 14 07:19:57 2009 (4A5BC11D)
fffff880`051c6000 fffff880`051f5000 SCSIPORT SCSIPORT.SYS Sat Nov 20 18:34:01 2010 (4CE7A419)
fffff880`051f5000 fffff880`051fe000 wmiacpi wmiacpi.sys Tue Jul 14 07:31:02 2009 (4A5BC3B6)
fffff880`05200000 fffff880`05204500 CmBatt CmBatt.sys Tue Jul 14 07:31:03 2009 (4A5BC3B7)
fffff880`05205000 fffff880`0520bc00 GEARAspiWDM GEARAspiWDM.sys Fri May 04 03:56:17 2012 (4FA2E2E1)
fffff880`0520d000 fffff880`055e2000 athrx athrx.sys Wed Jan 23 11:19:07 2013 (50FF56AB)
fffff880`055e2000 fffff880`055ef000 vwifibus vwifibus.sys Tue Jul 14 08:07:21 2009 (4A5BCC39)
fffff880`055ef000 fffff880`055fe000 kbdclass kbdclass.sys Tue Jul 14 07:19:50 2009 (4A5BC116)
fffff880`055fe000 fffff880`055ff480 swenum swenum.sys Tue Jul 14 08:00:18 2009 (4A5BCA92)
fffff880`05600000 fffff880`0562c000 rfcomm rfcomm.sys Tue Jul 14 08:06:56 2009 (4A5BCC20)
fffff880`0562c000 fffff880`0564c000 bthpan bthpan.sys Tue Jul 14 08:07:00 2009 (4A5BCC24)
fffff880`05650000 fffff880`056aa000 usbhub usbhub.sys Fri Mar 25 11:29:25 2011 (4D8C0C15)
fffff880`056aa000 fffff880`056bf000 NDProxy NDProxy.SYS Sat Nov 20 18:52:20 2010 (4CE7A864)
fffff880`056bf000 fffff880`0571c000 iusb3hub iusb3hub.sys Fri Feb 22 20:33:42 2013 (512765A6)
fffff880`0571c000 fffff880`057a8000 bthport bthport.sys Sat Jul 07 04:07:41 2012 (4FF7458D)
fffff880`057a8000 fffff880`057fb000 RtsUVStor RtsUVStor.sys Thu Aug 08 16:26:23 2013 (5203562F)
fffff880`05a00000 fffff880`05a16000 AgileVpn AgileVpn.sys Tue Jul 14 08:10:24 2009 (4A5BCCF0)
fffff880`05a16000 fffff880`05a3a000 rasl2tp rasl2tp.sys Sat Nov 20 18:52:34 2010 (4CE7A872)
fffff880`05a3a000 fffff880`05a46000 ndistapi ndistapi.sys Tue Jul 14 08:10:00 2009 (4A5BCCD8)
fffff880`05a46000 fffff880`05a75000 ndiswan ndiswan.sys Sat Nov 20 18:52:32 2010 (4CE7A870)
fffff880`05a81000 fffff880`064a3000 atikmdag atikmdag.sys Thu Aug 02 11:34:54 2012 (5019F55E)
fffff880`064a3000 fffff880`06597000 dxgkrnl dxgkrnl.sys Sat Nov 20 17:50:50 2010 (4CE799FA)
fffff880`06597000 fffff880`065ed000 USBPORT USBPORT.SYS Fri Mar 25 11:29:12 2011 (4D8C0C08)
fffff880`065ed000 fffff880`065fd000 CompositeBus CompositeBus.sys Sat Nov 20 18:33:17 2010 (4CE7A3ED)
fffff880`06800000 fffff880`068c5000 iusb3xhc iusb3xhc.sys Fri Feb 22 20:33:45 2013 (512765A9)
fffff880`068c5000 fffff880`068c6f00 USBD USBD.SYS Fri Mar 25 11:28:59 2011 (4D8C0BFB)
fffff880`068c7000 fffff880`068d2000 rdpbus rdpbus.sys Tue Jul 14 08:17:46 2009 (4A5BCEAA)
fffff880`068d2000 fffff880`07167540 igdpmd64 igdpmd64.sys Wed Aug 22 01:08:36 2012 (5033C094)
fffff880`07168000 fffff880`071ae000 dxgmms1 dxgmms1.sys Sat Nov 20 17:49:53 2010 (4CE799C1)
fffff880`071ae000 fffff880`071c1000 HECIx64 HECIx64.sys Tue Jul 03 06:14:58 2012 (4FF21D62)
fffff880`071c1000 fffff880`071d2000 usbehci usbehci.sys Fri Mar 25 11:29:04 2011 (4D8C0C00)
fffff880`071d2000 fffff880`071f6000 HDAudBus HDAudBus.sys Sat Nov 20 18:43:42 2010 (4CE7A65E)
fffff880`0840e000 fffff880`08813200 RTKVHD64 RTKVHD64.sys Tue Nov 27 21:48:01 2012 (50B4C491)
fffff880`08814000 fffff880`08851000 portcls portcls.sys Tue Jul 14 08:06:27 2009 (4A5BCC03)
fffff880`08851000 fffff880`08873000 drmk drmk.sys Tue Jul 14 09:01:25 2009 (4A5BD8E5)
fffff880`08873000 fffff880`08878200 ksthunk ksthunk.sys Tue Jul 14 08:00:19 2009 (4A5BCA93)
fffff880`08879000 fffff880`088d1000 IntcDAud IntcDAud.sys Tue Jun 19 22:40:51 2012 (4FE08F73)
fffff880`088d1000 fffff880`088df000 crashdmp crashdmp.sys Tue Jul 14 08:01:01 2009 (4A5BCABD)
fffff880`088df000 fffff880`088e9000 dump_diskdump dump_diskdump.sys Sat Apr 23 04:04:32 2011 (4DB1DF50)
fffff880`088e9000 fffff880`088fc000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 07:21:51 2009 (4A5BC18F)
fffff880`088fc000 fffff880`08908000 Dxapi Dxapi.sys Tue Jul 14 07:38:28 2009 (4A5BC574)
fffff880`08908000 fffff880`089a1000 btfilter btfilter.sys Tue Nov 27 10:03:02 2012 (50B41F56)
fffff880`089a1000 fffff880`089b9000 BTHUSB BTHUSB.sys Thu Apr 28 11:54:56 2011 (4DB8E510)
fffff880`089b9000 fffff880`089d4000 USBSTOR USBSTOR.SYS Fri Mar 11 12:37:16 2011 (4D79A6FC)
fffff880`089d4000 fffff880`089e2000 monitor monitor.sys Tue Jul 14 07:38:52 2009 (4A5BC58C)
fffff880`089e2000 fffff880`089f2000 BthEnum BthEnum.sys Tue Jul 14 08:06:52 2009 (4A5BCC1C)
fffff880`089f2000 fffff880`089fa080 HIDPARSE HIDPARSE.SYS Tue Jul 14 08:06:17 2009 (4A5BCBF9)
fffff880`08e00000 fffff880`08e24000 mrxsmb20 mrxsmb20.sys Wed Apr 27 10:39:37 2011 (4DB781E9)
fffff880`08e24000 fffff880`08e4e000 idmwfp idmwfp.sys Wed Aug 01 22:23:05 2012 (50193BC9)
fffff880`08e4e000 fffff880`08e5a000 npf npf.sys Sat Jun 26 00:50:58 2010 (4C24DE72)
fffff880`08e82000 fffff880`08f4b000 HTTP HTTP.sys Sat Nov 20 17:24:30 2010 (4CE793CE)
fffff880`08f4b000 fffff880`08f69000 bowser bowser.sys Wed Feb 23 12:55:04 2011 (4D649328)
fffff880`08f69000 fffff880`08f81000 mpsdrv mpsdrv.sys Tue Jul 14 08:08:25 2009 (4A5BCC79)
fffff880`08f81000 fffff880`08fae000 mrxsmb mrxsmb.sys Wed Apr 27 10:40:38 2011 (4DB78226)
fffff880`08fae000 fffff880`08ffc000 mrxsmb10 mrxsmb10.sys Sat Jul 09 10:46:28 2011 (4E17C104)
fffff880`0a800000 fffff880`0a869000 srv2 srv2.sys Fri Apr 29 11:05:46 2011 (4DBA2B0A)
fffff880`0a8c1000 fffff880`0a967000 peauth peauth.sys Tue Jul 14 09:01:19 2009 (4A5BD8DF)
fffff880`0a967000 fffff880`0a972000 secdrv secdrv.SYS Wed Sep 13 21:18:38 2006 (4508052E)
fffff880`0a972000 fffff880`0a9a3000 srvnet srvnet.sys Fri Apr 29 11:05:35 2011 (4DBA2AFF)
fffff880`0a9a3000 fffff880`0a9c0000 cdfs cdfs.sys Tue Jul 14 07:19:46 2009 (4A5BC112)
fffff880`0a9c0000 fffff880`0a9d2000 tcpipreg tcpipreg.sys Sat Nov 20 18:51:48 2010 (4CE7A844)
fffff880`0b000000 fffff880`0b00f000 modem modem.sys Tue Jul 14 08:10:48 2009 (4A5BCD08)
fffff880`0b00f000 fffff880`0b01e000 ANDROIDUSB ANDROIDUSB.sys Mon Oct 26 16:54:23 2009 (4AE563BF)
fffff880`0b020000 fffff880`0b0b8000 srv srv.sys Fri Apr 29 11:06:06 2011 (4DBA2B1E)
fffff880`0b0b8000 fffff880`0b0ee000 fastfat fastfat.SYS Tue Jul 14 07:23:28 2009 (4A5BC1F0)
fffff880`0b0ee000 fffff880`0b0f8000 vwifimp vwifimp.sys Tue Jul 14 08:07:28 2009 (4A5BCC40)
fffff880`0b15f000 fffff880`0b167000 TuneUpUtilitiesDriver64 TuneUpUtilitiesDriver64.sys Thu Sep 17 19:54:52 2009 (4AB2238C)
fffff880`0b1ac000 fffff880`0b1e2000 WUDFRd WUDFRd.sys Thu Jul 26 10:26:06 2012 (5010AABE)
fffff880`0b1e2000 fffff880`0b1f9000 bthmodem bthmodem.sys Tue Jul 14 08:06:52 2009 (4A5BCC1C)
fffff960`000a0000 fffff960`003b6000 win32k win32k.sys unavailable (00000000)
fffff960`005e0000 fffff960`005ea000 TSDDD TSDDD.dll unavailable (00000000)
fffff960`00670000 fffff960`00697000 cdd cdd.dll unavailable (00000000)
Unloaded modules:
fffff880`0b19d000 fffff880`0b1ac000 ANDROIDUSB.s
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000F000
fffff880`0b167000 fffff880`0b19d000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`0b124000 fffff880`0b133000 ANDROIDUSB.s
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000F000
fffff880`0b0ee000 fffff880`0b124000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`0b1e2000 fffff880`0b1f1000 ANDROIDUSB.s
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000F000
fffff880`0b1ac000 fffff880`0b1e2000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`0b176000 fffff880`0b1ac000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`0b167000 fffff880`0b176000 ANDROIDUSB.s
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000F000
fffff880`0b0ee000 fffff880`0b15f000 spsys.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00071000
fffff880`0b0ee000 fffff880`0b15f000 spsys.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00071000
fffff880`0b1b3000 fffff880`0b1e9000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`0b1a4000 fffff880`0b1b3000 ANDROIDUSB.s
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000F000
fffff880`0b15f000 fffff880`0b195000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`0b195000 fffff880`0b1a4000 ANDROIDUSB.s
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000F000
fffff880`0b195000 fffff880`0b1cb000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`0b15f000 fffff880`0b195000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`0b1b7000 fffff880`0b1ed000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`0b1a6000 fffff880`0b1b7000 WinUsb.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00011000
fffff880`0b170000 fffff880`0b1a6000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`0b15f000 fffff880`0b170000 WinUsb.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00011000
fffff880`0b1b2000 fffff880`0b1e8000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`0b17c000 fffff880`0b1b2000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`0b16b000 fffff880`0b17c000 WinUsb.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00011000
fffff880`0b135000 fffff880`0b16b000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`0b124000 fffff880`0b135000 WinUsb.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00011000
fffff880`0b0ee000 fffff880`0b124000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`0b1ed000 fffff880`0b1fe000 WinUsb.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00011000
fffff880`0b1b7000 fffff880`0b1ed000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`0b1a6000 fffff880`0b1b7000 WinUsb.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00011000
fffff880`0b170000 fffff880`0b1a6000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`0b15f000 fffff880`0b170000 WinUsb.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00011000
fffff880`0b0ee000 fffff880`0b15f000 spsys.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00071000
fffff880`01692000 fffff880`016a0000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000E000
fffff880`019f6000 fffff880`01a00000 dump_storpor
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000A000
fffff880`044dc000 fffff880`047a7000 dump_iaStorA
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 002CB000
fffff880`047a7000 fffff880`047ba000 dump_dumpfve
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00013000
DELL-Shrikanth G
2 Intern
•
618 Posts
0
October 16th, 2013 06:00
Hi bnour,
Thank you for the update and i appreciate your effort here. I would request you to run the hardware diagnostics along with the extended memory test to make sure hardware is fine. (Once you finish the diagnostics you will get a pop up to continue the test, select continue or yes). To run diagnostics
http://dell.to/GIszMn
Reply with your findings.