New BSOD thread will thank any help

[maler]

Hello.

A week ago i decided to install windows 7 x64 in my old computer. After installing i had some blue screen issues with marvell device controllers which i have finally solved by moving my hds to ide slots and disabling the driver from the bios. after that i reinstalled the system (tenth time i must say) and found out that blue screens had turned to reboots and, ocasinally, hangs.

I guesses it was a driver issue and after entering the forums decided to run de verifier and the program to make the dump.

If anyone needs any further info pls just ask

My system is:

AMD Athlon X2 dual core processor 6000+ 3000 GHz
Asus M2n32 WS pro
Geforce 8600 GT
2Gb Ram

maybe too short but its kinda hard to ask for help with the system hanging (third time i write this right now =))

Thanks in advance for your time and help

Maler

 

[reventon]

Hi,

BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 12 08:03:57.818 2010 (GMT+12)
System Uptime: 0 days 0:00:08.425
BugCheck A, {e, 2, 1, fffff800028dd31b}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/font]

The BSOD was Verifier Enabled but no 3rd party driver was flagged. This usually means hardware; especially as your drivers appear up to date.

You have had a lot of these errors over the past few days:

Event[648]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2010-07-11T03:16:12.000
  Description: 
Fault bucket , type 0
Event Name: [COLOR=Red]WindowsUpdateFailure[/COLOR]
Response: Not available
Cab Id: 0

A possibility as to why it is failing is the presence of Avast on your system. I would remove or disable it to try and get your computer fully updated.

As the BSOD appears to be hardware related start hardware testing with a memtest:

Memtest - Instructions:

Download the ISO (or the .exe for USB drives) from here Memtest86+ - Advanced Memory Diagnostic Tool

Then (if you have chosen the ISO) burn the ISO using IsoRecorder: ISO Recorder v3

Boot from the CD/USB and run the test (at least 7 passes per test) with only one stick of RAM in place at a time.

It is a time consuming process but it is the only way to be sure it isn't a RAM fault.

For your final test, run the test with all the RAM in place.

Regards,
Reventon

 

[maler]

Just to let you know. I have finally managed to install the update that was pending by stopping the auto-update process, deleting the downloads and the temps, and downloading it again (steps provided by microsoft support). The reboots are gone which is good, but the system still hangs and is rather unreliable. Im starting the ram tests and, considering it seems there was two issues, and one is solved, ill re-run the verifier and rezip the minidump to isolate the problem that is still present.

Anyway I want to thank you for your quick answer. Right now im able to make basic things such as write in the forum.

 

[maler]

Ok, ive tested the ram. 12 passes onthe first module and 24 onthe second, all succesfull. ive run the verifier and loaded the os, but couldnt get a blue screen. the system seemed stable. loaded the verifier again and included microsoft drivers too. couldnt get the error this way either. anyway ive had reboots, hangs and a couple of bs today. im uploading the zipped dump in case some one gets an idea on whats happening.

Thanks again for your time

 

[maler]

bump. still looking for help =)

 

[reventon]

The only dump file in that folder was the dump file that you had uploaded before.

This is suspicious as it probably means that the system is not producing dump files, which is a sign of a hardware error.

For lack of any pointers to the real issue at this point just continue as you are (Driver Verifier on) and upload any dump files that you get.

I would remove Avast just to be sure that it is not the problem, it most likely isn't but I have seen it at fault before.

Download the Avast Removal Tool (ART) from here -> save to desktop.

Boot into SAFEMODE - NO Networking. Then go to desktop, RIGHT-click on the ART icon and select Run as Administrator.

When complete - re-boot.

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

Regards,
Reventon