Windows 7 Tried updating drivers and uninstalling some known bsod causing programs. still having bsods

spcimnaerx

New Member
Joined
Jul 16, 2011
Hey guys, have some bsods that happen quite often.
Do I have memory problems? Should I try memtest?
 

Attachments

  • 022511-40841-01.dmp
    140.6 KB · Views: 516
  • 051611-31496-01.dmp
    140.6 KB · Views: 499
  • 052911-58749-01.dmp
    140.6 KB · Views: 510
  • 052911-60044-01.dmp
    140.6 KB · Views: 491
  • 070411-22557-01.dmp
    140.6 KB · Views: 485
  • 070411-28329-01.dmp
    140.6 KB · Views: 474
  • 070511-23805-01.dmp
    140.6 KB · Views: 482
  • 070511-24148-01.dmp
    140.6 KB · Views: 472
  • 070611-22183-01.dmp
    140.6 KB · Views: 495
  • 070611-24866-01.dmp
    140.6 KB · Views: 517
  • 070811-19843-01.dmp
    140.6 KB · Views: 494
  • 070811-21153-01.dmp
    140.6 KB · Views: 509
  • 070911-20108-01.dmp
    140.7 KB · Views: 517
  • 070911-22495-01.dmp
    140.7 KB · Views: 492
  • 070911-22822-01.dmp
    140.7 KB · Views: 518
  • 070911-23025-01.dmp
    140.7 KB · Views: 497
  • 070911-23181-01.dmp
    140.7 KB · Views: 501
  • 070911-23212-01.dmp
    140.7 KB · Views: 484
  • 070911-38079-01.dmp
    140.7 KB · Views: 471
  • 071011-30232-01.dmp
    140.7 KB · Views: 531
  • 071211-71526-01.dmp
    140.7 KB · Views: 481
  • 071411-25131-01.dmp
    140.7 KB · Views: 495
  • 071511-18907-01.dmp
    140.7 KB · Views: 501
  • 071511-21262-01.dmp
    140.7 KB · Views: 489
  • 071511-25006-01.dmp
    140.7 KB · Views: 495
  • 071511-25599-01.dmp
    140.7 KB · Views: 487
  • 071611-19531-01.dmp
    140.7 KB · Views: 429
spcimnaerx Hi and welcome.

These were virtually identical and blamed on memory corruption. Please run the following tests.




Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
 
I don't know much about the memory situation, but you do have some older drivers on your system so perhaps you know what they are for. It does not mean they are causing the problem, but something to see if you can get an updated version of.

MarvinBus MarvinBus.sys Fri Sep 23 16:17:57 2005 Possibly from Pinnacle...

giveio giveio.sys Wed Apr 03 21:33:25 1996 Seems to be for some type of mobile device...

mpc-hc.exe Seems to be a WMP substitute or codec of some type.

This one seems to be from Avast and perhaps not causing the problem, but possibly involved. Maybe it is just catching some type of security violation. aswSP.SYS
 
Back
Top Bottom