Well stop code suggest memory I guess.
If lucky it hints to where problem is - precisely. Cant see where here except for the obvious. I still would not exclude software.
In C:\Windows\Minidump\ you will have a mini-dump file, 1 for each crash, might tell more. Upload the latest here.
More importantly, test memory. Vista has build in tester, can be run from boot menu as well (copy and pasted from some MS article)
To run Windows Memory Diagnostic
- Click Start, click All Programs, and then expand Accessories.
- Right-click Command Prompt and select Run elevated from the context menu.
- At the command prompt, type mdsched.exe. If you are prompted, allow the action. You can choose to restart the computer and run the tool immediately or schedule the tool to run at the next restart.
- Windows Memory Diagnostic runs automatically after the computer restart. Windows Memory Diagnostic allows you to choose among three test suites of varying thoroughness.
Even better is to use Memtest86+
Memtest86+ - Advanced Memory Diagnostic Tool Download, burn iso, boot from CD, let it run for some hours. All there is to it.
People who overclock or otherwize tweak memory/cpu can get the most strangest STOP codes pointing in all directions, AV is to blaim, then IE7, then some low level driver - and nothing will be resolved until memory is fixed. I have tried having perfect Memtest86+ and stilll getting STOP codes. There is one more test you could do but try Memtest86+ first, or the Window Diag thing. Memtest86+ must be able to run no matter what.
Remember the SFC command
http://www.vistax64.com/tutorials/66978-system-files-sfc-command.html?ltr=S Very important you run that because some system files can be corrupted by now.
Also CHKDSK
http://www.vistax64.com/tutorials/67612-check-disk-chkdsk.html?ltr=C
Not much point in running them now - but do it after result of memory test. Actually only do it if successful test. If fail there is a memory module to look at! With any luck they get too little voltage, wrong timings and can be fixed. You are right about the changing slot. If extremely lucky changing slot can sometimes make all the difference. Dont count on that.
With no fail I would like to see yet another RSIT - not convinced this is hardware problem, mainly because your previous logs were messy. We will see. Also have to get some more info on memory module/bios setting for memory but later.