Windows 7 bugcheck 0x7E, action center suggests memtest, but RAM is o

[MagicAndre1981]

I sometimes get freezes the last 2 weeks with my PC. When this happens the monitor picture gets corrupted. I first thought my GPU is damaged, but today I got it again and this time a dump was created. This is the output of WinDbg:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

fffff880`0a621478 fffff800`03407164 nt!KeBugCheckEx
fffff880`0a621480 fffff800`033c6ae5 nt!PspUnhandledExceptionInSystemThread+0x24
fffff880`0a6214c0 fffff800`030c8abc nt! ?? ::NNGAKEGL::`string'+0x227d
fffff880`0a6214f0 fffff800`030c853d nt!_C_specific_handler+0x8c
fffff880`0a621560 fffff800`030c7315 nt!RtlpExecuteHandlerForException+0xd
fffff880`0a621590 fffff800`030d8391 nt!RtlDispatchException+0x415
fffff880`0a621c70 fffff800`0309c382 nt!KiDispatchException+0x135
fffff880`0a622310 fffff800`0309ac8a nt!KiExceptionDispatch+0xc2
fffff880`0a6224f0 fffff880`016df52b nt!KiGeneralProtectionFault+0x10a
fffff880`0a622680 fffff880`016d6f14 ndis!NdisMCreateLog+0x286b
fffff880`0a6226f0 fffff880`0164b095 ndis!NdisMPauseCo}plete+0x4364
fffff880`0a6227a0 fffff880`0164e3b3 ndis!NdisMQueueDpc+0x7f5
fffff880`0a622840 fffff880`0166848f ndis!NdisAllocateNetBufferAndNetBufferList+0x2233
fffff880`0a6228b0 fffff880`0164b728 ndis!riteLock+0x925f
fffff880`0a622a20 fffff880`0164bcc9 ndis!NdisFOidRequestComplete+0x5a8
fffff880`0a622a90 fffff880`04334231 ndis!NdisFOidRequest+0xc9
fffff880`0a622b70 fffff880`016d0582 nm3!NetmonOidRequest+0x109
fffff880`0a622ba0 fffff880`0165043c ndis!NdisMSynchronizeWithInterruptEx+0x842
fffff880`0a622c70 fffff800`030a7011 ndis!NdisAllocateNetBuffer+0x177c
fffff880`0a622cb0 fffff800`0333944e nt!ExpWorkerThread+0x111
fffff880`0a622d40 fffff800`0308e666 nt!PspSystemThreadStartup+0x5a
fffff880`0a622d80 00000000`00000000 nt!KiStartSystemThread+0x16

CHKIMG_EXTENSION: !chkimg -lo 50 -db !ndis
3393 errors : !ndis (fffff88001649048-fffff88001717fe0)

FOLLOWUP_NAME:  memory_corruption

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

so I ran the memory test of Windows 7 and memtest86+ each over 3 hours, but both don't detect any errors.

sfc tells that the ndis.sys is fine on the HDD, chkdsk also doesn't detect any errors. The only thing I see is the Network Monitor driver in version 3.4.2350.0 which is the latest version.

Are there any known issues with Network Monitor? What es can it be if memtest say RAM is fine?

Hardware:

AMD Phenom II X4 945

ASRock 880GXH/USB3 motherboard

8 GB Crucial DDR3 1333MHz RAM CL9

Radeon HD 5770

1TB Samsung F3 HDD

Edited August 9, 2011 by MagicAndre1981

[allen2]

I'd check if it happen only with this system as MS KB list about 10 articles and most comes with post sp1 hotfix for those crash (none network related) then you'll know if it's really hardware related. I don't have another system you could the hotfixes but sometimes it only make things worse they're only lightly tested.

Also ndis.sys crash debug might be the effect and not the cause => sometime poorly made network drivers come with memory leaks or there was an error and it was ndis.sys this time but might affect another driver next time.

I'll also try setting bios settings to default if possible and at least those memory related.

Edited August 9, 2011 by allen2

[MagicAndre1981]

which KBs?

the drivers are up to date and if chkimg detects errors, the file in the RAM differs from the file from the Symbol server. So the file is corrupted. Now I need to know what corrupts the driver in the RAM becasue the file on the HDD is fine.

[cluberti]

Is that a complete dump? If so, can it be zipped and uploaded somewhere? That particular function (NdisMCreateLog) takes a handle as it's OUT, so if the handle being NULL is the reason for the crash (and it may very well be, given it's a GPF) then there could indeed be a problem with the miniport that called the API (which in this case would be nm3). It's also possible the buffer size allocated isn't large enough, but I haven't seen crashes due to that in quite literally many, many years.

[MagicAndre1981]

I have a complete dump which I compress now and upload.

Currently I have disabled the network monitor driver for my WLAN connection. The crashes only happened when I was browsing the WWW with this WLAN connection.

[MagicAndre1981]

I think it was caused by the ASRock IES feature. I disabled the feature, selected the balanced powerplan of Windows 7 and now I have no issues for 1 week. Looks like my CPu has issues with the 2 reduced phases at low load.