BlueScreen on new system

SylarKEN · 03 Jun 2010

please help,

i have just got my pc from shop, has this error i had attached dmp file

very odd.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 2057

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000005003
BCP2: FFFFF70001080000
BCP3: 0000000000000EE4
BCP4: 000008B300001FC8
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\060310-19921-01.dmp
C:\Users\RayKenny\AppData\Local\Temp\WER-32509828-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

usasma · 03 Jun 2010

A very strange set of BSOD's - a STOP 0x1A, 2 STOP 0xA's, and a STOP 0x24

I'd suggest starting with these free 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)

Then, please update the AsIO.sys file by updating your Asus PCProbe program from the Asus website.

If the diagnostics pass, 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's:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun  3 04:51:54.737 2010 (GMT-4)
System Uptime: 0 days 2:52:26.830
BugCheck 1A, {5003, fffff70001080000, ee4, 8b300001fc8}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29771 )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  rundll32.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun  3 01:58:11.870 2010 (GMT-4)
System Uptime: 0 days 0:30:34.963
BugCheck A, {ffffffff, 2, 1, fffff80002c9584c}
Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+13c )
BUGCHECK_STR:  0xA
PROCESS_NAME:  MsMpEng.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun  2 16:33:37.502 2010 (GMT-4)
System Uptime: 0 days 0:12:35.595
BugCheck A, {f8011e, 2, 1, fffff80002aebf27}
Probably caused by : ntkrnlmp.exe ( nt!ExTryAcquireSpinLockExclusiveAtDpcLevel+2f )
BUGCHECK_STR:  0xA
PROCESS_NAME:  msiexec.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun  2 16:20:12.591 2010 (GMT-4)
System Uptime: 0 days 0:40:25.083
BugCheck 24, {1904fb, fffff8800a393958, fffff8800a3931c0, fffff880012df098}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCreateScb+118 )
PROCESS_NAME:  war3_Install.e
BUGCHECK_STR:  0x24

SylarKEN · 30 Jun 2010

please help, just back from holiday.

I done memory test and all update , i still get blue screen.

help..............please i dont know what to do with this.it a brand new machine

many appreciate.

usasma · 30 Jun 2010

I just got back from holiday myself! :)

Did you run the HDD diagnostic? Did you do the malware scan? Did you update the AsIO.sys program?

The Driver Verifier is supposed to cause a BSOD - let's analyze the dump file and see what it says......

usasma · 30 Jun 2010

Still probably hardware.
AsIO.sys program is not updated
None of the memory dumps are Driver Verifier enabled.

Please follow the instructions again in Post #2

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun 30 14:14:34.008 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:06.100
BugCheck 3B, {c0000005, fffff80002db40f3, fffff880092d5ed0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun 30 14:02:56.462 2010 (UTC - 4:00)
System Uptime: 0 days 0:09:03.555
BugCheck 1E, {ffffffffc0000005, fffff80002f690cc, 0, 200}
Probably caused by : memory_corruption ( nt!MiApplyCompressedFixups+40 )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun 30 13:52:50.705 2010 (UTC - 4:00)
System Uptime: 0 days 0:15:24.798
BugCheck 1A, {41284, 12992001, 2006, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  MsMpEng.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 28 20:08:45.349 2010 (UTC - 4:00)
System Uptime: 0 days 6:02:53.441
BugCheck 3B, {c0000005, fffff88002c16303, fffff88008b04d20, 0}
Probably caused by : MpFilter.sys ( MpFilter+16303 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  MsMpEng.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 27 14:16:58.341 2010 (UTC - 4:00)
System Uptime: 0 days 0:07:51.434
BugCheck 24, {1904fb, fffff88003338758, fffff88003337fc0, fffff880012ad708}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+b6c8 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 27 13:55:00.688 2010 (UTC - 4:00)
System Uptime: 0 days 8:56:29.701
BugCheck 1A, {5003, fffff70001080000, 10775, 1077700020cea}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b86 )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun 24 20:45:29.085 2010 (UTC - 4:00)
System Uptime: 0 days 5:53:44.224
BugCheck 3B, {c0000005, fffff80002fc297c, fffff8800b093d70, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObDereferenceSecurityDescriptor+20 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  taskhost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun 23 03:27:24.637 2010 (UTC - 4:00)
System Uptime: 0 days 0:54:32.666
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
BugCheck 1000007E, {ffffffffc000001d, fffff88004b26c7c, fffff880021b79f8, fffff880021b7260}
Probably caused by : atikmdag.sys ( atikmdag+2aec7c )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

BSOD BUGCHECK SUMMARY

Code:


fffff880`0437d000 fffff880`04384000   AsIO     AsIO.sys     Mon Dec 17 04:11:49 2007 (47663D55)