Could not read faulting driver name (win32k.sys problem)

Hello,
I'm having a problem with a win2k3 server As you can see by the dump, it is Windows Server 2003 Enterprise running terminal services. Even though it is running terminal services, the server is not used in that way except for us to administer it. No users log directly into it, they just print to it via mapped printers.
The function of this server it is our main Printserver with approx 490 printers.
10 days ago the server dumped and gave the same error, but hasn't again until today 26 may 2005. Today it dumped twice, exctaly 1 hour apart.
I debugged the file, but I would like some help with where I might go from here.
If possible, could someone take a look and make some suggestions?
Thanks in advance!

Debugger information:
------
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Mini052605-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 3790.srv03_gdr.050225-1827
Kernel base = 0x804de000 PsLoadedModuleList = 0x8057b6a8
Debug session time: Thu May 26 09:06:40.258 2005 (GMT-7)
System Uptime: 0 days 0:54:39.281
Loading Kernel Symbols
......................................................................................................
Loading unloaded module list
...
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {e3cead91, 0, bf943846, 1}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!vTransparentCopy+f5 )

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

1: kd> !analyse -v;r;kv;lmtn
No export analyse found
eax=f772713c ebx=00000050 ecx=88e8c020 edx=804e5bb0 esi=f7727120 edi=88e8c020
eip=80543ac9 esp=b2aa1868 ebp=b2aa1880 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
nt!KeBugCheckEx+0x19:
80543ac9 5d pop ebp
ChildEBP RetAddr Args to Child
b2aa1880 8052fa2f 00000050 e3cead91 00000000 nt!KeBugCheckEx+0x19 (FPO: [Non-Fpo])
b2aa18d0 804e2dfc 00000000 e3cead91 00000000 nt!MmAccessFault+0x796 (FPO: [Non-Fpo])
b2aa18d0 bf943846 00000000 e3cead91 00000000 nt!KiTrap0E+0xc8 (FPO: [0,0] TrapFrame @ b2aa18e8)
b2aa19a0 bf8c9d6f b2aa1b0c e35a3008 b2aa1d10 win32k!vTransparentCopy+0xf5 (FPO: [Non-Fpo])
b2aa1bc4 bf8ca56c e11d6c98 e2ae9018 b2aa1bf8 win32k!EngTransparentBlt+0x2ef (FPO: [EBP 0xb2aa1ce4] [8,131,0])
b2aa1d30 804dfd24 e1763008 e11d6c98 e365f138 win32k!NtGdiTransparentBlt+0x702 (FPO: [EBP 0xb2aa1d64] [11,78,0])
b2aa1d30 7ffe0304 e1763008 e11d6c98 e365f138 nt!KiSystemService+0xd0 (FPO: [0,0] TrapFrame @ b2aa1d64)
0407f1dc 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4 (FPO: [0,0,0])
start end module name
804de000 80745000 nt ntkrnlmp.exe Sun Feb 27 16:58:53 2005 (42226CCD)
80745000 8076d000 hal halmacpi.dll Mon Mar 24 23:07:28 2003 (3E800030)
b321c000 b323e000 RDPWD RDPWD.SYS Mon Mar 24 23:03:00 2003 (3E7FFF24)
b344e000 b3458000 TDTCP TDTCP.SYS Mon Mar 24 23:02:52 2003 (3E7FFF1C)
b34be000 b34eb000 Fastfat Fastfat.SYS Tue Mar 25 00:00:16 2003 (3E800C90)
b3653000 b36b2000 srv srv.sys Tue Mar 25 00:49:51 2003 (3E80182F)
b3892000 b38c1000 afd afd.sys Mon Mar 24 23:40:50 2003 (3E800802)
b38c1000 b38d9000 Cdfs Cdfs.SYS Tue Mar 25 00:17:19 2003 (3E80108F)
b38d9000 b38ec000 Fips Fips.SYS Tue Mar 25 00:54:59 2003 (3E801963)
b38ec000 b3958000 mrxsmb mrxsmb.sys Tue Jan 18 17:35:18 2005 (41EDB956)
b3958000 b3983000 rdbss rdbss.sys Mon Oct 11 17:38:09 2004 (416B2771)
b3983000 b39b8000 netbt netbt.sys Fri Jul 18 10:16:03 2003 (3F182B53)
b39b8000 b3a1a000 tcpip tcpip.sys Wed Mar 16 21:04:21 2005 (42390FD5)
b3a1a000 b3a36000 ipsec ipsec.sys Mon Mar 24 23:55:45 2003 (3E800B81)
b3aa2000 b3aa2b80 nsapci nsapci.sys Mon Jun 11 11:00:10 2001 (3B25072A)
b4e18000 b4e28980 naveng naveng.sys Tue Mar 15 12:35:44 2005 (42374720)
b4ed3000 b4edd000 dump_mraid35x dump_mraid35x.sys Mon Mar 24 23:05:06 2003 (3E7FFFA2)
b5372000 b537a000 RDPCDD RDPCDD.sys Mon Mar 24 23:03:05 2003 (3E7FFF29)
b5596000 b559d000 Null Null.SYS Mon Mar 24 23:03:05 2003 (3E7FFF29)
b56c1000 b56c8000 dxgthk dxgthk.sys Mon Mar 24 23:05:52 2003 (3E7FFFD0)
b56d9000 b56e6000 wanarp wanarp.sys Mon Mar 24 23:11:22 2003 (3E80011A)
b5865000 b586c000 parvdm parvdm.sys Mon Mar 24 23:03:49 2003 (3E7FFF55)
b5ada000 b5ae3000 ndisuio ndisuio.sys Mon Mar 24 23:09:47 2003 (3E8000BB)
b82d0000 b8368e20 navex15 navex15.sys Tue Mar 15 12:51:30 2005 (42374AD2)
b839a000 b83acf00 SYMEVENT SYMEVENT.SYS Wed Jan 14 18:02:13 2004 (4005F4A5)
b83ad000 b83fc000 savrt savrt.sys Mon Feb 09 15:24:30 2004 (402816AE)
b89f0000 b89f7000 Beep Beep.SYS Mon Mar 24 23:03:04 2003 (3E7FFF28)
b9013000 b901b000 Fs_Rec Fs_Rec.SYS Mon Mar 24 23:08:36 2003 (3E800074)
b914f000 b915f000 Savrtpel Savrtpel.sys Mon Feb 09 15:24:34 2004 (402816B2)
b9ee0000 b9ee8000 mnmdd mnmdd.SYS Mon Mar 24 23:07:53 2003 (3E800049)
b9f7f000 b9f8c000 netbios netbios.sys Mon Mar 24 23:09:53 2003 (3E8000C1)
b9fdf000 b9fee000 msgpc msgpc.sys Mon Mar 24 23:10:12 2003 (3E8000D4)
ba366000 ba36f000 dump_diskdump dump_diskdump.sys Mon Mar 24 23:05:15 2003 (3E7FFFAB)
ba396000 ba3a0000 flpydisk flpydisk.sys Mon Mar 24 23:04:32 2003 (3E7FFF80)
ba5cf000 ba5d9000 Dxapi Dxapi.sys Mon Mar 24 23:06:01 2003 (3E7FFFD9)
ba62f000 ba639000 Msfs Msfs.SYS Mon Mar 24 23:08:56 2003 (3E800088)
ba75a000 ba76d000 usbhub usbhub.sys Mon Mar 24 23:10:46 2003 (3E8000F6)
ba76d000 ba7a0000 update update.sys Tue Mar 25 00:59:59 2003 (3E801A8F)
ba7a0000 ba7d4000 rdpdr rdpdr.sys Mon Mar 24 23:09:30 2003 (3E8000AA)
ba7d4000 ba7e9000 raspptp raspptp.sys Tue Mar 25 00:19:09 2003 (3E8010FD)
ba7e9000 ba804000 ndiswan ndiswan.sys Tue Mar 25 00:48:19 2003 (3E8017D3)
ba804000 ba81b000 rasl2tp rasl2tp.sys Mon Mar 24 23:54:46 2003 (3E800B46)
ba81b000 ba83ce80 USBPORT USBPORT.SYS Mon Mar 24 23:10:43 2003 (3E8000F3)
ba83d000 ba867000 ks ks.sys Tue Mar 25 00:47:36 2003 (3E8017A8)
ba867000 ba87b000 redbook redbook.sys Mon Mar 24 23:04:38 2003 (3E7FFF86)
ba87b000 ba88f000 cdrom cdrom.sys Mon Mar 24 23:05:18 2003 (3E7FFFAE)
ba88f000 ba8a6000 parport parport.sys Mon Mar 24 23:03:56 2003 (3E7FFF5C)
ba8a6000 ba8be000 serial serial.sys Mon Mar 24 23:40:08 2003 (3E8007D8)
ba8be000 ba8d4000 i8042prt i8042prt.sys Tue Mar 25 01:01:43 2003 (3E801AF7)
ba8d4000 ba8ed000 VIDEOPRT VIDEOPRT.SYS Mon Mar 24 23:08:02 2003 (3E800052)
ba8ed000 ba8ff000 cirrus cirrus.sys Mon Mar 24 23:07:45 2003 (3E800041)
ba8ff000 ba989c00 el985n51 el985n51.sys Wed Apr 24 15:33:40 2002 (3CC732C4)
babb3000 babb4ba0 hpgate hpgate.sys Wed Aug 15 12:50:06 2001 (3B7AD26E)
bad38000 bad46000 NDProxy NDProxy.SYS Mon Mar 24 23:11:30 2003 (3E800122)
bad48000 bad57000 termdd termdd.sys Mon Mar 24 23:02:52 2003 (3E7FFF1C)
bad58000 bad61000 raspti raspti.sys Mon Mar 24 23:11:36 2003 (3E800128)
bad68000 bad73000 ptilink ptilink.sys Mon Mar 24 23:03:51 2003 (3E7FFF57)
bad78000 bad83000 TDI TDI.SYS Mon Mar 24 23:14:28 2003 (3E8001D4)
bad88000 bad96000 raspppoe raspppoe.sys Mon Mar 24 23:11:37 2003 (3E800129)
baf10000 baf18000 audstub audstub.sys Mon Mar 24 23:09:12 2003 (3E800098)
baf18000 baf1ce80 usbuhci usbuhci.sys Mon Mar 24 23:10:43 2003 (3E8000F3)
bf800000 bf9c7000 win32k win32k.sys Tue Mar 08 00:31:56 2005 (422D62FC)
bf9c7000 bf9cc760 HPW6Akmd HPW6Akmd.dll Thu Feb 10 23:43:03 2000 (38A3BD87)
bff30000 bff4b000 cirrus_bff30000 cirrus.dll Tue Mar 25 01:46:25 2003 (3E802571)
bff60000 bff7b000 RDPDD RDPDD.dll Tue Mar 25 12:12:05 2003 (3E80B815)
bff80000 bff96000 dxg dxg.sys Tue Mar 25 01:46:23 2003 (3E80256F)
f7237000 f7259000 Mup Mup.sys Tue Mar 25 00:55:58 2003 (3E80199E)
f7259000 f729a000 NDIS NDIS.sys Tue Mar 25 00:45:35 2003 (3E80172F)
f729a000 f7337000 Ntfs Ntfs.sys Mon Mar 24 23:40:05 2003 (3E8007D5)
f7337000 f7358000 KSecDD KSecDD.sys Mon Mar 24 23:05:39 2003 (3E7FFFC3)
f7358000 f736e000 CLASSPNP CLASSPNP.SYS Mon Mar 24 23:38:14 2003 (3E800766)
f736e000 f7394000 SCSIPORT SCSIPORT.SYS Tue Mar 25 00:01:25 2003 (3E800CD5)
f7394000 f73b0000 atapi atapi.sys Mon Mar 24 23:04:48 2003 (3E7FFF90)
f73b0000 f73d1000 volsnap volsnap.sys Mon Mar 24 23:05:47 2003 (3E7FFFCB)
f73d1000 f73fb000 dmio dmio.sys Mon Mar 24 23:08:14 2003 (3E80005E)
f73fb000 f7420000 ftdisk ftdisk.sys Mon Mar 24 23:05:26 2003 (3E7FFFB6)
f7420000 f7435000 pci pci.sys Mon Mar 24 23:16:40 2003 (3E800258)
f7435000 f7466000 ACPI ACPI.sys Mon Mar 24 23:16:21 2003 (3E800245)
f7487000 f7490000 WMILIB WMILIB.SYS Mon Mar 24 23:13:00 2003 (3E80017C)
f7497000 f74a6000 isapnp isapnp.sys Mon Mar 24 23:16:35 2003 (3E800253)
f74a7000 f74b4000 PCIIDEX PCIIDEX.SYS Mon Mar 24 23:04:44 2003 (3E7FFF8C)
f74b7000 f74c6000 MountMgr MountMgr.sys Mon Mar 24 23:03:05 2003 (3E7FFF29)
f74c7000 f74d5000 PartMgr PartMgr.sys Tue Mar 25 00:04:02 2003 (3E800D72)
f74d7000 f74e1000 mraid35x mraid35x.sys Mon Mar 24 23:05:06 2003 (3E7FFFA2)
f74e7000 f74f6000 disk disk.sys Mon Mar 24 23:05:20 2003 (3E7FFFB0)
f74f7000 f7503000 Dfs Dfs.sys Mon Mar 24 23:09:52 2003 (3E8000C0)
f7507000 f7510000 crcdisk crcdisk.sys Mon Mar 24 23:07:23 2003 (3E80002B)
f7547000 f7553000 Npfs Npfs.SYS Mon Mar 24 23:08:59 2003 (3E80008B)
f7567000 f7573000 processr processr.sys Mon Mar 24 23:07:36 2003 (3E800038)
f7577000 f7580000 watchdog watchdog.sys Mon Mar 24 23:09:01 2003 (3E80008D)
f7587000 f7591000 kbdclass kbdclass.sys Mon Mar 24 23:03:10 2003 (3E7FFF2E)
f7597000 f75a1000 mouclass mouclass.sys Mon Mar 24 23:03:09 2003 (3E7FFF2D)
f75a7000 f75b2000 fdc fdc.sys Mon Mar 24 23:04:31 2003 (3E7FFF7F)
f75b7000 f75c1000 serenum serenum.sys Mon Mar 24 23:04:01 2003 (3E7FFF61)
f75c7000 f75d0000 ndistapi ndistapi.sys Mon Mar 24 23:11:28 2003 (3E800120)
f7707000 f770f000 kdcom kdcom.dll Mon Mar 24 23:08:00 2003 (3E800050)
f770f000 f7717000 BOOTVID BOOTVID.dll Mon Mar 24 23:07:58 2003 (3E80004E)
f7717000 f771e000 intelide intelide.sys Mon Mar 24 23:04:45 2003 (3E7FFF8D)
f771f000 f7726000 dmload dmload.sys Mon Mar 24 23:08:08 2003 (3E800058)
f77f7000 f77ff000 rasacd rasacd.sys Mon Mar 24 23:11:50 2003 (3E800136)
f79c7000 f79c89a0 mmcdev mmcdev.sys Wed Apr 24 22:22:29 2002 (3CC79295)
f79ff000 f7a00200 swenum swenum.sys Mon Mar 24 23:03:22 2003 (3E7FFF3A)
f7a03000 f7a04580 USBD USBD.SYS Mon Mar 24 23:10:39 2003 (3E8000EF)

Unloaded modules:
ba5df000 ba5ed000 imapi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b879e000 b87aa000 vga.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
baf48000 baf50000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000

 

Server just dumped again any help would be greatly appreciated

Debug of minidump file
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\print-1\Mini060105-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 3790.srv03_gdr.050225-1827
Kernel base = 0x804de000 PsLoadedModuleList = 0x8057b6a8
Debug session time: Wed Jun 1 08:38:55.527 2005 (GMT-7)
System Uptime: 5 days 16:37:27.328
Loading Kernel Symbols
........................................................................................................
Loading unloaded module list
.........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {e4082518, 0, bf943846, 1}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!vTransparentCopy+f5 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e4082518, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf943846, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: e4082518

FAULTING_IP:
win32k!vTransparentCopy+f5
bf943846 221a and bl,[edx]

MM_INTERNAL_CODE: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR: 0x50

CURRENT_IRQL: 1

LAST_CONTROL_TRANSFER: from bf8c9d6f to bf943846

TRAP_FRAME: b085d8e8 -- (.trap ffffffffb085d8e8)
ErrCode = 00000000
eax=00000006 ebx=e4089efc ecx=00000000 edx=e4082518 esi=b085db0c edi=e4082518
eip=bf943846 esp=b085d95c ebp=b085d9a0 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
win32k!vTransparentCopy+0xf5:
bf943846 221a and bl,[edx] ds:0023:e4082518=??
Resetting default scope

STACK_TEXT:
b085d9a0 bf8c9d6f b085db0c e16e71e0 b085dd10 win32k!vTransparentCopy+0xf5
b085dbc4 bf8ca56c e4089e10 e4d2c4c8 b085dbf8 win32k!EngTransparentBlt+0x2ef
b085dd30 804dfd24 e1ac12b0 e4089e10 e31bdef8 win32k!NtGdiTransparentBlt+0x702
b085dd30 7ffe0304 e1ac12b0 e4089e10 e31bdef8 nt!KiSystemService+0xd0
04b8f1dc 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4


FOLLOWUP_IP:
win32k!vTransparentCopy+f5
bf943846 221a and bl,[edx]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!vTransparentCopy+f5

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 422d62fc

STACK_COMMAND: .trap ffffffffb085d8e8 ; kb

FAILURE_BUCKET_ID: 0x50_win32k!vTransparentCopy+f5

BUCKET_ID: 0x50_win32k!vTransparentCopy+f5

Followup: MachineOwner

 

Debug from Memory.dmp file

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


Loading Dump File [C:\print-1\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 3790.srv03_gdr.050225-1827
Kernel base = 0x804de000 PsLoadedModuleList = 0x8057b6a8
Debug session time: Wed Jun 1 08:38:55.527 2005 (GMT-7)
System Uptime: 5 days 16:37:27.328
Loading Kernel Symbols
........................................................................................................
Loading unloaded module list
.........
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffdf00c). Type ".hh dbgerr001" for details
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {e4082518, 0, bf943846, 1}

Probably caused by : win32k.sys ( win32k!vTransparentCopy+f5 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e4082518, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf943846, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)

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


READ_ADDRESS: e4082518 Paged pool

FAULTING_IP:
win32k!vTransparentCopy+f5
bf943846 221a and bl,[edx]

MM_INTERNAL_CODE: 1

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 422d62fc

MODULE_NAME: win32k

FAULTING_MODULE: bf800000 win32k

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

CURRENT_IRQL: 1

LAST_CONTROL_TRANSFER: from bf8c9d6f to bf943846

TRAP_FRAME: b085d8e8 -- (.trap ffffffffb085d8e8)
ErrCode = 00000000
eax=00000006 ebx=e4089efc ecx=00000000 edx=e4082518 esi=b085db0c edi=e4082518
eip=bf943846 esp=b085d95c ebp=b085d9a0 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
win32k!vTransparentCopy+0xf5:
bf943846 221a and bl,[edx] ds:0023:e4082518=??
Resetting default scope

STACK_TEXT:
b085d9a0 bf8c9d6f b085db0c e16e71e0 b085dd10 win32k!vTransparentCopy+0xf5
b085dbc4 bf8ca56c e4089e10 e4d2c4c8 b085dbf8 win32k!EngTransparentBlt+0x2ef
b085dd30 804dfd24 e1ac12b0 e4089e10 e31bdef8 win32k!NtGdiTransparentBlt+0x702
b085dd30 7ffe0304 e1ac12b0 e4089e10 e31bdef8 nt!KiSystemService+0xd0
04b8f1dc 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4


FOLLOWUP_IP:
win32k!vTransparentCopy+f5
bf943846 221a and bl,[edx]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!vTransparentCopy+f5

STACK_COMMAND: .trap ffffffffb085d8e8 ; kb

FAILURE_BUCKET_ID: 0x50_win32k!vTransparentCopy+f5

BUCKET_ID: 0x50_win32k!vTransparentCopy+f5

Followup: MachineOwner

 

One word. WOW!

I dont think I could come up with 490 printers with all of my clients combined along with the stores in this town selling them.

Tell your boss to quit killing trees and go paperless.

 

studerje - sorry to say I can't unravel one of those dump files to give you 'the answer'. I can't even say for sure what switches you need to use to create a file that gives more info.

I am about 99% sure that your problem is being caused by a print driver that is behaving badly.

If you have a limited number of different printers, it might be worth downloading new drivers and updating all of them. If you are in the situation that most of us find with almost as many different printers as the total number of devices, it might be worth opening a case with Microsoft Product Support. They can direct you to create a dump file that will allow them to tell you exactly which driver is at fault.

 

Hi!

You could try to run verifier on the suspicious drivers (divide them into groups and run each group at a time if you have as many drivers as printers). Turn on everything except "low resource simulation ". Do this until you find the driver that crashes. Unfortunately it could well be that other drivers crashes as well, but with a bit of luck...

Regards Pelle

 

This dump will need to be analyzed by microsoft product services to determine if thats blown pool or a bad bitmap. From the looks of the repeatability, one of the drivers you have doesnt like transparent bitblting.


Before you do that, remove this version-2 driver for the HP2000/2500 from the machine and see if it doesnt just go away. Do *NOT* allow version 2 drivers on a big dog print server.

HPW6Akmd.dll Thu Feb 10 23:43:03 2000 (38A3BD87)

You should also remove all third party language and port monitors as a preemptive step.