P5GDC Deluxe BSOD on startup

C

cdcdcd

Please help me understand and possibly solve this problem.

This is on a new machine with and Asus P5GDC Deluxe motherboard, Intel
LGA 775 Pentium 4 540J 3.2 GHz, XFX nVIDIA GeForce 6600 Video Card,
Mushkin 1 GB (2x512MB) DDR PC3200 and the usual hard drive, DVD
player, DVD-R drives.

I get a blue screen of death when I start the computer (not always,
but frequently enough to be anoying. The OS is XP Pro SP2. As far as I
know the BIOS and drivers are the latest.

I would suspect its not the memory unless I am very unlucky. I
replaced the memory totally. The memory I used to have on the machine
was Mushkin DDR (2 x 512MB) Now the machine has Mushkin DDR2 (again 2
x 512MB). It started fine three times and on the fourth I got a BSOD.
Here's the minidump from today:

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address
pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this
address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never
have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804e194e, The address that the exception occurred at
Arg3: ec51487c, Trap Frame
Arg4: 00000000

Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nt!KiTrap0D+123
804e194e 8903 mov [ebx],eax

TRAP_FRAME: ec51487c -- (.trap ffffffffec51487c)
ErrCode = 00000002
eax=8544a000 ebx=00000000 ecx=ec2aa820 edx=02510005 esi=00000000
edi=ec5149d4
eip=804e194e esp=ec5148f0 ebp=ec2aa820 iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
nt!KiTrap0D+0x123:
804e194e 8903 mov [ebx],eax ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 02510005 to 804e194e

STACK_TEXT:
ec2aa820 02510005 0100000f 0000026a 0000001e nt!KiTrap0D+0x123
WARNING: Frame IP not in any known module. Following frames may be
wrong.
8544a000 80564258 00000000 00000000 8544a000 0x2510005
8544a000 80564258 00000000 00000000 8544a000 nt!SeAccessCheck+0x114
85d93000 00000000 00000000 00000000 00000000 nt!SeAccessCheck+0x114

FOLLOWUP_IP:
nt!KiTrap0D+123
804e194e 8903 mov [ebx],eax

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiTrap0D+123

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 41107faa

STACK_COMMAND: .trap ffffffffec51487c ; kb

FAILURE_BUCKET_ID: 0x8E_nt!KiTrap0D+123

BUCKET_ID: 0x8E_nt!KiTrap0D+123

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

Mark A

cdcdcd said:
Please help me understand and possibly solve this problem.

This is on a new machine with and Asus P5GDC Deluxe motherboard, Intel
LGA 775 Pentium 4 540J 3.2 GHz, XFX nVIDIA GeForce 6600 Video Card,
Mushkin 1 GB (2x512MB) DDR PC3200 and the usual hard drive, DVD
player, DVD-R drives.

I get a blue screen of death when I start the computer (not always,
but frequently enough to be anoying. The OS is XP Pro SP2. As far as I
know the BIOS and drivers are the latest.

I would suspect its not the memory unless I am very unlucky. I
replaced the memory totally. The memory I used to have on the machine
was Mushkin DDR (2 x 512MB) Now the machine has Mushkin DDR2 (again 2
x 512MB). It started fine three times and on the fourth I got a BSOD.
Here's the minidump from today:

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address
pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this
address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never
have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804e194e, The address that the exception occurred at
Arg3: ec51487c, Trap Frame
Arg4: 00000000

Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nt!KiTrap0D+123
804e194e 8903 mov [ebx],eax

TRAP_FRAME: ec51487c -- (.trap ffffffffec51487c)
ErrCode = 00000002
eax=8544a000 ebx=00000000 ecx=ec2aa820 edx=02510005 esi=00000000
edi=ec5149d4
eip=804e194e esp=ec5148f0 ebp=ec2aa820 iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
nt!KiTrap0D+0x123:
804e194e 8903 mov [ebx],eax ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 02510005 to 804e194e

STACK_TEXT:
ec2aa820 02510005 0100000f 0000026a 0000001e nt!KiTrap0D+0x123
WARNING: Frame IP not in any known module. Following frames may be
wrong.
8544a000 80564258 00000000 00000000 8544a000 0x2510005
8544a000 80564258 00000000 00000000 8544a000 nt!SeAccessCheck+0x114
85d93000 00000000 00000000 00000000 00000000 nt!SeAccessCheck+0x114

FOLLOWUP_IP:
nt!KiTrap0D+123
804e194e 8903 mov [ebx],eax

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiTrap0D+123

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 41107faa

STACK_COMMAND: .trap ffffffffec51487c ; kb

FAILURE_BUCKET_ID: 0x8E_nt!KiTrap0D+123

BUCKET_ID: 0x8E_nt!KiTrap0D+123

Followup: MachineOwner
Click to expand...
I assume you are not overclocking anything. I would make sure you have the
latest firmware for the optical drives. If that does not help, then
disconnect them to see if that fixes the problem. Try disconnecting or
swapping out other components (like video card) if possible (you can run
video from an old PCI card, etc.).
 
P

Paul

cdcdcd said:
Please help me understand and possibly solve this problem.

This is on a new machine with and Asus P5GDC Deluxe motherboard, Intel
LGA 775 Pentium 4 540J 3.2 GHz, XFX nVIDIA GeForce 6600 Video Card,
Mushkin 1 GB (2x512MB) DDR PC3200 and the usual hard drive, DVD
player, DVD-R drives.

I get a blue screen of death when I start the computer (not always,
but frequently enough to be anoying. The OS is XP Pro SP2. As far as I
know the BIOS and drivers are the latest.

I would suspect its not the memory unless I am very unlucky. I
replaced the memory totally. The memory I used to have on the machine
was Mushkin DDR (2 x 512MB) Now the machine has Mushkin DDR2 (again 2
x 512MB). It started fine three times and on the fourth I got a BSOD.
Here's the minidump from today:

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
Click to expand...

How is the general machine health ?

1) Run memtest86+ from memtest.org - a few passes error free should suffice.
2) Run Prime95 from mersenne.org. This is a Windows level test,
and it proves the processor can complete a lengthy calculation
error free.
3) Use Asus Probe to verify temperatures and voltages.
The P4 processor will throttle (reduce compute rate) as it
approaches 70C. Supply voltages should be maintained to within
their 5% regulation limits, whether Prime95 is running or the
machine is idle. Some variation in processor voltage is allowed,
but the variation should correspond to processor activity.

Perhaps with additional testing, the cause will become more clear.

What kind of power supply are you using ?

Paul
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Windows Xp Reboot alone 2
Print Spooler Crashes on a regular basis - Windows 2003 Server 4
Irda.sys bsod 10
Vista crashes with a BSOD always - Potential conflict with OneCare 4
IRQL Not Less Or Equal crash, win32k.sys 3
!!! Strange BSOD !!! 5
Get BSOD error and shut down when loading blank CD/DVD media 2
BSoD references missing file? 4

Top