Win7 x64 Random BSOD's, different bugcheck codes

Did you also check the compatibility of your motherboard for your graphics card and cpu ?

The config is fine. (detailed in 1st post!)

I have another crash dump (attached) with similar stack to the previous dump.
Verifier still running on all non microsot drivers, even though no sign of that is to be found in the dump.
The last crash blamed afd.sys while this one has tcpip.sys as the probable cause; both windows components from what i understand and both related to networking.
The other thing that looks suspicious is the Realtek LAN driver involvement in both stacks. (Rt64win7)
Culd this be it? Shuld i revert to default windows drivers for the network card?
Please take a look at the last 2 dumps. Thx.

aSmith said:

The config is fine. (detailed in 1st post!)

I have another crash dump (attached) with similar stack to the previous dump.
Verifier still running on all non microsot drivers, even though no sign of that is to be found in the dump.
The last crash blamed afd.sys while this one has tcpip.sys as the probable cause; both windows components from what i understand and both related to networking.
The other thing that looks suspicious is the Realtek LAN driver involvement in both stacks. (Rt64win7)
Culd this be it? Shuld i revert to default windows drivers for the network card?
Please take a look at the last 2 dumps. Thx.

Memory corruption probably Related to Rt64win7.sys 8101E/8168/8169 NDIS 6.20 64-bit Driver from Realtek Corporation



These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



Driver verifier

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/Win7 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 "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- 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 wait for 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.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver 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.

aSmith said:

I did run memtest and had no errors, nothing is overclocked and verifier is running!

Didnt remove the realtek driver yet, but had another crash that did not involve it.
Any suggestions?

UPDATE:
I found a newer version of the realtek driver and installed it, but the system is still crashing.
(latest crashdump attached)
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

UPDATE 2:
3rd crashdump file attached

Still memory corruption as you saw and not driver verified.

So is it a driver that is not verified right now, or is driver verifier not working correctly?
What shuld i do? If it's a 3rd party driver, i can try a clean install...

aSmith said:

So is it a driver that is not verified right now, or is driver verifier not working correctly?
What shuld i do? If it's a 3rd party driver, i can try a clean install...

What drivers are you currently verifying? You can check by running verifier /query

Code:

Verified drivers:
Name: amdxata.sys, loads: 1, unloads: 0
Name: serial.sys, loads: 1, unloads: 0
Name: atikmpag.sys, loads: 1, unloads: 0
Name: atikmdag.sys, loads: 1, unloads: 0
Name: rt64win7.sys, loads: 1, unloads: 0
Name: ndis.sys, loads: 1, unloads: 0
Name: wmbenum.sys, loads: 1, unloads: 0
Name: wmxlcore.sys, loads: 1, unloads: 0
Name: rthdmivx.sys, loads: 1, unloads: 0
Name: rtkvhd64.sys, loads: 1, unloads: 0
Name: dump_dumpata.sys, loads: 0, unloads: 0
Name: dump_atapi.sys, loads: 2, unloads: 1
Name: dump_dumpfve.sys, loads: 2, unloads: 1
Name: wmfilter.sys, loads: 1, unloads: 0
Name: lhidfilt.sys, loads: 1, unloads: 0
Name: lmoufilt.sys, loads: 1, unloads: 0
Name: secdrv.sys, loads: 1, unloads: 0

The remaining drivers are all from microsoft.

aSmith said:

Code:

Verified drivers:
Name: amdxata.sys, loads: 1, unloads: 0
Name: serial.sys, loads: 1, unloads: 0
Name: atikmpag.sys, loads: 1, unloads: 0
Name: atikmdag.sys, loads: 1, unloads: 0
Name: rt64win7.sys, loads: 1, unloads: 0
Name: ndis.sys, loads: 1, unloads: 0
Name: wmbenum.sys, loads: 1, unloads: 0
Name: wmxlcore.sys, loads: 1, unloads: 0
Name: rthdmivx.sys, loads: 1, unloads: 0
Name: rtkvhd64.sys, loads: 1, unloads: 0
Name: dump_dumpata.sys, loads: 0, unloads: 0
Name: dump_atapi.sys, loads: 2, unloads: 1
Name: dump_dumpfve.sys, loads: 2, unloads: 1
Name: wmfilter.sys, loads: 1, unloads: 0
Name: lhidfilt.sys, loads: 1, unloads: 0
Name: lmoufilt.sys, loads: 1, unloads: 0
Name: secdrv.sys, loads: 1, unloads: 0

The remaining drivers are all from microsoft.

Newest crash is inconclusive. So we wait.