Sign in with
Sign up | Sign in
Your question

BSOD

Tags:
  • CPUs
  • Blue Screen
Last response: in CPUs
Share
November 17, 2010 11:15:38 AM

Hi, I have a Dell XPS 435MT with i7 920 processor, 6gb ram, 2x OCZ 30GB SSD - raid 0, and had a GTX 295, and Corsair 750 watt PSU... What would happen is while playing a game (or something CPU intensive) later on while the CPU heats up, the game starts to studder... then gets worse and worse and will eventually get a BSOD - didn't pay attention but they were different here and there...
Note this would happen only on a COLD bootup, i would simply restart the computer and everything would be fine and I can play any game and stress the CPU/GPU... This happens while going from a COLD bootup directly to a game. I didn't test out letting the CPU run for a while then playing a game but it's definitely there on a cold bootup...
one BSOD I was able to get was "A clock interrupt was not received on a secondary processor"
I have all the latest drivers, bios, firmware for all my devices and continually update everything...
I also tried disabling hyper threading, turbo boost, - and whatever else little options there were in the Dell BIOS.... and nothing changed...
Thinking it was the GPU, I upgraded to a GTX 580 (which is amazing BTW), and still get the BSOD...
Reading forums, people say that this is a CPU hardware failure? any thoughts? ONLY happens on cold bootup and a restart going right back into game solves the issue...
I'd hate to have to run heaven benchmark and let it crash everytime i start the computer up for the day just to get it started...
Even games like COD will studder and crash with the BSOD...
If it's possible for the CPU to be faulty, I am actually already thinking about buying a new MB(for overclocking) and if so, they got CPU bundles I might as well pursue... Any one else having such issues?

More about : bsod

November 17, 2010 11:22:04 AM

startup, F8, disable automatic restart, give us the stop code 0x numbers including all in brackets please.
m
0
l
a b à CPUs
November 17, 2010 11:32:30 AM

check temperatures as you start something intensive.
What RAM speed and timings are you using?
m
0
l
Related resources
November 17, 2010 11:43:39 AM

Everything is stock. So slow 6GB 1066 MHZ DDR 3 RAM. Can't overclock anything with Dell motherboard... Timings i am not sure of... And as far as temps, I never checked CPU temps but the GPU i did and all is fine. I can actually hear the stock processor fan start blowing faster as things get more intense. I will also disable automatic restart and get you the code after work... sigh...
m
0
l
November 17, 2010 4:47:34 PM

To be more specific, i am getting both "machine_check exception", and "a clock interupt was not received on a secondary processor within the specified interval".

BugCheck 124, {0, fffffa80053d6028, be000000, 800400}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80053d6028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

STACK_TEXT:
fffff880`02f6bb58 fffff800`03204903 : 00000000`00000124 00000000`00000000 fffffa80`053d6028 00000000`be000000 : nt!KeBugCheckEx
fffff880`02f6bb60 fffff800`02d9c4d3 : 00000000`00000001 fffffa80`053dda60 00000000`00000000 fffffa80`053ddab0 : hal!HalBugCheckSystem+0x1e3
fffff880`02f6bba0 fffff800`032045c8 : 00000000`00000728 fffffa80`053dda60 fffff880`02f6bf30 fffff880`02f6bf00 : nt!WheaReportHwError+0x263
fffff880`02f6bc00 fffff800`03203f1a : fffffa80`053dda60 fffff880`02f6bf30 fffffa80`053dda60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02f6bd50 fffff800`03203dd5 : 00000000`00000008 00000000`00000001 fffff880`02f6bfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02f6bd90 fffff800`031f7e88 : 00000000`00000000 fffff880`02f63180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`02f6bdc0 fffff800`02c84eac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02f6bdf0 fffff800`02c84d13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02f6bf30 fffff880`0121d8a2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`02f8bc38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!ReadIoMemRaw+0x26


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

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

2: kd> lmvm hardware
start end module name
m
0
l
!