Driver Error Problems

I honestly do not think this is a driver error. For one thing, most of your drivers are several years old. The only updates have been to minor components by Windows Update.

Nor do I think as a gut instinct this is faulty RAM.

I think you are looking at a new motherboard.

At the least for now, take the case apart, remove all adapter boards, and thoroughly clean everything. All heatsinks, fan cases, adapter slots, everything.

Re-assemble.

But I strongly suspect a failing motherboard. This can be anything from leaking capacitors to just about any component.

If you have additional Dumps stored, please try another recent one and post the results back.

 

After doing a Google search I am wondering the same thing. I am going to see if I can find any bulging or leaking capacitors.

My board is an MSI MS-6738. At one time MSI was having problems with bad capacitors.

Thanks for your help Bill.

I'll post more reports if possible.

 

Followup note...

If I have a failing board...Why are most of my problems associated with hibernation/ standby/ coldstart issues? I rarely see a BSOD after the desktop appears.

(Wished my 500th post would have been for an easier problem, lol.)

 

One indication of a pure hardware issue would be the fact that it works relatively okay when warm, and terribly when cold.

So at the moment your danger periods would be: cold start, hibernation start, or stand-by start.

A hardware issue such as bad capacitors could easily work this way. As could other pure hardware issues. One thing that you can be certain of is that the failures will become increasingly more common over time. Cold or Warm.

Your debug log does not suggest a driver issue, or bad RAM.

You might ping Forum member cpc2004 for a second, and quite frankly, more experienced opinion.

 

Hi James,

Your debug report shows that the crash is caused by CPU_CALL_ERROR. Usually it is caused by faulty Motherboard, video card or CPU. I have 4 cases relating to m/b, 1 case is related to video card and 1 case is related to CPU. You had better check the motherboard.

Problem of faulty motherboard
http://www.experts-exchange.com/Operating_Systems/WinXP/Q_21236265.html
http://www.techspot.com/vb/topic32555.html

 

cpc2004,

Thanks for the look and opinion.

Best,
Bill

 

Yes, thanks again cpc2004.

 

Another Log...

This seems to be driver related...

(I could have sworn that I posted this report earlier )

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini010307-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: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Wed Jan 3 11:32:55.531 2007 (GMT-5)
System Uptime: 0 days 11:01:56.111
Loading Kernel Symbols
................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000C5, {4, 2, 1, 8054ae34}

Probably caused by : ntoskrnl.exe ( nt!ExAllocatePoolWithTag+673 )

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

kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8054ae34, address which referenced memory

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


BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExAllocatePoolWithTag+673
8054ae34 897104 mov dword ptr [ecx+4],esi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: winlogon.exe

LAST_CONTROL_TRANSFER: from 80568995 to 8054ae34

STACK_TEXT:
f4ba6c10 80568995 00000000 00000001 53646156 nt!ExAllocatePoolWithTag+0x673
f4ba6d44 804de7ec ffffffff 0006f41c 00000000 nt!NtAllocateVirtualMemory+0xc0b
f4ba6d44 7c90eb94 ffffffff 0006f41c 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0006f420 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExAllocatePoolWithTag+673
8054ae34 897104 mov dword ptr [ecx+4],esi

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExAllocatePoolWithTag+673

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9

FAILURE_BUCKET_ID: 0xC5_2_nt!ExAllocatePoolWithTag+673

BUCKET_ID: 0xC5_2_nt!ExAllocatePoolWithTag+673

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

eax=815f40a0 ebx=80561940 ecx=00000000 edx=00000004 esi=80561988 edi=000001ff
eip=8054ae34 esp=f4ba6bbc ebp=f4ba6c10 iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010216
nt!ExAllocatePoolWithTag+0x673:
8054ae34 897104 mov dword ptr [ecx+4],esi ds:0023:00000004=????????
ChildEBP RetAddr Args to Child
f4ba6c10 80568995 00000000 00000001 53646156 nt!ExAllocatePoolWithTag+0x673 (FPO: [Non-Fpo])
f4ba6d44 804de7ec ffffffff 0006f41c 00000000 nt!NtAllocateVirtualMemory+0xc0b (FPO: [Non-Fpo])
f4ba6d44 7c90eb94 ffffffff 0006f41c 00000000 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ f4ba6d64)
WARNING: Frame IP not in any known module. Following frames may be wrong.
0006f420 00000000 00000000 00000000 00000000 0x7c90eb94
start end module name
804d7000 806eb100 nt ntoskrnl.exe Tue Mar 01 19:59:37 2005 (42250FF9)
806ec000 8070c380 hal halaacpi.dll Wed Aug 04 01:59:05 2004 (41107B29)
bf000000 bf011580 dxg dxg.sys Wed Aug 04 02:00:51 2004 (41107B93)
bf012000 bf074280 s3gnb s3gnb.dll Tue Mar 02 01:02:24 2004 (40442370)
bf800000 bf9c1180 win32k win32k.sys Wed Oct 05 20:05:44 2005 (43446A58)
f1444000 f146e180 kmixer kmixer.sys Wed Jun 14 04:47:45 2006 (448FCD31)
f19e3000 f19e6800 asyncmac asyncmac.sys Wed Aug 04 02:05:02 2004 (41107C8E)
f1a0f000 f1a4f280 HTTP HTTP.sys Thu Mar 16 19:33:09 2006 (441A03C5)
f1c80000 f1cd1480 srv srv.sys Mon Aug 14 06:34:39 2006 (44E051BF)
f20ba000 f20ce400 wdmaud wdmaud.sys Wed Jun 14 05:00:44 2006 (448FD03C)
f2137000 f2145d80 sysaudio sysaudio.sys Wed Aug 04 02:15:54 2004 (41107F1A)
f21bf000 f21eb400 mrxdav mrxdav.sys Wed Aug 04 02:00:49 2004 (41107B91)
f2200000 f22026c0 mdmxsdk mdmxsdk.sys Wed Apr 09 16:48:53 2003 (3E948735)
f234c000 f234eae0 wg3n wg3n.sys Sat May 03 19:00:37 2003 (3EB44A15)
f2380000 f2383280 ndisuio ndisuio.sys Wed Aug 04 02:03:10 2004 (41107C1E)
f4ab4000 f4acb480 dump_atapi dump_atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f4acc000 f4aef000 Fastfat Fastfat.SYS Wed Aug 04 02:14:15 2004 (41107EB7)
f4bb7000 f4c7e620 avg7core avg7core.sys Mon Oct 23 14:52:56 2006 (453D0F88)
f4c7f000 f4ceda00 mrxsmb mrxsmb.sys Fri May 05 05:41:42 2006 (445B1DD6)
f4cee000 f4d18a00 rdbss rdbss.sys Fri May 05 05:47:55 2006 (445B1F4B)
f4d19000 f4d3ad00 afd afd.sys Wed Aug 04 02:14:13 2004 (41107EB5)
f4d3b000 f4d62c00 netbt netbt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f4d63000 f4d83f00 ipnat ipnat.sys Wed Sep 29 18:28:36 2004 (415B3714)
f4d84000 f4ddbd80 tcpip tcpip.sys Thu Apr 20 07:51:47 2006 (444775D3)
f4ddc000 f4dee400 ipsec ipsec.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f6e8b000 f6e8d900 Dxapi Dxapi.sys Fri Aug 17 16:53:19 2001 (3B7D843F)
f6f2f000 f6f3e900 Cdfs Cdfs.SYS Wed Aug 04 02:14:09 2004 (41107EB1)
f6f4f000 f6f82200 update update.sys Wed Aug 04 01:58:32 2004 (41107B08)
f6f83000 f6f93e00 psched psched.sys Wed Aug 04 02:04:16 2004 (41107C60)
f6f9c000 f6f9e580 hidusb hidusb.sys Fri Aug 17 17:02:16 2001 (3B7D8658)
f6fbc000 f6fd2680 ndiswan ndiswan.sys Wed Aug 04 02:14:30 2004 (41107EC6)
f6fd3000 f6fe6900 parport parport.sys Wed Aug 04 01:59:04 2004 (41107B28)
f6fe7000 f700a980 portcls portcls.sys Wed Aug 04 02:15:47 2004 (41107F13)
f700b000 f73e1a00 ALCXWDM ALCXWDM.SYS Mon Nov 06 03:01:43 2006 (454EEBE7)
f73e2000 f7404680 ks ks.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f7405000 f74d1ac0 winachcf winachcf.sys Sat Jun 07 00:57:23 2003 (3EE170B3)
f74d2000 f74f4f00 USBPORT USBPORT.SYS Tue Oct 25 19:39:41 2005 (435EC23D)
f74f5000 f7508780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 02:07:04 2004 (41107D08)
f7509000 f7531c80 s3gnbm s3gnbm.sys Tue Mar 02 01:02:29 2004 (40442375)
f7542000 f7545f00 MODEMCSA MODEMCSA.sys Fri Aug 17 16:57:37 2001 (3B7D8541)
f757a000 f7594580 Mup Mup.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f7595000 f75b1000 Teefer Teefer.sys Thu Sep 04 19:46:06 2003 (3F57CEBE)
f75b1000 f75dda80 NDIS NDIS.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f75de000 f766a480 Ntfs Ntfs.sys Wed Aug 04 02:15:06 2004 (41107EEA)
f766b000 f7681780 KSecDD KSecDD.sys Wed Aug 04 01:59:45 2004 (41107B51)
f7682000 f7693f00 sr sr.sys Wed Aug 04 02:06:22 2004 (41107CDE)
f7694000 f7695000 fltmgr fltmgr.sys unavailable (00000000)
f76b4000 f76cb800 SCSIPORT SCSIPORT.SYS Wed Aug 04 01:59:39 2004 (41107B4B)
f76cc000 f76e3480 atapi atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f76e4000 f7702880 ftdisk ftdisk.sys Fri Aug 17 16:52:41 2001 (3B7D8419)
f7703000 f7713a80 pci pci.sys Wed Aug 04 02:07:45 2004 (41107D31)
f7714000 f7741d80 ACPI ACPI.sys Wed Aug 04 02:07:35 2004 (41107D27)
f7742000 f7767e00 d347bus d347bus.sys Sun Aug 22 09:31:09 2004 (4128A01D)
f7789000 f7791c00 isapnp isapnp.sys Fri Aug 17 16:58:01 2001 (3B7D8559)
f7799000 f77a3500 MountMgr MountMgr.sys Wed Aug 04 01:58:29 2004 (41107B05)
f77a9000 f77b5c80 VolSnap VolSnap.sys Wed Aug 04 02:00:14 2004 (41107B6E)
f77b9000 f77c1e00 disk disk.sys Wed Aug 04 01:59:53 2004 (41107B59)
f77c9000 f77d5200 CLASSPNP CLASSPNP.SYS Wed Aug 04 02:14:26 2004 (41107EC2)
f77d9000 f77e3500 viaagp viaagp.sys Wed Aug 04 02:07:42 2004 (41107D2E)
f7809000 f7812200 amdk7 amdk7.sys Wed Aug 04 01:59:19 2004 (41107B37)
f7819000 f7823380 imapi imapi.sys Wed Aug 04 02:00:12 2004 (41107B6C)
f7829000 f7835180 cdrom cdrom.sys Wed Aug 04 01:59:52 2004 (41107B58)
f7839000 f7847080 redbook redbook.sys Wed Aug 04 01:59:34 2004 (41107B46)
f7859000 f7867b80 drmk drmk.sys Wed Aug 04 02:07:54 2004 (41107D3A)
f7869000 f7878d80 serial serial.sys Wed Aug 04 02:15:51 2004 (41107F17)
f7879000 f7885e00 i8042prt i8042prt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f7889000 f7895880 rasl2tp rasl2tp.sys Wed Aug 04 02:14:21 2004 (41107EBD)
f7899000 f78a3200 raspppoe raspppoe.sys Wed Aug 04 02:05:06 2004 (41107C92)
f78a9000 f78b4d00 raspptp raspptp.sys Wed Aug 04 02:14:26 2004 (41107EC2)
f78b9000 f78c1900 msgpc msgpc.sys Wed Aug 04 02:04:11 2004 (41107C5B)
f78c9000 f78d2f00 termdd termdd.sys Wed Aug 04 01:58:52 2004 (41107B1C)
f78d9000 f78e2480 NDProxy NDProxy.SYS Fri Aug 17 16:55:30 2001 (3B7D84C2)
f78f9000 f7907100 usbhub usbhub.sys Wed Aug 04 02:08:40 2004 (41107D68)
f7959000 f7961700 wanarp wanarp.sys Wed Aug 04 02:04:57 2004 (41107C89)
f7969000 f7971700 netbios netbios.sys Wed Aug 04 02:03:19 2004 (41107C27)
f7979000 f7981880 Fips Fips.SYS Fri Aug 17 21:31:49 2001 (3B7DC585)
f7999000 f79a1d80 HIDCLASS HIDCLASS.SYS Wed Aug 04 02:08:18 2004 (41107D52)
f7a09000 f7a0f200 PCIIDEX PCIIDEX.SYS Wed Aug 04 01:59:40 2004 (41107B4C)
f7a11000 f7a15900 PartMgr PartMgr.sys Fri Aug 17 21:32:23 2001 (3B7DC5A7)
f7a19000 f7a1fd00 viaagp1 viaagp1.sys Wed Jul 02 06:08:01 2003 (3F02AF01)
f7a41000 f7a45280 usbohci usbohci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f7a49000 f7a4ff00 avg7rsxp avg7rsxp.sys Mon Jun 19 04:21:28 2006 (44965E88)
f7a51000 f7a57a80 usbehci usbehci.sys Tue Oct 25 19:39:41 2005 (435EC23D)
f7a69000 f7a70580 Modem Modem.SYS Wed Aug 04 02:08:04 2004 (41107D44)
f7a71000 f7a76000 usbuhci usbuhci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f7a79000 f7a7f500 usbprint usbprint.sys Wed Aug 04 02:01:23 2004 (41107BB3)
f7a99000 f7a9fb00 fdc fdc.sys Wed Aug 04 01:59:25 2004 (41107B3D)
f7aa9000 f7aaf000 kbdclass kbdclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7ab1000 f7ab5500 watchdog watchdog.sys Wed Aug 04 02:07:32 2004 (41107D24)
f7ac9000 f7acd880 TDI TDI.SYS Wed Aug 04 02:07:47 2004 (41107D33)
f7ad9000 f7add580 ptilink ptilink.sys Fri Aug 17 16:49:53 2001 (3B7D8371)
f7ae9000 f7aed080 raspti raspti.sys Fri Aug 17 16:55:32 2001 (3B7D84C4)
f7af1000 f7af6a00 mouclass mouclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7b09000 f7b0e000 flpydisk flpydisk.sys Wed Aug 04 01:59:24 2004 (41107B3C)
f7b21000 f7b26200 vga vga.sys Wed Aug 04 02:07:06 2004 (41107D0A)
f7b31000 f7b35a80 Msfs Msfs.SYS Wed Aug 04 02:00:37 2004 (41107B85)
f7b41000 f7b48880 Npfs Npfs.SYS Wed Aug 04 02:00:38 2004 (41107B86)
f7b59000 f7b61000 wpsdrvnt wpsdrvnt.sys Thu Sep 04 19:48:13 2003 (3F57CF3D)
f7b69000 f7b6f780 USBSTOR USBSTOR.SYS Wed Aug 04 02:08:44 2004 (41107D6C)
f7b91000 f7b97180 HIDPARSE HIDPARSE.SYS Wed Aug 04 02:08:15 2004 (41107D4F)
f7b99000 f7b9c000 BOOTVID BOOTVID.dll Fri Aug 17 16:49:09 2001 (3B7D8345)
f7b9d000 f7b9f480 compbatt compbatt.sys Fri Aug 17 16:57:58 2001 (3B7D8556)
f7ba1000 f7ba4700 BATTC BATTC.SYS Fri Aug 17 16:57:52 2001 (3B7D8550)
f7c49000 f7c4cc80 serenum serenum.sys Wed Aug 04 01:59:06 2004 (41107B2A)
f7c51000 f7c53280 rasacd rasacd.sys Fri Aug 17 16:55:39 2001 (3B7D84CB)
f7c55000 f7c57580 ndistapi ndistapi.sys Fri Aug 17 16:55:29 2001 (3B7D84C1)
f7c65000 f7c67f80 mouhid mouhid.sys Fri Aug 17 16:47:57 2001 (3B7D82FD)
f7c69000 f7c6cc80 mssmbios mssmbios.sys Wed Aug 04 02:07:47 2004 (41107D33)
f7c89000 f7c8ab80 kdcom kdcom.dll Fri Aug 17 16:49:10 2001 (3B7D8346)
f7c8b000 f7c8c100 WMILIB WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7c8d000 f7c8e500 viaide viaide.sys Wed Aug 04 01:59:42 2004 (41107B4E)
f7c8f000 f7c90480 d347prt d347prt.sys Sun Aug 22 09:31:48 2004 (4128A044)
f7c95000 f7c96100 swenum swenum.sys Wed Aug 04 01:58:41 2004 (41107B11)
f7c9b000 f7c9c280 USBD USBD.SYS Fri Aug 17 17:02:58 2001 (3B7D8682)
f7cbf000 f7cc0000 Fs_Rec Fs_Rec.SYS unavailable (00000000)
f7cc3000 f7cc4080 Beep Beep.SYS Fri Aug 17 16:47:33 2001 (3B7D82E5)
f7cc7000 f7cc8080 mnmdd mnmdd.SYS Fri Aug 17 16:57:28 2001 (3B7D8538)
f7cc9000 f7cca100 hiber_WMILIB hiber_WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7ccb000 f7ccc080 RDPCDD RDPCDD.sys Fri Aug 17 16:46:56 2001 (3B7D82C0)
f7cd3000 f7cd4080 avg7rsw avg7rsw.sys Tue Jul 26 08:10:51 2005 (42E6284B)
f7cd7000 f7cd8100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7d15000 f7d16000 ParVdm ParVdm.SYS unavailable (00000000)
f7dde000 f7ddf000 guard guard.sys Thu Sep 28 10:13:31 2006 (451BD88B)
f7e35000 f7e35c00 audstub audstub.sys Fri Aug 17 16:59:40 2001 (3B7D85BC)
f7e83000 f7e84000 Null Null.SYS unavailable (00000000)
f7e86000 f7e86f80 AvgAsCln AvgAsCln.sys Tue Sep 05 12:03:16 2006 (44FD9FC4)
f7e89000 f7e89f80 avgclean avgclean.sys Mon Aug 21 18:55:15 2006 (44EA39D3)
f7e91000 f7e91d00 dxgthk dxgthk.sys Fri Aug 17 16:53:12 2001 (3B7D8438)
f7eb0000 f7eb0860 BANTExt BANTExt.sys Wed May 27 22:43:29 1998 (356CCF51)

Unloaded modules:
f142c000 f1444000 hiber_atapi.
Timestamp: unavailable (00000000)
Checksum: 00000000
f1531000 f155c000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f1531000 f155c000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f17dc000 f1807000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f1edc000 f1f07000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7ed4000 f7ed5000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f225c000 f2269000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f1fa7000 f1fca000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f22cc000 f22da000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7d4b000 f7d4d000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b19000 f7b1e000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7c45000 f7c48000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

Again, I do not see a driver error.

Note this similarity to your first dump:

Dump #1:
LAST_CONTROL_TRANSFER: from 8059270f to 7f8aa2c5

Dump #2:
LAST_CONTROL_TRANSFER: from 80568995 to 8054ae34

This suggests to me that anytime the memory addressing lines are used for the segment containing 805xxxxx, things go haywire.

 

Well, ok Bill...You know more about this area of computing than I do. I was just concerned that maybe there were two problems to take care of.

So then this part below is not directly related to a driver fault, but is one of the possible symptoms of hardware failure?

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8054ae34, address which referenced memory

 

I know it is the use of the word DRIVER that bothers you. You have to take this with a grain of salt.

No driver appears in the db stack. What appears is nt! which is the kernel. Essentially the complaint is that a process (winlogon.exe) attempted to do a read running at IRQL 0 and ignoring the thread dispatcher at IRQL 2. Now winlogon.exe is not a driver to start with. Nor does it have any particular need if it wanted to read from the pagefile not to ask the THREAD SCHEDULER at IRQL2 to issue a new thread for the read.

Without an identified driver, we cannot use Driver Verifier. So the only choice left is to enable special pools and look at all the crashes that will occur and hope a driver name is revealed.

First, lets make sure virtual memory is sound.
Right click My Computer, Properties, Advanced.
Click Virtual Memory.
Select Custom size, and set the Min to 0, and the Max to 0
Click Set.
Click OK.

Reboot. Now it might complain, but that is fine.
Repeat the steps in the Virtual Memory page, but restore your original settings.
Click Set.
Click OK.
Reboot again.

Try just those steps for a few days or until it BSODs again. Submit the debugging session for the new DUMP. Then we will enable Special Pools with some registry changes.

To see where we are going, please read: http://support.microsoft.com/kb/188831/EN-US/