ASUS P5Q-EM New install bsod

I suspect that this is simply device drivers error that cause BSODs.
In looking through your drivers, here is the driver you need to update:

Code:

ASACPI   ASACPI.sys   Mon Mar 28 09:30:36 2005 (42476C4C)

It's date from 2005 is notorious for causing BSODs. Please update it rightaway following this instruction:
https://www.sevenforums.com/787431-post2.html (Make sure to download the right one, double check the name of driver please)

BUGCHECK SUMMARY:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.437\080310-27190-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a15000 PsLoadedModuleList = 0xfffff800`02c52e50
Debug session time: Tue Aug  3 04:22:20.979 2010 (UTC + 7:00)
System Uptime: 0 days 0:02:21.867
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {7, 67c65, 40000, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+351d5 )

Followup: MachineOwner
PROCESS_NAME:  svchost.exe <--run malwarebyte to make sure this is not something unusal
---------

Run a malware check:
Malwarebytes

Let us know if you need more help

Tuan

unfortunately, there were no .dmp files included.. navigate to c:/windows/minidump and zip up the .dmp files, and attach them to your next post...

Hi there,

Beyond that, please run Verifier with these settings:

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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

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

BUGCHECK SUMMARY:

Code:

BugCheck 1E, {ffffffffc0000005, fffff80002dee441, 0, a8}

Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+51 )

Followup: MachineOwner
---------
BugCheck 1A, {41284, 16afa001, 61c3, fffff70001080000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )

Followup: MachineOwner
---------
BugCheck A, {ffffffffffffffe3, 2, 1, fffff80002a8cd42}

Probably caused by : ntkrnlmp.exe ( nt!PopScanIdleList+e2 )

Followup: MachineOwner
---------

BugCheck 3B, {c0000005, fffff80002aa3ef5, fffff880046e0080, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+fd )

Followup: MachineOwner
---------
BugCheck 4E, {7, 67c65, 40000, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+351d5 )

Followup: MachineOwner
---------

Regard,

Tuan