Help me please..BSOD problem again..

From thread located here: https://www.sevenforums.com/crashes-d...ease-help.html

BSOD keep occured..please help..
Hello all friends..

I had posted a thread regarding same issues and follow the suggestion given.
I tried to re-install my touchpad driver from original source..but unluckily this BSOD happened again. I'm not sure whether this is the same error again but it happened everyday. So would somebody please take a look at my minidump file and help me counter this problem?

Attached Files Minidump.rar (113.3 KB, 0 views)

My response will follow shortly...

5 memory dumps from 30 May 2010 to 03 Jun 2010 (5 days)
4 different STOP errors, blaming at least 3 different causes

This may be indicative of a hardware problem - but it's too soon to tell.

But, there are also some indications that Driver Verifier might give us some more info here. So please run it according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, 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).

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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD's:

Code:

Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Wed Jun  2 19:41:01.590 2010 (GMT-4)
System Uptime: 0 days 0:06:11.277
BugCheck A, {28, 2, 1, 8184c0e9}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+1ed )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Wed Jun  2 07:40:44.666 2010 (GMT-4)
System Uptime: 0 days 1:15:46.353
BugCheck A, {c080ba9c, 0, 0, 818bb435}
Probably caused by : memory_corruption ( nt!MiUpdateWsle+1ab )
BUGCHECK_STR:  0xA
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun  1 12:02:17.314 2010 (GMT-4)
System Uptime: 0 days 2:40:23.001
BUGCHECK_STR:  0x50
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun  1 09:21:39.769 2010 (GMT-4)
System Uptime: 0 days 1:11:16.581
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun May 30 11:35:16.951 2010 (GMT-4)
System Uptime: 0 days 0:44:46.748
BugCheck D1, {f6cd2e0, 7, 0, 8b223756}
*** WARNING: Unable to verify timestamp for SynTP.sys
*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
Probably caused by : SynTP.sys ( SynTP+3756 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System

Use the system normally for about 36 hours (an estimate on my part) - or until you get a crash.
Upload the memory dump so we can analyze it.
If it shows a Driver Verifier enabled crash, then you can turn the Driver Verifier off.
If you do not get a crash within 36 hours, turn off Driver Verifier anyway - and let us know.