BSODs after installing HD 6770

Two crashes after verifier was enabled. Verifier still enabled.

Was problem free for a few days and just had a crash occur today, while it was idle, streaming online radio. Verifier is still enabled.

Not sure what happened to zigzag but still getting BSOD's. Attached is my latest 2 minidumps. Uninstalled DAEMON tools lite and the AMD catalyst control center but left all the other portions of the catalyst software suite. Driver verifer still enabled.

Any other guru willing to help anaylze?

Thanks

flameboy54 said:

Not sure what happened to zigzag but still getting BSOD's. Attached is my latest 2 minidumps. Uninstalled DAEMON tools lite and the AMD catalyst control center but left all the other portions of the catalyst software suite. Driver verifer still enabled.

Any other guru willing to help anaylze?

Thanks

Two of 4 were inconclusive. One was your directX and one was an OS file. If the ram is ok then it must be a driver. It may be timne to start thinking about a re-install (clean)

Thanks for the reply. In regards to the ram, my results from memtest showed that there were some errors:

RAM 1/slot 1: 6 passes, 0 errors
RAM 1/slot 2: 10 passes, 0 errors
RAM 2/slot 1: 17 passes, 10 errors
RAM 2/slot 2: 8 passes, 0 errors

Is it safe to say that despite the errors, the problem at hand is leaning more towards the OS instead of the ram?

I'm guessing a repair install (Repair Install - Windows 7 Forums) isn't suffice to fix the problem?

Just after I posted my last post I re-installed directX 11 and re-named sptd.sys to .bak just as a precautionary move. I'll see how that goes. I'll prep myself for a fresh install in the meantime.

Thanks for you help up to this point, it's much appreciated.

10 errors in 17 passes is probably OK. You will never stress your computer that much

I am indeed leaning towards the OS or 3rd party drivers.

A repair install may fix it and might be worth the effort but were it mine I would do a clean install.

You may have fixed it with your changes so lets wait and see.

Was starting to backing up all my data for a new install and got bombarded with BSOD's. Figured it was no use posting the mini dump files and I just proceed to backup and do a fresh install. After the installation I moved on to the motherboard drivers (chipset, LAN and audio), BIOS update (2603) and the 6770 drivers (Catalyst Software Suite 12.4), all from the manufactures websites. Installed MSE, Updated Windows via Windows Update where 80 updates were installed. This morning, as I was opening IE, I got a BSOD. Not sure if you want to see the minidump files or if you want to let it accumulate before analyzing.

In the meantime I'll proceed with updating Windows til its completely updated.

Opted to post the minidump files anyways. Also ran whocrashed since I've never played with it before. Here's the report:

Crash Dump Analysis
</B>
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 08/05/2012 2:35:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050812-29265-01.dmp
uptime: 00:08:00
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFF80000AAFB50, 0x8, 0xFFFFF80000AAFB50, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 08/05/2012 2:35:40 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:08:00
This was probably caused by the following module: afd.sys (afd+0x2C1F2)
Bugcheck code: 0x50 (0xFFFFF80000AAFB50, 0x8, 0xFFFFF80000AAFB50, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.



Conclusion
</B>
2 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

=============================================

EDIT: Just so happened after I posted this reply I got a BSOD. I've updated the attached zip with both the minidump files from this morning and a few minutes ago.

flameboy54 said:

Opted to post the minidump files anyways. Also ran whocrashed since I've never played with it before. Here's the report:

Crash Dump Analysis
</B>
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 08/05/2012 2:35:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050812-29265-01.dmp
uptime: 00:08:00
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFF80000AAFB50, 0x8, 0xFFFFF80000AAFB50, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 08/05/2012 2:35:40 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:08:00
This was probably caused by the following module: afd.sys (afd+0x2C1F2)
Bugcheck code: 0x50 (0xFFFFF80000AAFB50, 0x8, 0xFFFFF80000AAFB50, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.



Conclusion
</B>
2 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

=============================================

EDIT: Just so happened after I posted this reply I got a BSOD. I've updated the attached zip with both the minidump files from this morning and a few minutes ago.

Related to L1E62x64.sys Ethernet Controller(NDIS6.20) from Atheros Communications, Inc. Yours is from 2009. I would update it to the newest available.

I am a big fan of Nir Sofer's work, BUT blueScreenView more often than not, doesn't point out the correct causes. Similarly Who crashed is even worse.

I prefer to use WinDbg (the Windows Debugging Tools) to read the memory dumps. It is the Gold standard for those of us that do this and often will give us the answer by itself. (we don't need the full jcgriff2 report each time).

Thanks of for the tip.

I downloaded the latest L1E62x64.sys (29/3/2010) file from the Qualicomm website and updated the ethernet drivers via device manager but noticed the file in the system32/drivers folder was still dated 2009 so I manually copy and pasted it. Keep you posted on any BSOD's. Thanks again.