Windows 7: Windows 7 BSOD on ASUS P2K-E with Core2 Quad

I have been getting periodic BSOD on a machine that I recently built with an ASUS P2K-E motherboard and a Core2 Quad Q6600 processor. This is running Windows 7 RTM.

I can go a day or two with no problem and then have 2 BSOD within a couple of hours. No apparent pattern to it. The other day it happened while I wasn't even touching the keyboard. No audio or video going on - the screen just all of a sudden went blue and restarted.

I'm using all peripherals on the motherboard (audio, etc) except for the NIC. I suspected that might be the problem, so I disabled it and installed a dLink GB NIC. Same problem though. All drivers are from Windows Update. I didn't have to manually load anything other than the dLink driver for tyhe NIC - just got automatically detected and installed when I loaded the machine.

I attached the dump files. Greatly appreciated if someone can give me a clue here what might be going on.

W

While we are waiting for someone with a true debugger I took a quick look at this one. It seems like iexplore.exe caused win 7 to puke and die. Have you been having trouble with explorer hanging, or being busy?

TOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: iexplore.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002f6aa69 to fffff80002f6464c

STACK_TEXT:
fffff880`0d486ae0 fffff800`02f6aa69 : fffff880`0d486c00 00000000`00100000 00000000`00000000 00000000`00000001 : nt!ObReferenceObjectByHandleWithTag+0x10c
fffff880`0d486bb0 fffff800`02c72153 : fffffa80`0aa054c0 00000000`000015b4 00000000`00000000 00000000`00000000 : nt!NtWaitForSingleObject+0x69
fffff880`0d486c20 00000000`75122dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0ab9ed88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75122dd9


FOLLOWUP_IP:
nt!ObReferenceObjectByHandleWithTag+10c
fffff800`02f6464c 0fb64518 movzx eax,byte ptr [rbp+18h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ObReferenceObjectByHandleWithTag+10c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

STACK_COMMAND: .cxr 0xfffff8800d486100 ; kb

FAILURE_BUCKET_ID: X64_0x3B_nt!ObReferenceObjectByHandleWithTag+10c

BUCKET_ID: X64_0x3B_nt!ObReferenceObjectByHandleWithTag+10c

Followup: MachineOwner

Possible causes

This problem occurs if one or more of the processors in the computer:
•Require a microcode update that is not applied by the computer's basic input/output system (BIOS).
•Are damaged or defective.
•Are operating outside their specified ranges for temperature, power, or other conditions.



Let us know. Have you had more than 1 BSOD?

Ken

Nice work zigzag3143!

More memory dump files will be necessary to narrow down the possibilities here.

The STOP 0x3B error is a system service exception - which means that there was an error transitioning from non-privileged to privileged code. The most common cause for this is video drivers - but there's many other things that can cause this.

Several things to check:
- you have an older version of the ASACPI.sys driver on the system. This is normally associated with the Asus AISuite. Please go to the Asus website and download the Windows 7 version of this utility and install it. This driver is known to cause BSOD's in Windows 7
- your Marvell Yukon network driver is outdated, please visit the Marvell website to download the latest version. Please download the Windows 7 x64 version from here: Marvell: Download Drivers and install it on your system (if the Marvell device is still installed - if not, then please uninstall the Marvell software from your system).
- Something likely named Live Mesh has outdated drivers on your system (rdpdispm.sys). Please update that also.

Thanks for the quick replies. I have had several BSODs and have been seeing some hangs here and there with iExplore, so that sounds relevant. I think I forgot to mention that this is x64 version of Windows 7 - not sure if that metters or not.

Several things to try here. I'll report back how it goes.

This one,
This problem occurs if one or more of the processors in the computer:
•Require a microcode update that is not applied by the computer's basic input/output system (BIOS).
•Are damaged or defective.
•Are operating outside their specified ranges for temperature, power, or other conditions.

Leads me to believe it's a voltage shortfall somewhere in the system bios. Or there could be a bios update that can help you.

If you recently built the system there are probably a few adjustments that can be made in bios to fix this type of problem...system voltages or memory settings.

The error above also indicates that the processor is out of adjustment or unstable.

Also, running 6GB Ram usually requires you to mix memory types which hardly ever works correctly. Suggest the Op try running 4GB matched set with memory settings at manufacture specs.

Could someone post a link to this quote?:
The only thing that I can find with that text in it is a reference to a STOP 0x7f message here: Stop 7F, 0x00000008 (double-fault) error occurs because of a single-bit error in the ESP register

No need for a link, it's right at the bottom of ZigZags post.

Fine, I'll bow out of this one also.
Good luck

I'm done messing with this. I have two ASUS motherboards that have been nothing but trouble with Windows 7 x64 and a single MSI motherboard that has not had the slightest problem. I can't locate Windows 7 drivers from ASUS - beta or otherwise, and every fix I've tried has had no effect on the problems. I can replace the motherboard in my main machine with an Intel that has published Windows 7 x64 drivers for $90. Well worth my not having to spend any more time screwing with it.