Frequent BSODs in CS:CZ, page fault

[bheatlp]

Hi,
Stumbled upon this forum when researching a frequent BSOD which occurs when playing Counter-strike:Condition Zero. The BSOD originally showed up as a page_fault_in_nonpage_area caused by win32k.sys. When crashing the sound locks up, display goes bad and then displays the BSOD.

After researching this problem some measures were taken to resolve the issue by updating drivers, which initially was quite promising with no crash, but after half an hour or so a new BSOD occured, this time the page_fault_in_nonpaged_area is said to be caused by Dnetr28u.sys, which should be associated with my Wifi USB adapter from D-Link.

Memory tests have been run (Memtest 86 and windows own, not that extended tests though) and shows no errors.


My system:

Windows Vista SP1
Gigabyte 790FX-DS5
North Bridge: AMD 790FX
South Bridge: AMD SB600
Realtek ALC889A codec (AUDIO)
Realtek 8111B chip (LAN)

Athlon 64 X2 6400+
2x 160gb hard-drives running in mirrored RAID,
D-Link DWA-140 Rangebooster Wifi USB adapter (latest driver)
Sapphire HD3870 Graphics card (latest catalyst)

When trying to update the system drivers through the gigabyte home page there seems to be a problem installing the "north bridge filter driver", this one comes up as not being of the current version when the install manager analyzes the system after installing the same driver...



And the debugged crash dump:

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: aa101ea8, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 951361c4, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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

Page a9b16 not present in the dump file. Type ".hh dbgerr004" for details

READ_ADDRESS: aa101ea8

FAULTING_IP:
Dnetr28u+51c4
951361c4 8b9544ffffff mov edx,dword ptr [ebp-0BCh]

MM_INTERNAL_CODE: 0

IMAGE_NAME: Dnetr28u.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a7651c8

MODULE_NAME: Dnetr28u

FAULTING_MODULE: 95131000 Dnetr28u

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: hl.exe

CURRENT_IRQL: 0

TRAP_FRAME: aa121c64 -- (.trap 0xffffffffaa121c64)
ErrCode = 00000000
eax=86f6c5b8 ebx=95149790 ecx=00000000 edx=00000002 esi=86dbf0e8 edi=826b7000
eip=951361c4 esp=aa121cd8 ebp=aa101f64 iopl=0 nv up ei ng nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010296
Dnetr28u+0x51c4:
951361c4 8b9544ffffff mov edx,dword ptr [ebp-0BCh] ss:0010:aa101ea8=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 82092bf4 to 820dd195

STACK_TEXT:
aa121c4c 82092bf4 00000000 aa101ea8 00000000 nt!MmAccessFault+0x10a
aa121c4c 951361c4 00000000 aa101ea8 00000000 nt!KiTrap0E+0xdc
WARNING: Stack unwind information not available. Following frames may be wrong.
aa121d3c 8200c5b0 000001ff 82170102 aa121da4 Dnetr28u+0x51c4
aa121d4c 8680fadc 8680f0e8 82130902 00000002 hal!KfLowerIrql+0x64
aa121db0 8200c50c 8680fd02 00000000 8680f0e0 0x8680fadc
aa121dcc 8200c5b0 00000000 8680fd00 aa121dec hal!HalpCheckForSoftwareInterrupt+0x64
aa121ddc 82008f6b 9477a133 8680f0e8 aa121e08 hal!KfLowerIrql+0x64
aa121de0 9477a133 8680f0e8 aa121e08 94783f84 hal!KfReleaseSpinLock+0xb
aa121dec 94783f84 8680f028 8680dd00 8680dd98 USBPORT!USBPORT_ReleaseEpListLock+0x36
aa121e08 820517d6 2d4c7874 80004188 2c012400 USBPORT!USBPORT_TxCsqReleaseLock+0x83
aa121e2c 94dca7b5 00000000 00000002 0000001a nt!IoCsqInsertIrpEx+0x57
aa121f08 94dc889c 00000000 00000000 016b7000 fsdfw+0x37b5
aa121f64 951326c5 86e82000 86204298 86e82001 fsdfw+0x189c
aa121fe0 951499c7 86e82000 00000000 86a30ad0 Dnetr28u+0x16c5
aa122018 8274b5c4 86e82000 85b7ac98 00000000 Dnetr28u+0x189c7
aa122040 82680585 86dbf0e8 85b7ac98 00000000 ndis!ndisMSendNBLToMiniport+0xb4
aa122060 826805a8 85b7ac98 85b7ac98 00000000 ndis!ndisFilterSendNetBufferLists+0x8b
aa122078 9551b263 85afa008 85b7ac98 00000000 ndis!NdisFSendNetBufferLists+0x18
aa1220a8 9551b475 00000001 aa12224c aa12214c nwifi!Dot11OnDisassociate+0x183
aa122250 9551ebf4 87672008 86a30ad0 87672008 nwifi!Dot11FlushIntermediateSendQueue+0x85
aa122274 9551ec67 00000000 00000000 87673808 nwifi!MP6SendNBLInternal+0xe4
aa12228c 95521c13 87672008 86a30ad0 00000000 nwifi!MP6Send+0x67
aa1222a4 82680585 85afb010 86a30ad0 00000000 nwifi!FilterSendNetBufferLists+0x19
aa1222c4 826805a8 86a30ad0 86a30ad0 00000000 ndis!ndisFilterSendNetBufferLists+0x8b
aa1222dc 94d513c2 87673808 86a30ad0 00000000 ndis!NdisFSendNetBufferLists+0x18
aa1222fc 82680585 876735e8 86a30ad0 00000000 anodlwf+0x13c2
aa12231c 826805a8 86a30ad0 86a30ad0 00000000 ndis!ndisFilterSendNetBufferLists+0x8b
aa122334 94d3f4ab 873a0c10 86a30ad0 00000000 ndis!NdisFSendNetBufferLists+0x18
aa1223b0 82680638 8739e9f0 86a30ad0 00000000 pacer!PcFilterSendNetBufferLists+0x233
aa1223cc 8274b64a 86a30ad0 86a30ad0 00000000 ndis!ndisSendNBLToFilter+0x87
aa1223f0 82c624ce 87787488 86a30ad0 00000000 ndis!NdisSendNetBufferLists+0x4f
aa122438 82c620ac 87787840 00000000 00000000 tcpip!FlSendPackets+0x399
aa122478 82c61cbb 82cc8ca8 00000000 00000000 tcpip!IppFragmentPackets+0x201
aa1224b0 82c63ab6 82cc8ca8 aa1225cc 616c7049 tcpip!IppDispatchSendPacketHelper+0x252
aa122550 82c62f2a 001225cc aa122710 85f01e88 tcpip!IppPacketizeDatagrams+0x8fd
aa1226b0 82c5bf9e 00000000 00000004 82cc8ca8 tcpip!IppSendDatagramsCommon+0x604
aa1226d0 82c50e1b 8593f250 aa1226e8 8593f250 tcpip!IpNlpSendDatagrams+0x4b
aa122758 82c42449 8593f250 aa122970 85f01e88 tcpip!IppSlowSendDatagram+0x31
aa1227b4 82c5cd56 8593f250 00000000 aa122970 tcpip!IpNlpFastSendDatagram+0x47f
aa122a00 94cc182f 85ca86a8 859508d8 85695f80 tcpip!UdpSendMessages+0xb50
aa122a18 94cdef80 8573b8b8 aa122a30 8573b8b8 afd!AfdTLSendMessages+0x27
aa122a68 94cded87 8573b8b8 85695f80 3edf0c67 afd!AfdTLFastDgramSend+0x7d
aa122ae4 94cd43d0 8573b8b8 aa122b7c 00000026 afd!AfdFastDatagramSend+0x5ac
aa122c58 82284ac0 85792a01 00000001 0012d880 afd!AfdFastIoDeviceControl+0x3c1
aa122d00 8226eb4d 873969b0 000001b4 00000000 nt!IopXxxControlFile+0x2cf
aa122d34 8208fa9a 00000868 000001b4 00000000 nt!NtDeviceIoControlFile+0x2a
aa122d34 779f9a94 00000868 000001b4 00000000 nt!KiFastCallEntry+0x12a
0012d938 00000000 00000000 00000000 00000000 0x779f9a94


STACK_COMMAND: kb

FOLLOWUP_IP:
Dnetr28u+51c4
951361c4 8b9544ffffff mov edx,dword ptr [ebp-0BCh]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: Dnetr28u+51c4

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x50_Dnetr28u+51c4

BUCKET_ID: 0x50_Dnetr28u+51c4

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

 

[bheatlp]

Updated chkdsk

Update: Ran check disk, and this is what it returned, nothing critical from what I can understand atleast.

Windows will now check the disk.
253760 file records processed. 1117 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. 312692 index entries processed. 0 unindexed files processed. 253760 security descriptors processed. Cleaning up 5984 unused index entries from index $SII of file 0x9.
Cleaning up 5984 unused index entries from index $SDH of file 0x9.
Cleaning up 5984 unused security descriptors.
29467 data files processed. CHKDSK is verifying Usn Journal...
33841240 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
253744 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
12634413 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

156268543 KB total disk space.
105240324 KB in 220102 files.
122004 KB in 29468 indexes.
0 KB in bad sectors.
368559 KB in use by the system.
65536 KB occupied by the log file.
50537656 KB available on disk.

4096 bytes in each allocation unit.
39067135 total allocation units on disk.
12634414 allocation units available on disk.

 

[bheatlp]

Update:

Attached some minidumps.

 

[Route44]

One out of five dumps cited the D-Link wireless adapter driver Dnetr28u.sys as the cause of your issues. This driver is also a part of the Ralink wireless drivers as well.

Update your wireless drivers again but if that doesn't resolve your issues then it could be the wireless card is faulty.