Windows 7: Win 7 keeps on giving me BSOD's

bkg9990 · 20 Jul 2009

It's me again! Got my Windows 7 working for a while but my salvation was short lived. The BSOD fairies came to greet me again. I has something to do with my memory again. Tested memtest and it failed 72%

Here are examples:

Attachment 19164

keypox · 20 Jul 2009

Quote: Originally Posted by bkg9990

It's me again! Got my Windows 7 working for a while but my salvation was short lived. The BSOD fairies came to greet me again. I has something to do with my memory again. Tested memtest and it failed 72%

Here are examples:

Attachment 19164

then your memory maybe bad. Or its overclocked, running at bad timings, not enough voltage?

If you fail memtest then your gonna have problems

Orbital Shark · 20 Jul 2009

Quote: Originally Posted by keypox

then your memory maybe bad. Or its overclocked, running at bad timings, not enough voltage?

If you fail memtest then your gonna have problems

+1

Do you have more than 1 memory stick installed? If so you could try removing 1 then running the memtest again. If it fails then that's the bad stick, if it passes then try the other one.

Note

Just for piece of mind, try the following

1, Test 1 stick of memory
2, (pass or fail) Swap to another slot then test again

2 fails = bad memory
1 fail = bad slot, motherboard at fault

Repeat process for other stick of memory

bkg9990 · 20 Jul 2009

Already did, weird thing is one stick was good so I used that one and all went well with the installation.

After 2 hours I got the BSOD again linking to memory. Tried to run memtest and it's now failing at the very start.

PS: I ran memtest on each slot with 1 ram.

Orbital Shark · 20 Jul 2009

It could be the motherboard causing the issue then. I hate to say it but it could be frying your memory

Is there any way you can check the memory in another machine?

usasma · 20 Jul 2009

Upload the most recent memory dumps with your next post. We only need the one's after you went with the 1 good stick (the others will give false results so we don't need them).

Also, while you're waiting, test the good stick with the memory test again - does it pass or fail? Do you have good power protection (surge suppressor) and have you experienced any power surges/outages/brownouts recently?

bkg9990 · 20 Jul 2009

The ones I posted are the dumps when I used the good stick

Thats the sad part.

usasma · 21 Jul 2009

The memory dumps are all over the place, with no sure indication of a specific issue. This could be due to the memory issues (?have you run the memory test again?) or it may be due to malware (see below).

I noticed 2 older drivers - one for Avira antivirus, and another for a driver named a6qspml5.SYS

There's no search results for this second driver - which is suspicious. Could you search your system for it and see what it's properties are? In particular, check the Details tab for information on the manufacturer.

It may be that this is an infection - so I'd suggest downloading a fresh copy of Avira, uninstalling the old one, and then install the freshly downloaded one. Update it immediately and perform a complete system scan.

Here's a summary of the BSOD's:

Code:

*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7229.0.x86fre.winmain.090604-1901
Debug session time: Fri Jun 19 05:05:38.458 2009 (GMT-4)
System Uptime: 0 days 0:06:51.925
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, 0, a44aba74, 0}
*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
Probably caused by : afd.sys ( afd+3637 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7229.0.x86fre.winmain.090604-1901
Debug session time: Fri Jun 19 10:24:07.081 2009 (GMT-4)
System Uptime: 0 days 1:33:04.595
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7229.0.x86fre.winmain.090604-1901
Debug session time: Fri Jun 19 10:29:31.957 2009 (GMT-4)
System Uptime: 0 days 0:00:47.596
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

Windows 7: Win 7 keeps on giving me BSOD's

Win 7 keeps on giving me BSOD's problems?