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: BlueScreen after connecting to company network

30 Nov 2009   #11
Thomas R

Windows 7 Ultimate x64 SP1 Ver. 6.1.7601 (Build 7601)
 
 

Just had 2 blue screens while ZoneAlarm was not loaded - so it wasn't that. Would have been too easy I guess

Would a fullsize memory dump reveal more about the actual source of these crashes than a mini dump?

BTW our company network runs on Windows 2008 servers and it's a mixed network with Windows PCs (2000 & XP and maybe 1 other 7) and Macs.
At home my network is a D-Link DIR-825 Router, a D-Link DNS-323 Net-Drive and a HP LaserJet 5000. And there - as said before - I have no crashes.


My System SpecsSystem Spec
.
30 Nov 2009   #12
torrentg

7600.20510 x86
 
 

ZA was definitely the cause previously. Maybe there's something else going on now. You can post a new minidump if you like.

You have to completely uninstall ZA to have any beneficial effect. Not just disable.
My System SpecsSystem Spec
30 Nov 2009   #13
Thomas R

Windows 7 Ultimate x64 SP1 Ver. 6.1.7601 (Build 7601)
 
 

Here are the latest Mini Dump files.

I just had even crashes in save mode with network support.
My System SpecsSystem Spec
.

01 Dec 2009   #14
usasma
Microsoft MVP

 
 

These older drivers could be causing issues, please update them as soon as you can:
Code:
rimspx64.sys Tue Feb 27 02:10:37 2007
rixdpx64.sys Mon Mar 26 06:48:23 2007
SynTP.sys    Fri Oct 26 16:58:42 2007
stwrt64.sys  Thu Sep 13 11:30:19 2007
rimmpx64.sys Sun Mar 18 23:09:34 2007
I'd suggest running Driver Verifier to see if it can force a crash that will identify the culprit. Please follow these instructions exactly:
Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.


So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).


Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.


Reboot the system and waitfor it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.


Reboot into Windows (after the crash) and turn offDriver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.


More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
The memory dumps are virtually identical:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov 30 16:49:33.940 2009 (GMT-5)
System Uptime: 0 days 2:56:42.969
BugCheck 7F, {8, 80050031, 6f8, fffff80002a53798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov 30 17:05:38.093 2009 (GMT-5)
System Uptime: 0 days 0:15:27.733
BugCheck 7F, {8, 80050031, 6f8, fffff80001e89798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov 30 17:19:27.077 2009 (GMT-5)
System Uptime: 0 days 0:13:21.577
BugCheck 7F, {8, 80050031, 6f8, fffff80001e8e798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov 30 17:21:15.549 2009 (GMT-5)
System Uptime: 0 days 0:00:58.562
BugCheck 7F, {8, 80050031, 6f8, fffff80002a4f798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov 30 17:22:52.928 2009 (GMT-5)
System Uptime: 0 days 0:00:45.942
BugCheck 7F, {8, 80050031, 6f8, fffff80002a8b798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov 30 13:52:26.524 2009 (GMT-5)
System Uptime: 0 days 0:00:25.552
BugCheck 7F, {8, 80050031, 6f8, fffff80002a98798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov 30 13:46:26.417 2009 (GMT-5)
System Uptime: 0 days 0:05:16.430
BugCheck 7F, {8, 80050031, 6f8, fffff80002a9a798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
My System SpecsSystem Spec
02 Dec 2009   #15
Thomas R

Windows 7 Ultimate x64 SP1 Ver. 6.1.7601 (Build 7601)
 
 

OK, So I cloned my hard drive and used that clone for the test - just to be on the safe side.

I executed the test as described and Windows crashes already during startup with a blue screen.
It says that it is writing a dump file but after several crashes I could only find one new file in the Widows\Minidump folder. See attachment
My System SpecsSystem Spec
02 Dec 2009   #16
usasma
Microsoft MVP

 
 

Zone Alarm (vsdatant.sys). Haven't seen one of those in a long, long time!
This is a Driver Verifier enabled minidump, so it's what we were looking for by using Driver Verifier.

Since the driver is dated 17 Oct 09 - I'd suspect that it was either incompatible or corrupted. Uninstalling Zone Alarm would be the first thing to do. If you really want to keep the ZA, then download a fresh copy and install it. If that works, then you're good to go - if not then it's likely to be a compatibility issue.

Here's the memory dump analysis that I did:
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\FUBAR\TempDUMP\DATA\01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a5b000 PsLoadedModuleList = 0xfffff800`02c98e50
Debug session time: Wed Dec  2 16:43:18.162 2009 (GMT-5)
System Uptime: 0 days 0:00:08.098
Loading Kernel Symbols
...............................................................
.....
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {121, 2, fffff88002dc64b0, 0}

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

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

1: kd> !thread;!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;.logclose;q
GetPointerFromAddress: unable to read from fffff80002d03000
THREAD fffffa800370ab00  Cid 0004.0008  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 1
Not impersonating
GetUlongFromAddress: unable to read from fffff80002c41b74
Owning Process            fffffa8003687300       Image:         System
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      519          
Context Switch Count      1155             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address nt!Phase1Initialization (0xfffff80002f4e410)
Stack Init fffff880009a9db0 Current fffff880009a7f90
Base fffff880009aa000 Limit fffff880009a4000 Call 0
Priority 31 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`009a91d8 fffff800`02f563dc : 00000000`000000c4 00000000`00000121 00000000`00000002 fffff880`02dc64b0 : nt!KeBugCheckEx
fffff880`009a91e0 fffff800`02f69654 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00000001 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`009a9220 fffff880`02d79865 : fffff880`02dc64b0 00000000`00000000 00000000`00000001 fffff880`02da4c0e : nt!VerifierKeWaitForSingleObject+0x94
fffff880`009a92a0 fffff880`02dc64b0 : 00000000`00000000 00000000`00000001 fffff880`02da4c0e 00000000`00000000 : vsdatant+0x19865
fffff880`009a92a8 00000000`00000000 : 00000000`00000001 fffff880`02da4c0e 00000000`00000000 fffffa80`0365af18 : vsdatant+0x664b0

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000121, Waiting at DISPATCH_LEVEL, without a timeout.
Arg2: 0000000000000002, IRQL value.
Arg3: fffff88002dc64b0, Object to wait on.
Arg4: 0000000000000000, Timeout parameter.

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


BUGCHECK_STR:  0xc4_121

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f563dc to fffff80002accf00

STACK_TEXT:  
fffff880`009a91d8 fffff800`02f563dc : 00000000`000000c4 00000000`00000121 00000000`00000002 fffff880`02dc64b0 : nt!KeBugCheckEx
fffff880`009a91e0 fffff800`02f69654 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00000001 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`009a9220 fffff880`02d79865 : fffff880`02dc64b0 00000000`00000000 00000000`00000001 fffff880`02da4c0e : nt!VerifierKeWaitForSingleObject+0x94
fffff880`009a92a0 fffff880`02dc64b0 : 00000000`00000000 00000000`00000001 fffff880`02da4c0e 00000000`00000000 : vsdatant+0x19865
fffff880`009a92a8 00000000`00000000 : 00000000`00000001 fffff880`02da4c0e 00000000`00000000 fffffa80`0365af18 : vsdatant+0x664b0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
vsdatant+19865
fffff880`02d79865 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  vsdatant+19865

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: vsdatant

IMAGE_NAME:  vsdatant.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ad981d5

FAILURE_BUCKET_ID:  X64_0xc4_121_VRF_vsdatant+19865

BUCKET_ID:  X64_0xc4_121_VRF_vsdatant+19865

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

rax=0000000000000000 rbx=00000000000000c4 rcx=00000000000000c4
rdx=0000000000000121 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002accf00 rsp=fffff880009a91d8 rbp=0000000000000000
 r8=0000000000000002  r9=fffff88002dc64b0 r10=fffff80002fa3cac
r11=000000000000000d r12=0000000000000000 r13=fffffa800370ab00
r14=fffff88002db4f00 r15=fffff78000000300
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
nt!KeBugCheckEx:
fffff800`02accf00 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff880`009a91e0=00000000000000c4
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`009a91d8 fffff800`02f563dc : 00000000`000000c4 00000000`00000121 00000000`00000002 fffff880`02dc64b0 : nt!KeBugCheckEx
fffff880`009a91e0 fffff800`02f69654 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00000001 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`009a9220 fffff880`02d79865 : fffff880`02dc64b0 00000000`00000000 00000000`00000001 fffff880`02da4c0e : nt!VerifierKeWaitForSingleObject+0x94
fffff880`009a92a0 fffff880`02dc64b0 : 00000000`00000000 00000000`00000001 fffff880`02da4c0e 00000000`00000000 : vsdatant+0x19865
fffff880`009a92a8 00000000`00000000 : 00000000`00000001 fffff880`02da4c0e 00000000`00000000 fffffa80`0365af18 : vsdatant+0x664b0
start             end                 module name
fffff800`00b98000 fffff800`00ba2000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff800`02a12000 fffff800`02a5b000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff800`02a5b000 fffff800`03038000   nt       ntkrnlmp.exe Mon Jul 13 19:40:48 2009 (4A5BC600)
fffff880`00c00000 fffff880`00c2a000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00c2a000 fffff880`00c35000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00c4e000 fffff880`00c92000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`00c92000 fffff880`00ca6000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`00ca6000 fffff880`00d04000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00d04000 fffff880`00dc4000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`00dc4000 fffff880`00dcc000   intelide intelide.sys Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`00dcc000 fffff880`00ddc000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`00ddc000 fffff880`00df6000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00df6000 fffff880`00dff000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e00000 fffff880`00e15000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00e15000 fffff880`00e1e000   compbatt compbatt.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00e1e000 fffff880`00e2a000   BATTC    BATTC.SYS    Mon Jul 13 19:31:01 2009 (4A5BC3B5)
fffff880`00e2a000 fffff880`00e3f000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e3f000 fffff880`00e9b000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`00e9d000 fffff880`00f41000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f41000 fffff880`00f50000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f50000 fffff880`00fa7000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`00fa7000 fffff880`00fb0000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00fb0000 fffff880`00fba000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`00fba000 fffff880`00fed000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00fed000 fffff880`00ffa000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01035000 fffff880`01081000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`01081000 fffff880`01095000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01095000 fffff880`010f3000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`010f3000 fffff880`01166000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`01166000 fffff880`011b2000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`011b2000 fffff880`011ec000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`01200000 fffff880`01211000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`01211000 fffff880`0121b000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`0123b000 fffff880`013de000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`013de000 fffff880`013f8000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01400000 fffff880`01410000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`01410000 fffff880`01418000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01418000 fffff880`0142a000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`0142a000 fffff880`01433000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`01435000 fffff880`01527000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`01527000 fffff880`01587000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`01587000 fffff880`015b2000   ksecpkg  ksecpkg.sys  Mon Jul 13 19:50:34 2009 (4A5BC84A)
fffff880`015b2000 fffff880`015fc000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`01601000 fffff880`017fe000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`01800000 fffff880`01825000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`01825000 fffff880`01835000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`01835000 fffff880`0183e000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`0183e000 fffff880`01847000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01847000 fffff880`01850000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`01850000 fffff880`0185b000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0185b000 fffff880`0186c000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`0186c000 fffff880`0188a000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`0188a000 fffff880`01897000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`0189a000 fffff880`018d4000   fvevol   fvevol.sys   Mon Jul 13 19:22:15 2009 (4A5BC1A7)
fffff880`018d4000 fffff880`018ea000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`018ea000 fffff880`0191a000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`0191a000 fffff880`01928000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`01928000 fffff880`01934000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01934000 fffff880`0193d000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0193d000 fffff880`01950000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`01950000 fffff880`0197a000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`0197a000 fffff880`019d6000   klif     klif.sys     Tue Sep 22 06:31:19 2009 (4AB8A777)
fffff880`019d6000 fffff880`019df000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`019df000 fffff880`019e6000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`019e6000 fffff880`019f4000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`02c91000 fffff880`02d1b000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`02d1b000 fffff880`02d60000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`02d60000 fffff880`02df0000   vsdatant vsdatant.sys Sat Oct 17 04:35:33 2009 (4AD981D5)
fffff880`03a76000 fffff880`03f9f000   kl1      kl1.sys      Fri Sep 25 09:59:13 2009 (4ABCCCB1)
start             end                 module name
fffff880`00f50000 fffff880`00fa7000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02c91000 fffff880`02d1b000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`00c2a000 fffff880`00c35000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00df6000 fffff880`00dff000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00c00000 fffff880`00c2a000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00e1e000 fffff880`00e2a000   BATTC    BATTC.SYS    Mon Jul 13 19:31:01 2009 (4A5BC3B5)
fffff880`019df000 fffff880`019e6000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`01950000 fffff880`0197a000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00d04000 fffff880`00dc4000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`018ea000 fffff880`0191a000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00ca6000 fffff880`00d04000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`010f3000 fffff880`01166000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`00e15000 fffff880`00e1e000   compbatt compbatt.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`0191a000 fffff880`01928000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`018d4000 fffff880`018ea000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01934000 fffff880`0193d000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01928000 fffff880`01934000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0193d000 fffff880`01950000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`01081000 fffff880`01095000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01035000 fffff880`01081000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`01211000 fffff880`0121b000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`0189a000 fffff880`018d4000   fvevol   fvevol.sys   Mon Jul 13 19:22:15 2009 (4A5BC1A7)
fffff880`015b2000 fffff880`015fc000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02a12000 fffff800`02a5b000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`0142a000 fffff880`01433000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`00dc4000 fffff880`00dcc000   intelide intelide.sys Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff800`00b98000 fffff800`00ba2000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`03a76000 fffff880`03f9f000   kl1      kl1.sys      Fri Sep 25 09:59:13 2009 (4ABCCCB1)
fffff880`0197a000 fffff880`019d6000   klif     klif.sys     Tue Sep 22 06:31:19 2009 (4AB8A777)
fffff880`013de000 fffff880`013f8000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01587000 fffff880`015b2000   ksecpkg  ksecpkg.sys  Mon Jul 13 19:50:34 2009 (4A5BC84A)
fffff880`00c4e000 fffff880`00c92000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`00ddc000 fffff880`00df6000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`01850000 fffff880`0185b000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00fb0000 fffff880`00fba000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01095000 fffff880`010f3000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`01418000 fffff880`0142a000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01435000 fffff880`01527000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`02d1b000 fffff880`02d60000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01527000 fffff880`01587000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`0185b000 fffff880`0186c000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff800`02a5b000 fffff800`03038000   nt       ntkrnlmp.exe Mon Jul 13 19:40:48 2009 (4A5BC600)
fffff880`0123b000 fffff880`013de000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`019d6000 fffff880`019df000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`00e00000 fffff880`00e15000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00fba000 fffff880`00fed000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00dcc000 fffff880`00ddc000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`01200000 fffff880`01211000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00c92000 fffff880`00ca6000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`01835000 fffff880`0183e000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`0183e000 fffff880`01847000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01847000 fffff880`01850000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`011b2000 fffff880`011ec000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`01410000 fffff880`01418000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01601000 fffff880`017fe000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`0188a000 fffff880`01897000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`0186c000 fffff880`0188a000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`00fed000 fffff880`00ffa000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`019e6000 fffff880`019f4000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`01800000 fffff880`01825000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`01400000 fffff880`01410000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00e2a000 fffff880`00e3f000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e3f000 fffff880`00e9b000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01166000 fffff880`011b2000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`02d60000 fffff880`02df0000   vsdatant vsdatant.sys Sat Oct 17 04:35:33 2009 (4AD981D5)
fffff880`01825000 fffff880`01835000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e9d000 fffff880`00f41000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f41000 fffff880`00f50000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00fa7000 fffff880`00fb0000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
Bugcheck code 000000C4
Arguments 00000000`00000121 00000000`00000002 fffff880`02dc64b0 00000000`00000000
My System SpecsSystem Spec
02 Dec 2009   #17
Thomas R

Windows 7 Ultimate x64 SP1 Ver. 6.1.7601 (Build 7601)
 
 

Some more Minidumps.
One was caused by the SigmaTel Audio driver which is a know problem.
The other one by SynTP.sys (Synaptics). I think that's the TouchPad driver.

I already uninstalled ZoneAlarm Extreme Security from the cloned system and so far I haven't had a crash. So that one looks like confirmed. I will download a fresh ZoneAlarm installation and see what that does.
My System SpecsSystem Spec
02 Dec 2009   #18
torrentg

7600.20510 x86
 
 

ZoneAlarm is not completely uninstalled as there is still bsod from vsdatant.sys.

I use this for many months and is perfect. Try installing it if you want:

https://www.zonealarm.com/security/e...A-60day-1user#
My System SpecsSystem Spec
02 Dec 2009   #19
Thomas R

Windows 7 Ultimate x64 SP1 Ver. 6.1.7601 (Build 7601)
 
 

Those dumps are from before uninstalling ZoneAlarm - after that I no crashes anymore.
My System SpecsSystem Spec
03 Dec 2009   #20
Thomas R

Windows 7 Ultimate x64 SP1 Ver. 6.1.7601 (Build 7601)
 
 

I downloaded and installed a new ZoneAlarm Extreme Security package and now it's working fine now. I also ran the new driver through the verifier test and this time it passed.
Thanks torrentg & usasma for the help.
My System SpecsSystem Spec
Reply

 BlueScreen after connecting to company network




Thread Tools




Similar help and support threads
Thread Forum
Very strange problem connecting to network drives / network.
So im at a complete loss here.... I have a windows 7 pro x86 computer that out of the blue stopped connecting to its network drives. I tried a few things like flushing the dns, re-registering, new IP finally I decided to rejoin it to the domain, big mistake. The computer couldn't contact the...
Network & Sharing
Bluescreen after connecting xbox 360 controller
Whenever I plug my 360 controller into my pc its followed by blue screen of death, can anyone help med out? I didn't have this problem a few weeks ago.I changed usb ports, reinstalled the drivers and its still happening
BSOD Help and Support
How to access an end user's PC on company network
Hello. I'm a desktop analyst and I need access to a remote PC on our network. The user has disabled remote access to his PC. I need to see files on that PC and I planned on using \\domain\computername c$ but it says "could not connect". That command works on other PC's here, but not the one in...
Network & Sharing
Admin rights are removed when connected to the company network
I am allowed to make myself an admininstrator while on the network or off the network but the next time (which is the second, the first time is to make the changes), my administrator rights disappear. I have added myself as an admininstrator in every way listed I think on all threads with no luck.
Network & Sharing
Network Sharing Problem. Connecting Desktop to home network
So i'm having an issue connecting my desktop to my home network for file sharing. My Desktop is connected to the internet like so: Desktop ->(Ethernet cable)-> Uverse 2wire router -> Internet. I have no issues with my internet connection, and in fact I am posting this from my desktop now. ...
Network & Sharing


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 00:33.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App