Windows 7 is unstable

techyguy said:

Well,I got to check only on the antiviruses,as I already got a hardware firewall(I have disabled Windows Firewall now).I have already checked MSE,and well,I liked it! :P It's probably the most compatible with Windows,so I'll stick with it (plus it has a x64 version).

Microsoft Security Essentials is a good choice. You might wanna have WinPatrol and Malwarebytes for added protection.

Hope that helps,
Captain

Capt.Jack Sparrow said:

techyguy said:

Well,I got to check only on the antiviruses,as I already got a hardware firewall(I have disabled Windows Firewall now).I have already checked MSE,and well,I liked it! :P It's probably the most compatible with Windows,so I'll stick with it (plus it has a x64 version).

Microsoft Security Essentials is a good choice. You might wanna have WinPatrol and Malwarebytes for added protection.

Hope that helps,
Captain

Thanks a lot for your help.However,I found that nod 32 wasn't the cause,it just induced the problem.As I said before,I thought the problem was ram,and it was.I did memory tests with memtest86+ and found that one of my memories was faulty.Now,I use 6gb of ram,and everything runs perfect as it should be.

The problem in general is characterized by many exception code 0xc0000005 errors in different programs or services in each reboot(dll files may not load,it will seem like they are corrupted,when they aren't) and by some BSOD and random restarts.

Now,I'm gonna give some steps,for anyone who has a similar problem:
Firstly,when you check if the problem persists,try to open as many programs as you can altogether(and every program you got,don't forget to check all of them),so that you push your memory a little,in order to project the problem.
Another way is through Windows Experience Index.If it stops or crashes,or finishes but the score isn't saved,then you got a problem.
The steps are:

1.Check for malware,as malware usually causes this kind of problems,because it tries to access memory addresses that it shouldn't.Clean the malware,if there is any and retry.

2.Update your bios and drivers.Check for driver errors with DPC Latency Checker->http://www.thesycon.de/eng/latency_check.shtml.Then retry.

3.Disable any resource hogging applications and services and retry.

4.Disable any firewall or antivirus you have and retry.

5.Turn Dep off and retry.To turn Dep off,do the following:
Open the command line: “Start” -> enter “cmd.exe” into search field and hit enter.
Simply run the following command to disable it:
bcdedit.exe /set {current} nx AlwaysOff
You can enable it again with:
bcdedit.exe /set {current} nx AlwaysOn

If you run this command and you are not able to start Windows, then run Windows in safemode and enable it again, using the command above. Start Windows in safemode by pressing F8 during bootup.

Alternatively,you can use a tool like easybcd 2.0 beta->http://neosmart.net/forums/showthread.php?t=642.Just register at the forum,and then download the latest build.
Open easybcd and go to advanced settings->advanced->noexecute and set it to always off.

6.If the problems still persists,try to set the maximum memory through ->run->msconfig->boot tab->select the current os->advanced options->maximum memory and set it to a number from 1024-4095 mb (1 mb is for hardware) and retry.If the system works fine,then go to step 8.

7.Scan and repair corrupted files through windows-key+r->cmd->sfc /scannow.

8.If none of these worked or step 6 worked,try the memtest86+ boot utility and check for faulty ram(some info is given further down).I got it from ubcd-> Ultimate Boot CD - Download the UBCD.Get the image and burn it.

Some info for anyone who doesn't know how dual channel works:

Dual channel practically means that two memory slots work as one.Memories in slot 1 and 3 work together,and memories in 2 and 4 work together.If you have let's say,2x2048mb memories,Windows reads slots 1 and 3 as one (if you have put the two memories in slot 1 and 3,which is recommended because that way,memory performs faster!) and you see 4096 mb used(if you have Windows x64,less if you are using Windows x86).

Now,if you are using 4x2048mb memories,Windows (x64,x84 reads 8gb but doesn't use slots 2 and 4) reads and uses all slots and memories are mapped to this ranges:
0-4096mb ->Slot 1 and 3
4096-8192mb ->Slot 2 and 4

So...if you didn't have any problems when you used 4gbs of memories and you have with 8gbs,that means that either your 2 and 4 slots are damaged,or that one of the two memories inserted in slots 2 and 4 have a problem,or maybe both of them!
For my problem,I took out memories in slots 1,2 and 3 and put 4 in slot 1.Everything was fine,no errors.Then,I put the memory which used to be in slot 2 in slot 3 (it was dual channel that way) and got errors.So I knew now,that the memory in slot 2 was faulty.Then I took out the faulty one,and put the memory that used to be in slot 1.Everything was fine again!So,now I got no access violation errors anymore!

When you'll run the test,leave it at least 2 passes (you can run all tests,or select 1 of them),in order to make sure,that you do or do not have an error.

Obviously,the exact opposite could happen,one of the memories in slot 1 and 3 could be faulty,but the test is the same(only then,Windows would have problems even with 4bs of ram,if you had 2x2048mbs memories in slot 1 and 3).