ASUS P5Q-EM New install bsod

[blackie]

Hi,

I would really appreciate it if anyone has any advice.

I have just done a clean install of windows 7 64 Professional edition OEM and I am getting occasional bsod problems.

My system is:

Motherboard: P5Q-EM
CPU: Core2duo E7400 2.8GHz
RAM: 2GB Kingston DDR2 800GHz
HDD: 1.5GB Hitachi Green
Onboard Graphics: Intel G45
Antec PSU: 350W
Case: Antec Minuet

I have tried everything I can think of. This is clean install because I wanted to eliminate any errors caused by software or drivers.

So far I have installed windows and turned on updates. I have also installed zencast.

I have followed the instructions for posting and have attached a zip file with a .dmp file, the output from resource monitor and Windows7_BSOD_jcgriff2.

Thanks in advance to anyone who can help.

Cheers.

 

[ttran]

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:

ASACPI   ASACPI.sys   Mon Mar 28 09:30:36 [B][COLOR=Red]2005[/COLOR][/B] (42476C4C)

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

BUGCHECK SUMMARY:

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:  [COLOR=Red]svchost.exe[/COLOR] <--run malwarebyte to make sure this is not something unusal
---------

Run a malware check:
Malwarebytes

Let us know if you need more help

Tuan

 

[blackie]

Thanks for the reply Tuan. That is really helpful. I have updated that driver and I will see how that goes. Thanks again for taking the time to help out.

 

[blackie]

Everything has been going great until tonight I got another crash. I have tried the malwarebyte and done the upgrade of ASACPI. Not sure what I should try next. I have run the Windows7_BSOD_jcgriff2 and performance monitor and attached the results. Does anyone have any ideas on what I should try?


Thanks in advance to anyone who can help.

Cheers.

 

[Tews]

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

 

[blackie]

Thanks for the quick reply Tews! I have attached the three .dmp files that have been created since I reinstalled. Let me know if you need any more information.

Cheers

 

[blackie]

more dumps.

I have a few extra dumps to add. I'm not sure if these have any extra info. I am about to start the process of learning how to read all of this stuff. Any advice on tutorials would be greatly appreciated.

Thanks in advance!

 

[ttran]

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:

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:

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

 

[blackie]

Thanks Tuan,

Since I've only just reinstalled windows I don't have a lot to lose if I get into an unrecoverable mess. I give it a try.

 

[blackie]

Hi,
I've run verifier and had a crash. I have attached the file from the c:\windows\minidump folder. I'm not sure if 'verifier' has its own dump file. If so, could you let me know where to find it. Hopefully something will turn up from this.

Thanks for the help.

 

[ttran]

Hi,
I've run verifier and had a crash. I have attached the file from the c:\windows\minidump folder. I'm not sure if 'verifier' has its own dump file. If so, could you let me know where to find it. Hopefully something will turn up from this.

Thanks for the help.

Just check for the newest DMP after the crash and upload it. Hopefully we can get something out from it

 

[blackie]

Sorry, I was sure that I had attached this. Hopefully this time. I also found a file called MEMORY.DMP that was from the same time but it is large (268MB), is there anything in it of use?
Thanks again for your time on this.

 

[Jonathan_King]

I see memory corruption blamed, but verifier was running. The only driver I see that I suspect would cause that is your Realtek networking drivers:

Rt64win7.sys Thu Feb 26 04:04:13 2009

Please update them to the latest version, you might check on the computer manufacturer's downloads page.

Other than that driver, you may want to test RAM.

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.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Aug  7 07:29:14.824 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:50.712
BugCheck A, {fffffa8010294060, 2, 1, fffff80002ad3cde}
Probably caused by : memory_corruption ( nt!MiDeletePteList+18e )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]