BSOD

[shuvit]

Hi
I have bsod when playing game, plugging in usb drives.
Not on over clocked
It has been bugging me for weeks


Attached are my files
Pls help.
Thanks!

 

[zigzag3143]

Hi
I have bsod when playing game, plugging in usb drives.
Not on over clocked
It has been bugging me for weeks


Attached are my files
Pls help.
Thanks!

These were probably caused by your video driver. You need to remove all traces of the current driver before you download and instll a fresh copy.


Let us know if y ou need help

Ken

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat May 29 14:11:04.162 2010 (GMT-4)
System Uptime: 0 days 0:57:46.505
BugCheck 1000008E, {c0000005, 909c984a, 8ea69b50, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+46c )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  ShippingPC-BmG
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat May 29 13:12:45.663 2010 (GMT-4)
System Uptime: 0 days 0:01:29.021
BUGCHECK_STR:  0x10e_2
PROCESS_NAME:  SearchProtocol
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat May 29 06:28:00.082 2010 (GMT-4)
System Uptime: 0 days 2:43:57.050
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
BUGCHECK_STR:  0xc2_b
PROCESS_NAME:  AssassinsCreed

 

[shuvit]

Thanks

 

[usasma]

Please run Driver Verifier 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:

Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Tue Jun  1 12:06:01.667 2010 (GMT-4)
System Uptime: 0 days 2:07:00.635
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  dwm.exe

 

[usasma]

It would be very nice of you to give us a bit more information about your system - and about what was happening when the BSOD's occurred (where in the boot sequence, etc).

3 memory dumps, 3 different STOP errors, 3 different causes
Starting to look like a hardware error to me - although there's enough evidence of driver involvement that it's not sure.

I would start with these free, bootable hardware diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Mon Jun 14 11:27:29.080 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:29.126
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Mon Jun 14 11:26:01.555 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:21.601
BUGCHECK_STR:  0xDA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Mon Jun 14 11:20:59.633 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:15.054
BugCheck 1000007E, {c000001d, 92764a2a, 8a983794, 8a983370}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

 

[ttran]

Please download 3rd party call memtest 86, burn it to CD and let it run for at least 5 passes

BugCheck 1000007E, {c000001d, 92764a2a, 8a983794, 8a983370}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
BugCheck 1A, {5003, c0802000, ef7, ef9dae}
Probably caused by : memory_corruption ( nt!MiAllocateWsle+6f )
Followup: MachineOwner
---------
BugCheck DA, {504, c04d1a30, 1, 1a346}
Probably caused by : memory_corruption ( nt!MiReplenishBitMap+238 )
Followup: MachineOwner
---------

And also run system file check to see if everything is doing ok
Go start-->type cmd in search and run as administrator--->in cmd window type in sfc /scannow (space between sfc and /)
Good Luck

 

[shuvit]

Hi
Actually i just exchanged my 4 G RAMs last month.
so i can rule them out.

Any othr bugs in the dump tat to take note

 

[reventon]

Hi,

[FONT=lucida console]
System Uptime: 0 days 0:00:[COLOR=Red]28.534[/COLOR]
System Uptime: 0 days 0:00:[COLOR=Red]11.311[/COLOR]
System Uptime: 0 days 0:01:12.374
System Uptime: 0 days 0:00:[COLOR=Red]17.177[/COLOR]
[/FONT]

3 of the 4 BSODs did happen within 1 minute of startup - this suggests that your problem is either with a boot driver or hardware.

The fact that the 4th BSOD happened after an hour means that it is most likely hardware.

Can you try booting your system in SAFE MODE a few times - as if it is Hardware you will still get the BSODs

The easiest bit of Hardware to test is your memory:

Memtest - Instructions:

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

Then (if you have chosen the ISO) burn the ISO using ImgBurn: The Official ImgBurn Website

Boot from the CD/USB and run the test (at least 5 passes per test) with only one stick of RAM in place, if the stick passes then swap it into the other sockets in turn until you can be sure that all the sockets are fine.

Then test the rest of the RAM one at a time (no need to swap the sockets; still 5 passes per test).

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

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Jun 19 16:28:04.488 2010 (GMT+12)
System Uptime: 0 days 0:00:28.534
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Jun 19 16:23:34.265 2010 (GMT+12)
System Uptime: 0 days 0:00:11.311
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_IOERR_C0000428
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Jun 19 15:56:35.328 2010 (GMT+12)
System Uptime: 0 days 0:01:12.374
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Fri Jun 18 04:42:39.131 2010 (GMT+12)
System Uptime: 0 days 0:00:17.177
BugCheck 1000007E, {c0000005, 82b3f87b, 8a99bb00, 8a99b6e0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+21b )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/FONT]

 

[shuvit]

thks