• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Random Reboots after upgrade

M

mstumpf123

Junior Member
:disgust: Hello, I installed a new mb ecs p4m800pro-m v2 and intel pentium d 945 dual core cpu, reinstalled winxp pro. machine started rebooting almost immediatley. have upgraded ps to 500w, have tried 3 versions of the board. i might say that the board has 2gb pc 3200 ddr 400 of memory, that was working fine previously. in despair, installed clean copy of windows in empty partition, worked for about 10 minutes then rebooted. I get a machine check exception error in event viewer, but msoft says only that it could be mem, ps, cpu, ram. have run memtest on memory for several hours, have been logging temps with everest, cpu sits around 45c no spikes. i am a loss, as i said , this is the 3rd board i tried. no other peripherals other than what came on the board. any ideas???
 
have read nad tried those ideas, yesterday took the board and cpu to store. it failed at store, replaced cpu. took back to office, it failed within 5 minutes. switched memory , still fails. today going to try to running board outside of case (who knows). to summarize, have replaced so far -> cpu, board, ram, ps. will also disconnect cdrom drives, and floppy. still desparate...........
 
Originally posted by: mstumpf123
have read nad tried those ideas, yesterday took the board and cpu to store. it failed at store, replaced cpu. took back to office, it failed within 5 minutes. switched memory , still fails. today going to try to running board outside of case (who knows). to summarize, have replaced so far -> cpu, board, ram, ps. will also disconnect cdrom drives, and floppy. still desparate...........
Click to expand...

Since you just bought this machine, I'd suggest taking it back to the hardware vendor to have them give you a machine that works.

nocturne, I couldn't post in your thread, but I had a few comments on what you wrote:

N>also set dump file size to small 64kb if you plan on debugging the dump files

If you're going to do this yourself, you ought to set it to kernel size. If you're going to e-mail the dumpfile to someone else, only then should someone set it to mini-size. Kernel dumps will give better information, more frequently, and more reliably. Since there's no need to mail it to anyone, there's no reason not to use it.

N>Most often, a device driver isn't compatible with SP2, so an updated one is necessary

That's generous. I'd say that the driver is poorly written to begin with if there's a problem, since there's typically no reason for an older driver to crash if it's written properly the first time, if it generally works in XP.

N>BSOD's from software can be much harder to diagnose, unless it is obvious which program initiates the crash

You wrote 'software'; I'd say 'driver', since what most people call software (ie programs) runs in user mode and won't BSOD a box.

Good guide.
 
My friend's computer was doing something similar once. You could make it reboot by banging on the desk!

He had screwed the mobo DIRECTLY to the case with no brass risers so it was shorting out on the case.

BTW, I'm not saying that's what you've done...
 
I'm just wondering if the OP found a soultion to his problem. I am having the exact same problem with the same board. I've built ten systems with this board and no problems. Now I'm on my third board on another build and I keep having the same reboot probem. I can replicate it by printing to a LAN based Brother printer, but it won't reboot when printing to a LAN HP Laserjet. MEMTEST passes fine, Stress prime passes fine, but as soon as I try to print to the brother printer, it reboots. It will also reboot randomly when browsing the net. I've swapped EVERY single part out, reinstalled windows, disabled onboard devices to no avail. If I has to guess, there may be a conflict arising from the order in which devices or windows updates are installed, except I can't pinpoint where the probelm lies. Very frustrating to say the least. I'm stubborn so I won't give up until I solve the problem. I'm pretty sure its a software issue because I find it hard to believe I managed to get three defective boards in a row.
 
BTW here's the entry in the event log
"The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009c (0x00000000, 0xf7a22050, 0xb2000000, 0x1040080f). A dump was saved in: C:\WINDOWS\Minidump\Mini102806-01.dmp."

From what I understand this is a pretty generic error code, but maybe someone has some insight.
 
Following your instructions on your blog, here's what I got:
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini102806-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\debug*http//msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sat Oct 28 18:24:42.656 2006 (GMT-7)
System Uptime: 0 days 0:03:14.350
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.....................................................................................................
Loading User Symbols
Loading unloaded module list
..
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, f7a22050, b2000000, 1040080f}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+601aa )

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

Any clues?
 
Yes - fix your symbols. Go through the Symbol file Path setup steps again, and be sure you save your workspace after doing that, then repeat the !analyze -v bits, and those symbol errors should go away. Then let us know.
 
I forced a crash by printing to the networked Brother printer. Here it is.


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


Loading Dump File [C:\WINDOWS\Minidump\Mini102806-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/downloads/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sat Oct 28 19:22:52.031 2006 (GMT-7)
System Uptime: 0 days 0:07:48.729
Loading Kernel Symbols
.....................................................................................................
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, f7a22050, b2000000, 1040080f}

*** WARNING: Unable to verify timestamp for xfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for xfilt.sys
Probably caused by : intelppm.sys ( intelppm!AcpiC1Idle+12 )

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

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

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000000
Arg2: f7a22050
Arg3: b2000000
Arg4: 1040080f

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

NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

This error is documented in the following publication:

- IA-32 Intel(r) Architecture Software Developer's Manual
Volume 3: System Programming Guide

Bit Mask:

MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1011001000000000000000000000000000010000010000000000100000001111


VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.

UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.

EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.

PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.

BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL



Concatenated Error Code:
--------------------------
_VAL_UC_EN_PCC_BUSCONNERR_F

This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.

BUGCHECK_STR: 0x9C_IA32_GenuineIntel

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 80702bff to 805371aa

STACK_TEXT:
f7a22028 80702bff 0000009c 00000000 f7a22050 nt!KeBugCheckEx+0x1b
f7a22154 806fdc52 f7a1ed70 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd
f7a22154 f78a0062 f7a1ed70 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x4a
f7ba5d38 f7a1e000 80560f00 f7a20e20 f7a1ec50 intelppm!AcpiC1Idle+0x12
WARNING: Frame IP not in any known module. Following frames may be wrong.
f7ba5d50 804dcbef 00000000 0000000e 00000000 0xf7a1e000
f7ba5d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10


STACK_COMMAND: kb

FOLLOWUP_IP:
intelppm!AcpiC1Idle+12
f78a0062 6a00 push 0

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: intelppm!AcpiC1Idle+12

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME: intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107b37

FAILURE_BUCKET_ID: 0x9C_IA32_GenuineIntel_intelppm!AcpiC1Idle+12

BUCKET_ID: 0x9C_IA32_GenuineIntel_intelppm!AcpiC1Idle+12

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


BTW, thanks for your help.
 
Unsure without looking at it more ... first glance seems to be a printer driver issue forcing a problem with a CPU driver, but that's just a guess. Do you have the latest Brother printer drivers on the Windows PC that is sharing this print device (assuming it's XP)?
 
It also crashes randomly when the printer driver is uninstalled. I just know that I can force the error that way. Other random reboots seem to occur when browsing the internet but it returns the same error.
 
Get rid of that driver completely from your system and then we can continue. Call Brother if you must, but get it out of there.
 
I think I finally found the problem (knock on wood.) After following your guide and then googling some of the info found in the debug report, I started messing with the memory settings in the bios. The default is set to AUTO, so I changed it to 200mhz and voila, no more reboots, not even while printing. What a finicky chipset. It would pass Memtest and stress prime no prob, but as soon as I would start browsing the internet or printing to the network printer it would crash. I wonder if it was overclocking the PCI bus? Is there a reporting tool that would tell me what the current speed the PCI bus is set at? Thanks again for all of your help.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top