new install, various BCCs

Oh great ones,
I need some pro help on this one. I recently "upgraded" to 7x64 on this system with a new install on a new hard drive. Mobo and Video have been running fine for months under XP. I also upgraded the RAM, which is now my top suspect. Depending on what you find in the logs, I can swap in the old sticks and see how that goes.

Anyway, it's been kicking out fairly random stop errors that I can't find any pattern to. They generally happen once a day and during different task. I don't even understand half of them (I'm no engineer).

Things I've done:
All drivers up to date
Bios up to date
Windows fully updated
* started driver verifier prior to preparing the attachment, no errors after 2+ hours (will update if/when I get one).

Please guide me, gurus.

Hi,

Yes, Avira should be removed as it is a possible cause

Avira Uninstallation instructions (follow these exactly): Avira Solutions - Knowledge Base Problem Details

Install MS Security Essentials --> http://www.microsoft.com/Security_Essentials/

Then reset the Windows Firewall to its default settings -
START -> type cmd.exe -> right-click -> run as administrator -> type netsh advfirewall reset press enter

Thonnas said:

* started driver verifier prior to preparing the attachment, no errors after 2+ hours (will update if/when I get one).

Yes - DV is a good idea.

Thonnas said:

I also upgraded the RAM, which is now my top suspect

I would suspect it too - some motherboards require the RAM voltage to be set manually if all slots are full. Is this the case here?

What RAM set up (model and # sticks etc.) did you have before and what do you have now?

Regards,
Reventon

BUGCHECK SUMMARY

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 20 07:44:56.552 2010 (GMT+12)
System Uptime: 0 days 14:44:03.363
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments ffffb880`19331570 00000000`0000000d 00000000`00000001 fffff800`02c3b8f0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Aug 19 16:34:55.463 2010 (GMT+12)
System Uptime: 0 days 3:24:33.289
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Aug 19 08:07:29.415 2010 (GMT+12)
System Uptime: 1 days 14:35:02.024
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40e8b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
Bugcheck code 00000050
Arguments fffff800`47a93ea1 00000000`00000008 fffff800`47a93ea1 00000000`00000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

@ #2 (and #3)
Done. I never even considered that as a possibility. Wasn't really liking it, anyway. Back to avast.

@ #3
I forgot to mention that I did run memtest86 through 3 passes (I'll have to run it longer, but it wasn't one of my top suspects at the time). I only have 2 sticks installed and have verified proper voltages.

Old sticks were: OCZ2P800R22GK
New sticks are: KVR800D2K2/4GR

Still no stop error after 4+ hours, including the log prep and a little gaming (despite the sluggishness). Going to run a 3d demo test overnight and see if anything pops. How long should I run Driver Verifier if nothing happens?

Hopefully avast was the culprit.

Avast is also known for the same kind of errors. Microsoft Security Essentials is the way to go, at least until this is sorted.

However I think that the following is your #1 problem

Thonnas said:

Old sticks were: OCZ2P800R22GK - OCZ (CAS Latency 4)
New sticks are: KVR800D2K2/4GR - Kingston (CAS Latency 6)

Mixing non-identical sticks of RAM (especially ones with different timings as shown above) can cause problems exactly likes the one seen above.

Remove the new set and see if problems continue.

If you want to replace the new set buy identical RAM to your old set.

EDIT: I misinterpreted what you were saying. You have not mixed the RAM at all. However, you should still swap the old sticks in for now.

Yeah, I'm aware of the differences. I'm using the old ones in a different system. I might pick up some other ram tomorrow.

Just as I was about to leave it for the night, I got a stop error pointing to avast, so I'll remove that and keep DV on.

Alright, got another stop error. I disabled driver verifier and processed another report package (see attached).

Let me know what you think.

Hi,

For some reason the collection application did not pick up any BSOD minidumps. . .

However - I was able to see that you have had a few BSODs (as well as some apphangs) since the date of the last minidump.

Code:

8/27/2010 9:55 PM        Fault bucket X64_IP_MISALIGNED, type 0 Event Name: BlueScreen Attached files: c:\dumps\082710-30357-01.dmp Analysis symbol: X64_IP_MISALIGNED
8/27/2010 8:12 AM        Fault bucket X64_0xc9_226_aswTdi+14e0, type 0 Event Name: BlueScreen Attached files: c:\dumps\082710-37596-01.dmp Analysis symbol: X64_0xc9_226_aswTdi+14e0
8/27/2010 5:35 AM        Event Name: AppHangB1 Problem signature: P1: Fallout3.exe P2: 1.0.0.12 P3: 48d194b3 P4: ee28 P5: 2048
8/27/2010 3:50 AM        Fault bucket X64_0xA_nt!KyRetireDpcList+5, type 0 Event Name: BlueScreen Attached files: c:\dumps\082610-17097-01.dmp Analysis symbol: X64_0xA_nt!KyRetireDpcList+5
8/26/2010 1:11 AM        Event Name: APPCRASH Problem signature: P1: firefox.exe P2: 1.9.2.3855 P3: 4c48d5ce P4: FOXITR~1.OCX P5: 1.0.1.224 P6: 4b849404 P7: c0000005 P8: 00002dce
8/25/2010 10:56 PM        Fault bucket X64_0x3D_HDAudBus!HdaController::Isr+43b Event Name: BlueScreen Attached files: c:\dumps\082510-19702-01.dmp Analysis symbol: X64_0x3D_HDAudBus!HdaController::Isr+43b
8/24/2010 4:01 AM        Event Name: AppHangB1 Problem signature:P1: hl.exea;P2: 1.1.1.1 P3: 48feaf5a P4: af93 P5: 16897 
8/23/2010 7:07 AM        Event Name: AppHangB1 Problem signature: P1: eclient.exe P2: 0.0.0.0 P3: 4c5cd0df P4: 5aae
8/21/2010 8:19 PM        Event Name: APPCRASH Problem signature: P1: firefox.exe P2: 1.9.2.3855 P3: 4c48d5ce P4: FOXITR~1.OCX P5: 1.0.1.224 P6: 4b849404 P7: c0000005 P8: 00002dce

Key points from the above:

1. Avast was responsible for at least one BSOD as seen by the driver aswTdi.sys being mentioned.

2. HDAudBus.sys was blamed for another BSOD. This is a Microsoft Driver - so we are looking for something else at fault here.

3. The location of the 4 minidump files for the four BSODs mentioned is shown to be:

Code:

c:\dumps\082710-30357-01.dmp
c:\dumps\082710-37596-01.dmp
c:\dumps\082610-17097-01.dmp
c:\dumps\082510-19702-01.dmp

C:\dumps is not the standard Minidump location - this is the most likely reason that the application has not picked them up. So, upload the 4 files mentioned above so we can take an indepth look.

Regards,
Reventon

I could have sworn I saw the app identify that location, and thought it was getting everything. I changed it when i enabled mini-dumps. Here are all of them since I switched it.

enjoy