Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD error 0x0000001e


14 Jan 2012   #1

Windows 7 Professions 64-bit
 
 
BSOD error 0x0000001e

Hello,

I purchased a few new parts for my computer a while back as upgrades, I basically replaced everything but my HDD. I put everything together and did a clean install for windows 7 pro 64 bit. I am getting fairly random blue screens, sometimes they happen when surfing the internet, but they are guaranteed to happen shortly after starting a video game (I have tried WoW and LoL). I believe blue screen view says it is ntoskrnl.exe causing the crash. I have tried repairing Windows and updating all my drivers but I can't seem to fix it. I also removed my anti-virus software temporarily because it seemed to be causing an issue but no change. Any help you guys could give would be great, I have attached my DMP files, I hope they can help.

AMD phenom II black edition X4 975
Gigabyte 880GM-2DH
8GB DDR3 Patriot Memory (2x4GB)
80 GB Seagate HDD
NVidea GeForce GTS 250


My System SpecsSystem Spec
.

14 Jan 2012   #2

Windows 7 Home Premium 64 Bit
 
 

What antivirus did you have and how did you remove it? Did you use the tool provided by the developer? If not, find any tools from the developer for removal to make sure all remnants are removed.

Once your old antivirus is completely removed, we suggest for the time being that you replace your antivirus with Microsoft Security Essentials - Free Antivirus for Windows to run alongside Windows firewall.

I will now take a look at your .dmp files and post back in 10-20 minutes.
My System SpecsSystem Spec
14 Jan 2012   #3
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

*** I am currently on a lappy without WinDbg & thus unable to analyse your DMPS...***

In the interim please read this information...

Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED


* This indicates that a kernel-mode program generated an exception which the error handler did not catch.


* The following actions might prevent an error like this from happening again:


> Download and install updates and device drivers for your computer from Windows Update.

> Scan your computer for computer viruses.
> Check your hard disk for errors.
Disk Check



> For good measure download the free version of Malwarebytes.


Update it immediately.

Run a full system scan.

Tell us the results at the end please.


Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!


EDIT.
I note {above} my friend writhziden is currently analyzing your DMPS.
My System SpecsSystem Spec
.


14 Jan 2012   #4

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\dpcrowley\Windows_NT6_BSOD_jcgriff2\011212-26426-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02a1f000 PsLoadedModuleList = 0xfffff800`02c5ce70 Debug session time: Thu Jan 12 11:27:16.100 2012 (UTC - 7:00) System Uptime: 0 days 0:03:00.411 Loading Kernel Symbols .............................................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Unable to load image Unknown_Module_00000000`08587630, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`08587630 *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`08587630 Unknown module 'Unknown_Module_00000000_08587630' found on stack, using vad to reload module. !vad_reload -1 0x8587630 00000000`0a6f94c0: Unable to get VAD.PrivateMemory Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ Unknown module 'Unknown_Module_00000000_08587630' found on stack, using vad to reload module. !vad_reload -1 0x8587630 00000000`0a6f94c0: Unable to get VAD.PrivateMemory EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +3432373430323564 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff880035fd5a8 -- (.exr 0xfffff880035fd5a8) ExceptionAddress: fffff880060557cf ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff880035fd650 -- (.trap 0xfffff880035fd650) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=958f6d584ef0618e rbx=0000000000000000 rcx=fffffa8007d67ff0 rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880060557cf rsp=fffff880035fd7e0 rbp=0000000000000000 r8=fffffa8007d82e00 r9=0000000000000000 r10=fffffa8007d4ec80 r11=0000000000000002 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc fffff880`060557cf ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a872ee to fffff80002a8f590 STACK_TEXT: fffff880`035fc698 fffff800`02a872ee : 00000000`00000010 fffffa80`09e8fa18 fffff880`035fce10 fffff800`02abc524 : nt!KeBugCheck fffff880`035fc6a0 fffff800`02ab52dd : fffff800`02c9db7c fffff800`02bd7e68 fffff800`02a1f000 fffff880`035fd5a8 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`035fc6d0 fffff800`02abc950 : fffff800`02bdeb0c fffff880`035fc748 fffff880`035fd5a8 fffff800`02a1f000 : nt!RtlpExecuteHandlerForException+0xd fffff880`035fc700 fffff800`02ac98cf : fffff880`035fd5a8 fffff880`035fce10 fffff880`00000000 fffffa80`07d4ec80 : nt!RtlDispatchException+0x410 fffff880`035fcde0 fffff800`02a8ec02 : fffff880`035fd5a8 fffffa80`088aba60 fffff880`035fd650 fffffa80`07d40950 : nt!KiDispatchException+0x16f fffff880`035fd470 fffff800`02a8d50a : fffffa80`00000000 00000000`00000001 fffffa80`092e8010 fffff880`05609808 : nt!KiExceptionDispatch+0xc2 fffff880`035fd650 fffff880`060557cf : fffffa80`07d68000 fffff880`035fd890 fffffa80`07d4ec80 fffffa80`088aba60 : nt!KiGeneralProtectionFault+0x10a fffff880`035fd7e0 fffffa80`07d68000 : fffff880`035fd890 fffffa80`07d4ec80 fffffa80`088aba60 fffffa80`07d68000 : 0xfffff880`060557cf fffff880`035fd7e8 fffff880`035fd890 : fffffa80`07d4ec80 fffffa80`088aba60 fffffa80`07d68000 fffffa80`088dfa10 : 0xfffffa80`07d68000 fffff880`035fd7f0 fffffa80`07d4ec80 : fffffa80`088aba60 fffffa80`07d68000 fffffa80`088dfa10 00000000`08f16001 : 0xfffff880`035fd890 fffff880`035fd7f8 fffffa80`088aba60 : fffffa80`07d68000 fffffa80`088dfa10 00000000`08f16001 958f6d58`4ef0618e : 0xfffffa80`07d4ec80 fffff880`035fd800 fffffa80`07d68000 : fffffa80`088dfa10 00000000`08f16001 958f6d58`4ef0618e fffffa80`07d4ec80 : 0xfffffa80`088aba60 fffff880`035fd808 fffffa80`088dfa10 : 00000000`08f16001 958f6d58`4ef0618e fffffa80`07d4ec80 fffff880`06055a1a : 0xfffffa80`07d68000 fffff880`035fd810 00000000`08f16001 : 958f6d58`4ef0618e fffffa80`07d4ec80 fffff880`06055a1a fffffa80`07d54000 : 0xfffffa80`088dfa10 fffff880`035fd818 958f6d58`4ef0618e : fffffa80`07d4ec80 fffff880`06055a1a fffffa80`07d54000 fffffa80`088e0410 : Unknown_Module_00000000_08587630+0x98e9d1 fffff880`035fd820 fffffa80`07d4ec80 : fffff880`06055a1a fffffa80`07d54000 fffffa80`088e0410 00000000`00000000 : 0x958f6d58`4ef0618e fffff880`035fd828 fffff880`06055a1a : fffffa80`07d54000 fffffa80`088e0410 00000000`00000000 fffffa80`06e69ec0 : 0xfffffa80`07d4ec80 fffff880`035fd830 fffffa80`07d54000 : fffffa80`088e0410 00000000`00000000 fffffa80`06e69ec0 fffffa80`07d4ec80 : 0xfffff880`06055a1a fffff880`035fd838 fffffa80`088e0410 : 00000000`00000000 fffffa80`06e69ec0 fffffa80`07d4ec80 fffff880`0605596a : 0xfffffa80`07d54000 fffff880`035fd840 00000000`00000000 : fffffa80`06e69ec0 fffffa80`07d4ec80 fffff880`0605596a fffffa80`07d54000 : 0xfffffa80`088e0410 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiKernelCalloutExceptionHandler+e fffff800`02a872ee 90 nop SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44 FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e Followup: MachineOwner ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\dpcrowley\Windows_NT6_BSOD_jcgriff2\011212-32089-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02a57000 PsLoadedModuleList = 0xfffff800`02c94e70 Debug session time: Thu Jan 12 15:38:05.648 2012 (UTC - 7:00) System Uptime: 0 days 0:13:14.349 Loading Kernel Symbols ..............................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 Loading User Symbols Missing image name, possible paged-out or corrupt data. Loading unloaded module list .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. . ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: Unknown_Module_00000000`00000000>+0 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002ad50ca to fffff8800102d7f2 STACK_TEXT: fffff800`00b9cc98 fffff800`02ad50ca : 00000000`0035e222 fffffa80`08168608 fffff800`02c4fc40 00000000`00000001 : 0xfffff880`0102d7f2 fffff800`00b9cca0 fffff800`02acfd5c : fffff800`02c41e80 fffff800`00000000 00000000`00000000 fffff880`00e0bf44 : nt!PoIdle+0x53a fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c STACK_COMMAND: kb FOLLOWUP_IP: nt!PoIdle+53a fffff800`02ad50ca 0fba25761518000f bt dword ptr [<Unloaded_Unknown_Module_00000000`00000000>+0x181576 (00000000`00181576)],0Fh SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!PoIdle+53a FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44 FAILURE_BUCKET_ID: X64_0x1E_0_nt!PoIdle+53a BUCKET_ID: X64_0x1E_0_nt!PoIdle+53a Followup: MachineOwner ---------
  3. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\dpcrowley\Windows_NT6_BSOD_jcgriff2\011212-29640-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02a4f000 PsLoadedModuleList = 0xfffff800`02c8ce70 Debug session time: Thu Jan 12 15:57:51.528 2012 (UTC - 7:00) System Uptime: 0 days 0:01:19.230 Loading Kernel Symbols ............................................................... ................................................................ .................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Unable to load image \SystemRoot\system32\DRIVERS\WUSB54Gv4x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for WUSB54Gv4x64.sys *** ERROR: Module load completed but symbols could not be loaded for WUSB54Gv4x64.sys Probably caused by : WUSB54Gv4x64.sys ( WUSB54Gv4x64+2d7cf ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +3432373430323564 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff880035fd5a8 -- (.exr 0xfffff880035fd5a8) ExceptionAddress: fffff880060337cf (WUSB54Gv4x64+0x000000000002d7cf) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff880035fd650 -- (.trap 0xfffff880035fd650) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=958f6d581260618e rbx=0000000000000000 rcx=fffffa80089c3ff0 rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880060337cf rsp=fffff880035fd7e0 rbp=0000000000000000 r8=fffffa8007cdca00 r9=0000000000000000 r10=fffffa8007caaa70 r11=0000000000000002 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc WUSB54Gv4x64+0x2d7cf: fffff880`060337cf ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ab72ee to fffff80002abf590 STACK_TEXT: fffff880`035fc698 fffff800`02ab72ee : 00000000`00000010 fffffa80`0a3aec38 fffff880`035fce10 fffff800`02aec524 : nt!KeBugCheck fffff880`035fc6a0 fffff800`02ae52dd : fffff800`02ccdb7c fffff800`02c07e68 fffff800`02a4f000 fffff880`035fd5a8 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`035fc6d0 fffff800`02aec950 : fffff800`02c0eb0c fffff880`035fc748 fffff880`035fd5a8 fffff800`02a4f000 : nt!RtlpExecuteHandlerForException+0xd fffff880`035fc700 fffff800`02af98cf : fffff880`035fd5a8 fffff880`035fce10 fffff880`00000000 fffffa80`07caaa70 : nt!RtlDispatchException+0x410 fffff880`035fcde0 fffff800`02abec02 : fffff880`035fd5a8 fffffa80`08a0ee70 fffff880`035fd650 fffffa80`07cb0900 : nt!KiDispatchException+0x16f fffff880`035fd470 fffff800`02abd50a : fffffa80`00000000 00000000`00000001 fffffa80`093a8010 fffff880`05609808 : nt!KiExceptionDispatch+0xc2 fffff880`035fd650 fffff880`060337cf : fffffa80`089c4000 fffff880`035fd890 fffffa80`07caaa70 fffffa80`08a0ee70 : nt!KiGeneralProtectionFault+0x10a fffff880`035fd7e0 fffffa80`089c4000 : fffff880`035fd890 fffffa80`07caaa70 fffffa80`08a0ee70 fffffa80`089c4000 : WUSB54Gv4x64+0x2d7cf fffff880`035fd7e8 fffff880`035fd890 : fffffa80`07caaa70 fffffa80`08a0ee70 fffffa80`089c4000 fffffa80`07cb5e40 : 0xfffffa80`089c4000 fffff880`035fd7f0 fffffa80`07caaa70 : fffffa80`08a0ee70 fffffa80`089c4000 fffffa80`07cb5e40 00000000`00000001 : 0xfffff880`035fd890 fffff880`035fd7f8 fffffa80`08a0ee70 : fffffa80`089c4000 fffffa80`07cb5e40 00000000`00000001 958f6d58`1260618e : 0xfffffa80`07caaa70 fffff880`035fd800 fffffa80`089c4000 : fffffa80`07cb5e40 00000000`00000001 958f6d58`1260618e fffffa80`07caaa70 : 0xfffffa80`08a0ee70 fffff880`035fd808 fffffa80`07cb5e40 : 00000000`00000001 958f6d58`1260618e fffffa80`07caaa70 fffff880`06033a1a : 0xfffffa80`089c4000 fffff880`035fd810 00000000`00000001 : 958f6d58`1260618e fffffa80`07caaa70 fffff880`06033a1a fffffa80`089b0000 : 0xfffffa80`07cb5e40 fffff880`035fd818 958f6d58`1260618e : fffffa80`07caaa70 fffff880`06033a1a fffffa80`089b0000 fffffa80`07cb5bd0 : 0x1 fffff880`035fd820 fffffa80`07caaa70 : fffff880`06033a1a fffffa80`089b0000 fffffa80`07cb5bd0 fffffa80`0930cb40 : 0x958f6d58`1260618e fffff880`035fd828 fffff880`06033a1a : fffffa80`089b0000 fffffa80`07cb5bd0 fffffa80`0930cb40 00000000`0000000c : 0xfffffa80`07caaa70 fffff880`035fd830 fffffa80`089b0000 : fffffa80`07cb5bd0 fffffa80`0930cb40 00000000`0000000c fffffa80`07caaa70 : WUSB54Gv4x64+0x2da1a fffff880`035fd838 fffffa80`07cb5bd0 : fffffa80`0930cb40 00000000`0000000c fffffa80`07caaa70 fffff880`0603396a : 0xfffffa80`089b0000 fffff880`035fd840 fffffa80`0930cb40 : 00000000`0000000c fffffa80`07caaa70 fffff880`0603396a fffffa80`089b0000 : 0xfffffa80`07cb5bd0 fffff880`035fd848 00000000`0000000c : fffffa80`07caaa70 fffff880`0603396a fffffa80`089b0000 fffffa80`089f4980 : 0xfffffa80`0930cb40 fffff880`035fd850 fffffa80`07caaa70 : fffff880`0603396a fffffa80`089b0000 fffffa80`089f4980 00000000`00000000 : 0xc fffff880`035fd858 fffff880`0603396a : fffffa80`089b0000 fffffa80`089f4980 00000000`00000000 00000000`00000004 : 0xfffffa80`07caaa70 fffff880`035fd860 fffffa80`089b0000 : fffffa80`089f4980 00000000`00000000 00000000`00000004 fffffa80`07cdcb40 : WUSB54Gv4x64+0x2d96a fffff880`035fd868 fffffa80`089f4980 : 00000000`00000000 00000000`00000004 fffffa80`07cdcb40 fffffa80`089f4980 : 0xfffffa80`089b0000 fffff880`035fd870 00000000`00000000 : 00000000`00000004 fffffa80`07cdcb40 fffffa80`089f4980 00000000`00000018 : 0xfffffa80`089f4980 STACK_COMMAND: kb FOLLOWUP_IP: WUSB54Gv4x64+2d7cf fffff880`060337cf ?? ??? SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: WUSB54Gv4x64+2d7cf FOLLOWUP_NAME: MachineOwner MODULE_NAME: WUSB54Gv4x64 IMAGE_NAME: WUSB54Gv4x64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 45923fcb FAILURE_BUCKET_ID: X64_0x1E_0_WUSB54Gv4x64+2d7cf BUCKET_ID: X64_0x1E_0_WUSB54Gv4x64+2d7cf Followup: MachineOwner ---------
  4. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\dpcrowley\Windows_NT6_BSOD_jcgriff2\011412-33212-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce70 Debug session time: Sat Jan 14 12:56:00.299 2012 (UTC - 7:00) System Uptime: 0 days 1:09:51.984 Loading Kernel Symbols ............................................................... ................................................................ ................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Unable to load image \SystemRoot\system32\DRIVERS\WUSB54Gv4x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for WUSB54Gv4x64.sys *** ERROR: Module load completed but symbols could not be loaded for WUSB54Gv4x64.sys Probably caused by : WUSB54Gv4x64.sys ( WUSB54Gv4x64+2d7cf ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +3432373430323564 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff88002ffd5a8 -- (.exr 0xfffff88002ffd5a8) ExceptionAddress: fffff8800582d7cf (WUSB54Gv4x64+0x000000000002d7cf) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff88002ffd650 -- (.trap 0xfffff88002ffd650) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=958f6d582900618e rbx=0000000000000000 rcx=fffffa80088c7ff0 rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800582d7cf rsp=fffff88002ffd7e0 rbp=0000000000000000 r8=fffffa8009422000 r9=0000000000000000 r10=fffffa8007c79940 r11=0000000000000002 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc WUSB54Gv4x64+0x2d7cf: fffff880`0582d7cf ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ac72ee to fffff80002acf590 STACK_TEXT: fffff880`02ffc698 fffff800`02ac72ee : fffffa80`0892907c 00000000`000058c4 fffff880`02ffce10 fffff800`02afc524 : nt!KeBugCheck fffff880`02ffc6a0 fffff800`02af52dd : fffff800`02cddb7c fffff800`02c17e68 fffff800`02a5f000 fffff880`02ffd5a8 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`02ffc6d0 fffff800`02afc950 : fffff800`02c1eb0c fffff880`02ffc748 fffff880`02ffd5a8 fffff800`02a5f000 : nt!RtlpExecuteHandlerForException+0xd fffff880`02ffc700 fffff800`02b098cf : fffff880`02ffd5a8 fffff880`02ffce10 fffff880`00000000 fffffa80`07c79940 : nt!RtlDispatchException+0x410 fffff880`02ffcde0 fffff800`02acec02 : fffff880`02ffd5a8 fffffa80`08965da0 fffff880`02ffd650 fffffa80`07c63d00 : nt!KiDispatchException+0x16f fffff880`02ffd470 fffff800`02acd50a : fffffa80`63536f56 fffffa80`072c5b80 fffffa80`07a957c0 fffff880`011ad001 : nt!KiExceptionDispatch+0xc2 fffff880`02ffd650 fffff880`0582d7cf : fffffa80`088c8000 00000000`00004001 fffffa80`07c79940 fffffa80`08965da0 : nt!KiGeneralProtectionFault+0x10a fffff880`02ffd7e0 fffffa80`088c8000 : 00000000`00004001 fffffa80`07c79940 fffffa80`08965da0 fffffa80`088c8000 : WUSB54Gv4x64+0x2d7cf fffff880`02ffd7e8 00000000`00004001 : fffffa80`07c79940 fffffa80`08965da0 fffffa80`088c8000 00000000`00004000 : 0xfffffa80`088c8000 fffff880`02ffd7f0 fffffa80`07c79940 : fffffa80`08965da0 fffffa80`088c8000 00000000`00004000 fffffa80`00000000 : 0x4001 fffff880`02ffd7f8 fffffa80`08965da0 : fffffa80`088c8000 00000000`00004000 fffffa80`00000000 958f6d58`2900618e : 0xfffffa80`07c79940 fffff880`02ffd800 fffffa80`088c8000 : 00000000`00004000 fffffa80`00000000 958f6d58`2900618e fffffa80`06994100 : 0xfffffa80`08965da0 fffff880`02ffd808 00000000`00004000 : fffffa80`00000000 958f6d58`2900618e fffffa80`06994100 fffff880`0582da1a : 0xfffffa80`088c8000 fffff880`02ffd810 fffffa80`00000000 : 958f6d58`2900618e fffffa80`06994100 fffff880`0582da1a fffffa80`088b4000 : 0x4000 fffff880`02ffd818 958f6d58`2900618e : fffffa80`06994100 fffff880`0582da1a fffffa80`088b4000 00000000`00000000 : 0xfffffa80`00000000 fffff880`02ffd820 fffffa80`06994100 : fffff880`0582da1a fffffa80`088b4000 00000000`00000000 fffffa80`075d2ca0 : 0x958f6d58`2900618e fffff880`02ffd828 fffff880`0582da1a : fffffa80`088b4000 00000000`00000000 fffffa80`075d2ca0 00000000`00000000 : 0xfffffa80`06994100 fffff880`02ffd830 fffffa80`088b4000 : 00000000`00000000 fffffa80`075d2ca0 00000000`00000000 fffffa80`075d2e03 : WUSB54Gv4x64+0x2da1a fffff880`02ffd838 00000000`00000000 : fffffa80`075d2ca0 00000000`00000000 fffffa80`075d2e03 fffff880`0582d96a : 0xfffffa80`088b4000 STACK_COMMAND: kb FOLLOWUP_IP: WUSB54Gv4x64+2d7cf fffff880`0582d7cf ?? ??? SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: WUSB54Gv4x64+2d7cf FOLLOWUP_NAME: MachineOwner MODULE_NAME: WUSB54Gv4x64 IMAGE_NAME: WUSB54Gv4x64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 45923fcb FAILURE_BUCKET_ID: X64_0x1E_0_WUSB54Gv4x64+2d7cf BUCKET_ID: X64_0x1E_0_WUSB54Gv4x64+2d7cf Followup: MachineOwner ---------
  5. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\dpcrowley\Windows_NT6_BSOD_jcgriff2\011412-23665-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02a07000 PsLoadedModuleList = 0xfffff800`02c44e70 Debug session time: Sat Jan 14 13:41:40.535 2012 (UTC - 7:00) System Uptime: 0 days 0:44:56.236 Loading Kernel Symbols ............................................................... ................................................................ ................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Unable to load image \SystemRoot\system32\DRIVERS\WUSB54Gv4x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for WUSB54Gv4x64.sys *** ERROR: Module load completed but symbols could not be loaded for WUSB54Gv4x64.sys Probably caused by : WUSB54Gv4x64.sys ( WUSB54Gv4x64+2d7cf ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +3432373430323564 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff88002dfd5a8 -- (.exr 0xfffff88002dfd5a8) ExceptionAddress: fffff8800582d7cf (WUSB54Gv4x64+0x000000000002d7cf) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff88002dfd650 -- (.trap 0xfffff88002dfd650) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=958f6d58e6b0618e rbx=0000000000000000 rcx=fffffa80088aeff0 rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800582d7cf rsp=fffff88002dfd7e0 rbp=0000000000000000 r8=fffffa8009336d00 r9=0000000000000000 r10=fffffa8007cd3e70 r11=0000000000000002 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc WUSB54Gv4x64+0x2d7cf: fffff880`0582d7cf ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a6f2ee to fffff80002a77590 STACK_TEXT: fffff880`02dfc698 fffff800`02a6f2ee : 00000000`00000000 00000000`0000fbf0 fffff880`02dfce10 fffff800`02aa4524 : nt!KeBugCheck fffff880`02dfc6a0 fffff800`02a9d2dd : fffff800`02c85b7c fffff800`02bbfe68 fffff800`02a07000 fffff880`02dfd5a8 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`02dfc6d0 fffff800`02aa4950 : fffff800`02bc6b0c fffff880`02dfc748 fffff880`02dfd5a8 fffff800`02a07000 : nt!RtlpExecuteHandlerForException+0xd fffff880`02dfc700 fffff800`02ab18cf : fffff880`02dfd5a8 fffff880`02dfce10 fffff880`00000000 fffffa80`07cd3e70 : nt!RtlDispatchException+0x410 fffff880`02dfcde0 fffff800`02a76c02 : fffff880`02dfd5a8 fffffa80`08925e70 fffff880`02dfd650 fffffa80`07cdfc20 : nt!KiDispatchException+0x16f fffff880`02dfd470 fffff800`02a7550a : fffffa80`00000000 00000000`00000001 fffffa80`09063010 fffff880`04fb3808 : nt!KiExceptionDispatch+0xc2 fffff880`02dfd650 fffff880`0582d7cf : fffffa80`088af000 fffff880`00d74afc fffffa80`07cd3e70 fffffa80`08925e70 : nt!KiGeneralProtectionFault+0x10a fffff880`02dfd7e0 fffffa80`088af000 : fffff880`00d74afc fffffa80`07cd3e70 fffffa80`08925e70 fffffa80`088af000 : WUSB54Gv4x64+0x2d7cf fffff880`02dfd7e8 fffff880`00d74afc : fffffa80`07cd3e70 fffffa80`08925e70 fffffa80`088af000 fffffa80`07ed9101 : 0xfffffa80`088af000 fffff880`02dfd7f0 fffff880`05835f65 : fffffa80`088c0ac0 fffffa80`088c0ac0 fffffa80`086d0850 fffff880`0582d96a : Wdf01000!imp_WdfRequestReuse+0x12c fffff880`02dfd840 fffffa80`088c0ac0 : fffffa80`088c0ac0 fffffa80`086d0850 fffff880`0582d96a fffffa80`0889b000 : WUSB54Gv4x64+0x35f65 fffff880`02dfd848 fffffa80`088c0ac0 : fffffa80`086d0850 fffff880`0582d96a fffffa80`0889b000 fffffa80`089239f0 : 0xfffffa80`088c0ac0 fffff880`02dfd850 fffffa80`086d0850 : fffff880`0582d96a fffffa80`0889b000 fffffa80`089239f0 fffffa80`0889b000 : 0xfffffa80`088c0ac0 fffff880`02dfd858 fffff880`0582d96a : fffffa80`0889b000 fffffa80`089239f0 fffffa80`0889b000 fffffa80`07c847d0 : 0xfffffa80`086d0850 fffff880`02dfd860 fffffa80`0889b000 : fffffa80`089239f0 fffffa80`0889b000 fffffa80`07c847d0 fffffa80`09336e20 : WUSB54Gv4x64+0x2d96a fffff880`02dfd868 fffffa80`089239f0 : fffffa80`0889b000 fffffa80`07c847d0 fffffa80`09336e20 fffffa80`089239f0 : 0xfffffa80`0889b000 fffff880`02dfd870 fffffa80`0889b000 : fffffa80`07c847d0 fffffa80`09336e20 fffffa80`089239f0 fffffa80`08794330 : 0xfffffa80`089239f0 fffff880`02dfd878 fffffa80`07c847d0 : fffffa80`09336e20 fffffa80`089239f0 fffffa80`08794330 fffffa80`07c847d0 : 0xfffffa80`0889b000 fffff880`02dfd880 fffffa80`09336e20 : fffffa80`089239f0 fffffa80`08794330 fffffa80`07c847d0 00000000`00000018 : 0xfffffa80`07c847d0 fffff880`02dfd888 fffffa80`089239f0 : fffffa80`08794330 fffffa80`07c847d0 00000000`00000018 fffffa80`0889b000 : 0xfffffa80`09336e20 fffff880`02dfd890 fffffa80`08794330 : fffffa80`07c847d0 00000000`00000018 fffffa80`0889b000 00000000`00000000 : 0xfffffa80`089239f0 fffff880`02dfd898 fffffa80`07c847d0 : 00000000`00000018 fffffa80`0889b000 00000000`00000000 fffffa80`08925010 : 0xfffffa80`08794330 fffff880`02dfd8a0 00000000`00000018 : fffffa80`0889b000 00000000`00000000 fffffa80`08925010 00000000`00000580 : 0xfffffa80`07c847d0 fffff880`02dfd8a8 fffffa80`0889b000 : 00000000`00000000 fffffa80`08925010 00000000`00000580 00000000`00000064 : 0x18 fffff880`02dfd8b0 00000000`00000000 : fffffa80`08925010 00000000`00000580 00000000`00000064 fffffa80`07096010 : 0xfffffa80`0889b000 STACK_COMMAND: kb FOLLOWUP_IP: WUSB54Gv4x64+2d7cf fffff880`0582d7cf ?? ??? SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: WUSB54Gv4x64+2d7cf FOLLOWUP_NAME: MachineOwner MODULE_NAME: WUSB54Gv4x64 IMAGE_NAME: WUSB54Gv4x64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 45923fcb FAILURE_BUCKET_ID: X64_0x1E_0_WUSB54Gv4x64+2d7cf BUCKET_ID: X64_0x1E_0_WUSB54Gv4x64+2d7cf Followup: MachineOwner ---------
  6. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\dpcrowley\Windows_NT6_BSOD_jcgriff2\011412-22042-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c5ae70 Debug session time: Sat Jan 14 14:21:25.807 2012 (UTC - 7:00) System Uptime: 0 days 0:04:03.118 Loading Kernel Symbols ............................................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +3335366539353066 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002a9b0ca to fffff88003db47f2 STACK_TEXT: fffff800`03faac98 fffff800`02a9b0ca : 00000000`0035e22c fffffa80`08182dd8 fffff800`02c15c40 00000000`00000001 : 0xfffff880`03db47f2 fffff800`03faaca0 fffff800`02a95d5c : fffff800`02c07e80 fffff800`00000000 00000000`00000000 fffff880`149a8db0 : nt!PoIdle+0x53a fffff800`03faad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c STACK_COMMAND: kb FOLLOWUP_IP: nt!PoIdle+53a fffff800`02a9b0ca 0fba25761518000f bt dword ptr [nt!PerfGlobalGroupMask+0x8 (fffff800`02c1c648)],0Fh SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!PoIdle+53a FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44 FAILURE_BUCKET_ID: X64_0x1E_0_nt!PoIdle+53a BUCKET_ID: X64_0x1E_0_nt!PoIdle+53a Followup: MachineOwner ---------
  7. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\dpcrowley\Windows_NT6_BSOD_jcgriff2\011412-19546-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Unable to load image Unknown_Module_00000000`001dab86, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`001dab86 *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`001dab86 Debugger can not determine kernel base address Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce70 Debug session time: Sat Jan 14 14:24:24.760 2012 (UTC - 7:00) System Uptime: 0 days 0:02:29.445 Unable to load image Unknown_Module_00000000`001dab86, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`001dab86 *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`001dab86 Debugger can not determine kernel base address Loading Kernel Symbols . Loading User Symbols Loading unloaded module list .................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Unable to load image Unknown_Module_00000000`001dab86, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`001dab86 *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`001dab86 Unknown module 'Unknown_Module_00000000_001dab86' found on stack, using vad to reload module. !vad_reload -1 0x1dab86 02000000`0021309c: Unable to get VAD.PrivateMemory ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ Unknown module 'Unknown_Module_00000000_001dab86' found on stack, using vad to reload module. !vad_reload -1 0x1dab86 02000000`0021309c: Unable to get VAD.PrivateMemory ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +3335366539353066 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002add0ca to fffff880019e17f2 STACK_TEXT: fffff800`00b9cc98 fffff800`02add0ca : 00000000`0035e240 fffffa80`080d2dd8 fffff800`02c57c40 00000000`00000001 : 0xfffff880`019e17f2 fffff800`00b9cca0 00000000`0035e240 : fffffa80`080d2dd8 fffff800`02c57c40 00000000`00000001 fffff800`02c49e80 : 0xfffff800`02add0ca fffff800`00b9cca8 fffffa80`080d2dd8 : fffff800`02c57c40 00000000`00000001 fffff800`02c49e80 fffff800`02adab57 : Unknown_Module_00000000_001dab86+0x1836ba fffff800`00b9ccb0 fffff800`02c57c40 : 00000000`00000001 fffff800`02c49e80 fffff800`02adab57 00000000`1f8b3a18 : 0xfffffa80`080d2dd8 fffff800`00b9ccb8 00000000`00000001 : fffff800`02c49e80 fffff800`02adab57 00000000`1f8b3a18 00000000`1f8b3a07 : 0xfffff800`02c57c40 fffff800`00b9ccc0 fffff800`02c49e80 : fffff800`02adab57 00000000`1f8b3a18 00000000`1f8b3a07 00000000`1f8b3a18 : 0x1 fffff800`00b9ccc8 fffff800`02adab57 : 00000000`1f8b3a18 00000000`1f8b3a07 00000000`1f8b3a18 00000000`0000006a : 0xfffff800`02c49e80 fffff800`00b9ccd0 00000000`1f8b3a18 : 00000000`1f8b3a07 00000000`1f8b3a18 00000000`0000006a fffffa80`080d2d40 : 0xfffff800`02adab57 fffff800`00b9ccd8 00000000`1f8b3a07 : 00000000`1f8b3a18 00000000`0000006a fffffa80`080d2d40 400000c2`400000c1 : 0x1f8b3a18 fffff800`00b9cce0 00000000`1f8b3a18 : 00000000`0000006a fffffa80`080d2d40 400000c2`400000c1 fffffa80`400000c3 : 0x1f8b3a07 fffff800`00b9cce8 00000000`0000006a : fffffa80`080d2d40 400000c2`400000c1 fffffa80`400000c3 00000000`1b0b9444 : 0x1f8b3a18 fffff800`00b9ccf0 fffffa80`080d2d40 : 400000c2`400000c1 fffffa80`400000c3 00000000`1b0b9444 00000000`000004df : 0x6a fffff800`00b9ccf8 400000c2`400000c1 : fffffa80`400000c3 00000000`1b0b9444 00000000`000004df fffff800`02ad578d : 0xfffffa80`080d2d40 fffff800`00b9cd00 fffffa80`400000c3 : 00000000`1b0b9444 00000000`000004df fffff800`02ad578d 00000000`00000010 : 0x400000c2`400000c1 fffff800`00b9cd08 00000000`1b0b9444 : 00000000`000004df fffff800`02ad578d 00000000`00000010 00000000`00000202 : 0xfffffa80`400000c3 fffff800`00b9cd10 00000000`000004df : fffff800`02ad578d 00000000`00000010 00000000`00000202 00000000`00000087 : 0x1b0b9444 fffff800`00b9cd18 fffff800`02ad578d : 00000000`00000010 00000000`00000202 00000000`00000087 fffff800`02ad5842 : 0x4df fffff800`00b9cd20 00000000`00000010 : 00000000`00000202 00000000`00000087 fffff800`02ad5842 fffff800`00b96080 : 0xfffff800`02ad578d fffff800`00b9cd28 00000000`00000202 : 00000000`00000087 fffff800`02ad5842 fffff800`00b96080 fffffa80`069ab890 : 0x10 fffff800`00b9cd30 00000000`00000087 : fffff800`02ad5842 fffff800`00b96080 fffffa80`069ab890 00000000`00000000 : 0x202 fffff800`00b9cd38 fffff800`02ad5842 : fffff800`00b96080 fffffa80`069ab890 00000000`00000000 00000000`00000000 : 0x87 fffff800`00b9cd40 fffff800`00b96080 : fffffa80`069ab890 00000000`00000000 00000000`00000000 fffffa80`092f0b60 : 0xfffff800`02ad5842 fffff800`00b9cd48 fffffa80`069ab890 : 00000000`00000000 00000000`00000000 fffffa80`092f0b60 00000000`00000002 : 0xfffff800`00b96080 fffff800`00b9cd50 00000000`00000000 : 00000000`00000000 fffffa80`092f0b60 00000000`00000002 fffff800`02c57c40 : 0xfffffa80`069ab890 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: CORRUPT_MODULELIST Followup: MachineOwner ---------
  8. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\dpcrowley\Windows_NT6_BSOD_jcgriff2\011412-18548-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02a5d000 PsLoadedModuleList = 0xfffff800`02c9ae70 Debug session time: Sat Jan 14 15:22:54.645 2012 (UTC - 7:00) System Uptime: 0 days 0:58:06.346 Loading Kernel Symbols .............................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 Loading User Symbols Loading unloaded module list .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. ..Missing image name, possible paged-out or corrupt data. Missing image name, possible paged-out or corrupt data. ...Missing image name, possible paged-out or corrupt data. ..Missing image name, possible paged-out or corrupt data. ..Missing image name, possible paged-out or corrupt data. ... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Probably caused by : Wdf01000.sys ( Wdf01000!FxIoTarget::RemoveCompletedRequestLocked+b7 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +3432373430323564 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff88002ffd5a8 -- (.exr 0xfffff88002ffd5a8) ExceptionAddress: fffff8800582d7cf ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff88002ffd650 -- (.trap 0xfffff88002ffd650) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=958f6d58b880618e rbx=0000000000000000 rcx=fffffa80088a7ff0 rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800582d7cf rsp=fffff88002ffd7e0 rbp=0000000000000000 r8=fffffa8009260c00 r9=0000000000000000 r10=fffffa8007cdfc80 r11=0000000000000002 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc fffff880`0582d7cf ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ac52ee to fffff80002acd590 STACK_TEXT: fffff880`02ffd7e0 fffffa80`088a8000 : fffff880`02ffd890 fffffa80`07cdfc80 fffffa80`088e6ad0 fffffa80`088a8000 : 0xfffff880`0582d7cf fffff880`02ffd7e8 fffff880`02ffd890 : fffffa80`07cdfc80 fffffa80`088e6ad0 fffffa80`088a8000 fffffa80`088e3d40 : 0xfffffa80`088a8000 fffff880`02ffd7f0 fffffa80`07cdfc80 : fffffa80`088e6ad0 fffffa80`088a8000 fffffa80`088e3d40 00000000`00000001 : 0xfffff880`02ffd890 fffff880`02ffd7f8 fffffa80`088e6ad0 : fffffa80`088a8000 fffffa80`088e3d40 00000000`00000001 958f6d58`b880618e : 0xfffffa80`07cdfc80 fffff880`02ffd800 fffffa80`088a8000 : fffffa80`088e3d40 00000000`00000001 958f6d58`b880618e fffffa80`0888f010 : 0xfffffa80`088e6ad0 fffff880`02ffd808 fffffa80`088e3d40 : 00000000`00000001 958f6d58`b880618e fffffa80`0888f010 fffff880`0582da1a : 0xfffffa80`088a8000 fffff880`02ffd810 00000000`00000001 : 958f6d58`b880618e fffffa80`0888f010 fffff880`0582da1a fffffa80`08894000 : 0xfffffa80`088e3d40 fffff880`02ffd818 958f6d58`b880618e : fffffa80`0888f010 fffff880`0582da1a fffffa80`08894000 fffff800`02a16e08 : 0x1 fffff880`02ffd820 fffffa80`0888f010 : fffff880`0582da1a fffffa80`08894000 fffff800`02a16e08 fffffa80`0888f010 : 0x958f6d58`b880618e fffff880`02ffd828 fffff880`0582da1a : fffffa80`08894000 fffff800`02a16e08 fffffa80`0888f010 00000000`00000002 : 0xfffffa80`0888f010 fffff880`02ffd830 fffffa80`08894000 : fffff800`02a16e08 fffffa80`0888f010 00000000`00000002 fffffa80`08089350 : 0xfffff880`0582da1a fffff880`02ffd838 fffff800`02a16e08 : fffffa80`0888f010 00000000`00000002 fffffa80`08089350 fffff880`0582d96a : 0xfffffa80`08894000 fffff880`02ffd840 0000057f`f830c5c8 : fffffa80`09260c58 fffffa80`088e6d40 fffffa80`07cf3a30 fffff880`00d5e30f : hal!HalpDmaSyncMapBuffers+0x1b0 fffff880`02ffd8f0 fffffa80`09260c58 : fffffa80`088e6d40 fffffa80`07cf3a30 fffff880`00d5e30f 00000000`00000007 : 0x57f`f830c5c8 fffff880`02ffd8f8 fffffa80`088e6d40 : fffffa80`07cf3a30 fffff880`00d5e30f 00000000`00000007 fffff880`13e16020 : 0xfffffa80`09260c58 fffff880`02ffd900 fffffa80`07cf3a30 : fffff880`00d5e30f 00000000`00000007 fffff880`13e16020 fffffa80`07f1a608 : 0xfffffa80`088e6d40 fffff880`02ffd908 fffff880`00d5e30f : 00000000`00000007 fffff880`13e16020 fffffa80`07f1a608 fffff880`13e1154a : 0xfffffa80`07cf3a30 fffff880`02ffd910 fffff880`00d5ec9b : fffffa80`07cf3a30 fffffa80`07cf3a30 fffffa80`07cf3a40 fffffa80`08629001 : Wdf01000!FxIoTarget::RemoveCompletedRequestLocked+0xb7 fffff880`02ffd960 fffff880`00d5edc4 : fffffa80`08592302 fffff880`13e06f3d 00000000`00000000 fffff800`02a177d8 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb fffff880`02ffd9d0 fffff800`02ab7fc5 : fffffa80`096a3540 fffff800`02c022dd 00000000`0000093a fffff800`02a16354 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c fffff880`02ffda00 fffff800`02acfbb6 : fffffa80`0890efbb 00000000`00000000 00000000`00000000 fffffa80`0890ee10 : nt!IopUnloadSafeCompletion+0x55 fffff880`02ffda30 fffff880`13e135e9 : fffffa80`07f19050 fffffa80`09260c00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x336 fffff880`02ffdb20 fffffa80`07f19050 : fffffa80`09260c00 00000000`00000000 00000000`00000000 fffffa80`0000000f : 0xfffff880`13e135e9 fffff880`02ffdb28 fffffa80`09260c00 : 00000000`00000000 00000000`00000000 fffffa80`0000000f 00000000`00000000 : 0xfffffa80`07f19050 fffff880`02ffdb30 00000000`00000000 : 00000000`00000000 fffffa80`0000000f 00000000`00000000 fffffa80`06d819f0 : 0xfffffa80`09260c00 STACK_COMMAND: .trap 0xfffff88002ffd650 ; kb FOLLOWUP_IP: Wdf01000!FxIoTarget::RemoveCompletedRequestLocked+b7 fffff880`00d5e30f 4038ab3e010000 cmp byte ptr [rbx+13Eh],bpl SYMBOL_STACK_INDEX: 11 SYMBOL_NAME: Wdf01000!FxIoTarget::RemoveCompletedRequestLocked+b7 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Wdf01000 IMAGE_NAME: Wdf01000.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc19f FAILURE_BUCKET_ID: X64_0x1E_0_Wdf01000!FxIoTarget::RemoveCompletedRequestLocked+b7 BUCKET_ID: X64_0x1E_0_Wdf01000!FxIoTarget::RemoveCompletedRequestLocked+b7 Followup: MachineOwner ---------

Please update your WUSB54Gv4x64.sys driver or remove the component/software using it. It caused many of your blue screen crashes.
Code:
WUSB54Gv4x64	fffff880`06e00000	fffff880`06e52000	Wed Dec 27 02:41:31 2006 (45923fcb)	00053254	None	WUSB54Gv4x64.sys
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

The following can be used to supplement JMH's post

Check for viruses.
Download and install the free version of Malwarebytes : Free anti-malware, anti-virus and spyware removal download (do not start the trial) and make sure it is updated. Do not run a scan yet.
Download VIPRE Rescue - VIPRE Computer Recovery Solution from Sunbelt Software but do not unzip it yet
Download the Fakerean removal tool but do not run it yet.
Start your computer in Safe Mode
Unzip VIPRE Rescue and let it run.
Run a full scan with Malwarebytes.
Run the fakerean removal tool.
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log

Run Windows updates. I note you do not yet have SP1 on your computer. Install all updates and driver updates available and post back whether you are still having stability issues.

Alternative method to update to Service Pack 1
Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site
Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH
My System SpecsSystem Spec
16 Jan 2012   #5

Windows 7 Professions 64-bit
 
 

So I have followed all directions thus far. All tests passed for Memtest, I ran all the virus programs and I did find and remove Trojan.FakeAlert.SecGen using malware bytes. I have not used disk check yet, but I plan on it, I will upload my DMP's again because I got a new BSOD today 0x000000F4 I believe, anyway it gave parameters this time so it may be informational, if you guys could look into that. I didn't know how to delete any of my old DMP's sorry about that. I also did download a tool to fully remove my anti-virus, kapersky and have replaced it with the Windows one.

Also my internet has slowed down quite a bit since updating its driver and I can't figure out why.

Thanks a lot guys for your help.
My System SpecsSystem Spec
16 Jan 2012   #6

Windows 7 Home Premium 64 Bit
 
 

Code:
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\dpcrowley\Windows_NT6_BSOD_jcgriff2\011612-22136-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02a06000 PsLoadedModuleList = 0xfffff800`02c43e70
Debug session time: Mon Jan 16 16:11:00.308 2012 (UTC - 7:00)
System Uptime: 0 days 0:01:33.619
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8008dea060, fffffa8008dea340, fffff80002d7e300}

Probably caused by : csrss.exe

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8008dea060, Terminating object
Arg3: fffffa8008dea340, Process image file name
Arg4: fffff80002d7e300, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8008dea060

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

BUGCHECK_STR:  0xF4_C000001D

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02c37b08 fffff800`02e02c92 : 00000000`000000f4 00000000`00000003 fffffa80`08dea060 fffffa80`08dea340 : nt!KeBugCheckEx
fffff880`02c37b10 fffff800`02daadf3 : ffffffff`ffffffff fffffa80`08e47b60 fffffa80`08dea060 fffffa80`08dea060 : nt!PspCatchCriticalBreak+0x92
fffff880`02c37b50 fffff800`02d3030c : ffffffff`ffffffff 00000000`00000001 fffffa80`08dea060 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17336
fffff880`02c37ba0 fffff800`02a75813 : fffffa80`08dea060 fffff880`c000001d 00000000`004ef560 fffffa80`08e47b60 : nt!NtTerminateProcess+0x20c
fffff880`02c37c20 00000000`777df97a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`004ed158 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777df97a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_C000001D_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_C000001D_IMAGE_csrss.exe

Followup: MachineOwner
---------
You had a critical system process terminate unexpectedly. This can be caused by the process crashing or the user ending the process through task manager. If you have ended a process through task manager, be careful that it is not a SYSTEM process. Otherwise, it was probably due to the process crashing on its own. System files crash due to corruption. Corruption can occur at the hard disk level, or the system level. Run your disk check first. Then do the next step.
Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after the third run or if the first run comes back with no integrity violations.
My System SpecsSystem Spec
17 Jan 2012   #7

Windows 7 Professions 64-bit
 
 

Hey guys,

So I ran my first disc check and...I have not experienced any BSOD errors yet..it has been a day so far. I have tried to use the applications which caused the BSOD, and it has been running fine..I will post my log still to actually see if something was fixed or my computer is being nice for a day.

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
209152 file records processed. File verification completed.
800 large file records processed. 0 bad file records processed. 2 EA records processed. 60 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
247040 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
209152 file SDs/SIDs processed. Cleaning up 1623 unused index entries from index $SII of file 0x9.
Cleaning up 1623 unused index entries from index $SDH of file 0x9.
Cleaning up 1623 unused security descriptors.
Security descriptor verification completed.
18945 data files processed. CHKDSK is verifying Usn Journal...
36251408 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
209136 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
8061834 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

78140128 KB total disk space.
45523668 KB in 79083 files.
54276 KB in 18946 indexes.
0 KB in bad sectors.
314844 KB in use by the system.
65536 KB occupied by the log file.
32247340 KB available on disk.

4096 bytes in each allocation unit.
19535032 total allocation units on disk.
8061835 allocation units available on disk.

Internal Info:
00 31 03 00 f8 7e 01 00 5a d8 02 00 00 00 00 00 .1...~..Z.......
d7 00 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 ....<...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
My System SpecsSystem Spec
17 Jan 2012   #8

Windows 7 Home Premium 64 Bit
 
 

No errors were found on the disk... See how it runs for a while and let us know if you need help.
My System SpecsSystem Spec
07 Feb 2012   #9

Windows 7 Home Premium 64 Bit
 
 

Is the system more stable after the disk check? How is your internet speed? Need further help?
My System SpecsSystem Spec
Reply

 BSOD error 0x0000001e




Thread Tools



Similar help and support threads for2: BSOD error 0x0000001e
Thread Forum
BSOD error 0x0000001e BSOD Help and Support
Random BSOD stop error 0x0000001E, hardware error? BSOD Help and Support
BSOD error 0x0000001e BSOD Help and Support
BSOD error 0x0000001e BSOD Help and Support
BSOD error 0x0000001e and others BSOD Help and Support
BSOD error 0x0000001e BSOD Help and Support
0x0000001E BSoD Error BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:46 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33