Windows Keeps Crashing - Blue Screen of Death! Please help

[pbd22]

Hi.

My computer keeps crashing. I think it is overclocking but I can't
quite tell.
I have tried -

1) adding more heatsink compound.
2) leaving the chasis door open
3) adding new fans (I have about 8 in / around the mobo).

I have two CPUs in an ASUS mobo. Here are my BIOS temp
readings:

CPU1 Temp: 59*c/138*f
CPU2 Temp 60*c/140*f
MB Temp 47*c/116.5*f

Here is the Dump analysis:

----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 0b290060
PfnDataBase 817a5000
PsLoadedModuleList 8055c700
PsActiveProcessHead 805627b8
MachineImageType 0000014c
NumberProcessors 00000004
BugCheckCode 000000f4
BugCheckParameter1 00000003
BugCheckParameter2 8a335890
BugCheckParameter3 8a335a04
BugCheckParameter4 805d1204
PaeEnabled 00000001
KdDebuggerDataBlock 8054c2e0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00000398
DriverListOffset 00002fa8
DriverCount 00000089
StringPoolOffset 00005858
StringPoolSize 000012d0
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack ba9b7c68
DebuggerDataOffset 00002d18
DebuggerDataSize 00000290
DataBlocksOffset 00006b28
DataBlocksCount 00000005


Windows XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86
compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Mar 24 13:47:31 2009
System Uptime: 0 days 0:05:18
start end module name
804d7000 806e2000 nt Checksum: 001FA9E1 Timestamp: Thu
Aug 14 04:22:02 2008 (48A3F93A)

Unloaded modules:
b82e5000 b830f000 kmixer.sys Timestamp: unavailable (00000000)
b8851000 b887b000 kmixer.sys Timestamp: unavailable (00000000)
b92f9000 b92fa000 drmkaud.sys Timestamp: unavailable (00000000)
b887b000 b889e000 aec.sys Timestamp: unavailable (00000000)
b8a6d000 b8a7a000 DMusic.sys Timestamp: unavailable (00000000)
b8a7d000 b8a8b000 swmidi.sys Timestamp: unavailable (00000000)
badfe000 bae00000 splitter.sys Timestamp: unavailable (00000000)
baa88000 baa95000 i8042prt.sys Timestamp: unavailable (00000000)
ba9d8000 ba9e3000 imapi.sys Timestamp: unavailable (00000000)
b9f87000 b9f8b000 kbdhid.sys Timestamp: unavailable (00000000)
bac80000 bac85000 Cdaudio.SYS Timestamp: unavailable (00000000)
b9f8f000 b9f92000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

[LVTravel]

"pbd22" > wrote in message
...
> Hi.
>
> My computer keeps crashing. I think it is overclocking but I can't
> quite tell.
> I have tried -
>
> 1) adding more heatsink compound.
> 2) leaving the chasis door open
> 3) adding new fans (I have about 8 in / around the mobo).
>
> I have two CPUs in an ASUS mobo. Here are my BIOS temp
> readings:
>
> CPU1 Temp: 59*c/138*f
> CPU2 Temp 60*c/140*f
> MB Temp 47*c/116.5*f
>
> Here is the Dump analysis:
>
> ----- 32 bit Kernel Mini Dump Analysis
>
> DUMP_HEADER32:
> MajorVersion 0000000f
> MinorVersion 00000a28
> DirectoryTableBase 0b290060
> PfnDataBase 817a5000
> PsLoadedModuleList 8055c700
> PsActiveProcessHead 805627b8
> MachineImageType 0000014c
> NumberProcessors 00000004
> BugCheckCode 000000f4
> BugCheckParameter1 00000003
> BugCheckParameter2 8a335890
> BugCheckParameter3 8a335a04
> BugCheckParameter4 805d1204
> PaeEnabled 00000001
> KdDebuggerDataBlock 8054c2e0
> MiniDumpFields 00000dff
>
> TRIAGE_DUMP32:
> ServicePackBuild 00000200
> SizeOfDump 00010000
> ValidOffset 0000fffc
> ContextOffset 00000320
> ExceptionOffset 000007d0
> MmOffset 00001068
> UnloadedDriversOffset 000010a0
> PrcbOffset 00001878
> ProcessOffset 000024c8
> ThreadOffset 00002728
> CallStackOffset 00002980
> SizeOfCallStack 00000398
> DriverListOffset 00002fa8
> DriverCount 00000089
> StringPoolOffset 00005858
> StringPoolSize 000012d0
> BrokenDriverOffset 00000000
> TriageOptions 00000041
> TopOfStack ba9b7c68
> DebuggerDataOffset 00002d18
> DebuggerDataSize 00000290
> DataBlocksOffset 00006b28
> DataBlocksCount 00000005
>
>
> Windows XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86
> compatible
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
> Debug session time: Tue Mar 24 13:47:31 2009
> System Uptime: 0 days 0:05:18
> start end module name
> 804d7000 806e2000 nt Checksum: 001FA9E1 Timestamp: Thu
> Aug 14 04:22:02 2008 (48A3F93A)
>
> Unloaded modules:
> b82e5000 b830f000 kmixer.sys Timestamp: unavailable (00000000)
> b8851000 b887b000 kmixer.sys Timestamp: unavailable (00000000)
> b92f9000 b92fa000 drmkaud.sys Timestamp: unavailable (00000000)
> b887b000 b889e000 aec.sys Timestamp: unavailable (00000000)
> b8a6d000 b8a7a000 DMusic.sys Timestamp: unavailable (00000000)
> b8a7d000 b8a8b000 swmidi.sys Timestamp: unavailable (00000000)
> badfe000 bae00000 splitter.sys Timestamp: unavailable (00000000)
> baa88000 baa95000 i8042prt.sys Timestamp: unavailable (00000000)
> ba9d8000 ba9e3000 imapi.sys Timestamp: unavailable (00000000)
> b9f87000 b9f8b000 kbdhid.sys Timestamp: unavailable (00000000)
> bac80000 bac85000 Cdaudio.SYS Timestamp: unavailable (00000000)
> b9f8f000 b9f92000 Sfloppy.SYS Timestamp: unavailable (00000000)
>
> Finished dump check

The code on the blue screen and the other information would help us to help
you more than the crash dump.

Also, if the unit was overheating normally you don't get a blue screen, you
get a total shutdown with a possible reboot.

Has system always blue screened or has this started since changing
something?

Does system work OK if you stop the overclocking?

[pbd22]

Thanks for the reply.
Yes, I have been trying to capture the blue screen information as, I
agree, this is the most
useful info. Unfortunately it flickers the blue screen for a tenth of
a second and then reboots
itself. I am trying to find a setting that says something to the
effect of "don't reboot on error"
but don't know if it exists?

The only thing I have recently changed is the addition of an 8 port
switch (replacing a 4). Despite
my feeling that this is completely irrelevant, I have tried a boot
with my network unplugged and
get the same error.

Stopping overclocking sounds like a good test. I'll look into how to
do that and report back. If you
know how to capture my "blue screen" info prior to the reboot, that
would be most helpful.

Thanks.

[Paul]

pbd22 wrote:
> Thanks for the reply.
> Yes, I have been trying to capture the blue screen information as, I
> agree, this is the most
> useful info. Unfortunately it flickers the blue screen for a tenth of
> a second and then reboots
> itself. I am trying to find a setting that says something to the
> effect of "don't reboot on error"
> but don't know if it exists?
>
> The only thing I have recently changed is the addition of an 8 port
> switch (replacing a 4). Despite
> my feeling that this is completely irrelevant, I have tried a boot
> with my network unplugged and
> get the same error.
>
> Stopping overclocking sounds like a good test. I'll look into how to
> do that and report back. If you
> know how to capture my "blue screen" info prior to the reboot, that
> would be most helpful.
>
> Thanks.

Control Panels : System : Advanced : Startup and Recovery : Settings

Untick "Automatically restart"

Click OK.

Paul

[Unknown]

Do you know what overclocking is?
"Paul" > wrote in message
...
> pbd22 wrote:
>> Thanks for the reply.
>> Yes, I have been trying to capture the blue screen information as, I
>> agree, this is the most
>> useful info. Unfortunately it flickers the blue screen for a tenth of
>> a second and then reboots
>> itself. I am trying to find a setting that says something to the
>> effect of "don't reboot on error"
>> but don't know if it exists?
>>
>> The only thing I have recently changed is the addition of an 8 port
>> switch (replacing a 4). Despite
>> my feeling that this is completely irrelevant, I have tried a boot
>> with my network unplugged and
>> get the same error.
>>
>> Stopping overclocking sounds like a good test. I'll look into how to
>> do that and report back. If you
>> know how to capture my "blue screen" info prior to the reboot, that
>> would be most helpful.
>>
>> Thanks.
>
> Control Panels : System : Advanced : Startup and Recovery : Settings
>
> Untick "Automatically restart"
>
> Click OK.
>
> Paul

[Paul]

Unknown wrote:
> Do you know what overclocking is?

"Stopping overclocking sounds like a good test."

That means the OP is headed in the right direction :-)
What more can you say ?

Overclocks are subject to electromigration failure, and
there have been reports in the past, of steadily decreasing
stable operating frequency. But this is information an
overclocker would get from an enthusiast site and forum.
I've even seen symptoms of this, on a P4.

http://en.wikipedia.org/wiki/Electromigration

Paul

> "Paul" > wrote in message
> ...
>> pbd22 wrote:
>>> Thanks for the reply.
>>> Yes, I have been trying to capture the blue screen information as, I
>>> agree, this is the most
>>> useful info. Unfortunately it flickers the blue screen for a tenth of
>>> a second and then reboots
>>> itself. I am trying to find a setting that says something to the
>>> effect of "don't reboot on error"
>>> but don't know if it exists?
>>>
>>> The only thing I have recently changed is the addition of an 8 port
>>> switch (replacing a 4). Despite
>>> my feeling that this is completely irrelevant, I have tried a boot
>>> with my network unplugged and
>>> get the same error.
>>>
>>> Stopping overclocking sounds like a good test. I'll look into how to
>>> do that and report back. If you
>>> know how to capture my "blue screen" info prior to the reboot, that
>>> would be most helpful.
>>>
>>> Thanks.
>> Control Panels : System : Advanced : Startup and Recovery : Settings
>>
>> Untick "Automatically restart"
>>
>> Click OK.
>>
>> Paul
>
>

[Unknown]

Point is, OP should KNOW if he is overclocking or not. (Unless he bought a
used computer).
"Paul" > wrote in message
...
> Unknown wrote:
>> Do you know what overclocking is?
>
> "Stopping overclocking sounds like a good test."
>
> That means the OP is headed in the right direction :-)
> What more can you say ?
>
> Overclocks are subject to electromigration failure, and
> there have been reports in the past, of steadily decreasing
> stable operating frequency. But this is information an
> overclocker would get from an enthusiast site and forum.
> I've even seen symptoms of this, on a P4.
>
> http://en.wikipedia.org/wiki/Electromigration
>
> Paul
>
>> "Paul" > wrote in message
>> ...
>>> pbd22 wrote:
>>>> Thanks for the reply.
>>>> Yes, I have been trying to capture the blue screen information as, I
>>>> agree, this is the most
>>>> useful info. Unfortunately it flickers the blue screen for a tenth of
>>>> a second and then reboots
>>>> itself. I am trying to find a setting that says something to the
>>>> effect of "don't reboot on error"
>>>> but don't know if it exists?
>>>>
>>>> The only thing I have recently changed is the addition of an 8 port
>>>> switch (replacing a 4). Despite
>>>> my feeling that this is completely irrelevant, I have tried a boot
>>>> with my network unplugged and
>>>> get the same error.
>>>>
>>>> Stopping overclocking sounds like a good test. I'll look into how to
>>>> do that and report back. If you
>>>> know how to capture my "blue screen" info prior to the reboot, that
>>>> would be most helpful.
>>>>
>>>> Thanks.
>>> Control Panels : System : Advanced : Startup and Recovery : Settings
>>>
>>> Untick "Automatically restart"
>>>
>>> Click OK.
>>>
>>> Paul
>>

[Pauli Taglia[_2_]]

"Unknown" > wrote:

>Point is, OP should KNOW if he is overclocking or not. (Unless he bought a
>used computer).

Or a custom-built gaming machine that came with overclocking preset.


>"Paul" > wrote in message
...
>> Unknown wrote:
>>> Do you know what overclocking is?
>>
>> "Stopping overclocking sounds like a good test."
>>
>> That means the OP is headed in the right direction :-)
>> What more can you say ?
>>
>> Overclocks are subject to electromigration failure, and
>> there have been reports in the past, of steadily decreasing
>> stable operating frequency. But this is information an
>> overclocker would get from an enthusiast site and forum.
>> I've even seen symptoms of this, on a P4.
>>
>> http://en.wikipedia.org/wiki/Electromigration
>>
>> Paul
>>
>>> "Paul" > wrote in message
>>> ...
>>>> pbd22 wrote:
>>>>> Thanks for the reply.
>>>>> Yes, I have been trying to capture the blue screen information as, I
>>>>> agree, this is the most
>>>>> useful info. Unfortunately it flickers the blue screen for a tenth of
>>>>> a second and then reboots
>>>>> itself. I am trying to find a setting that says something to the
>>>>> effect of "don't reboot on error"
>>>>> but don't know if it exists?
>>>>>
>>>>> The only thing I have recently changed is the addition of an 8 port
>>>>> switch (replacing a 4). Despite
>>>>> my feeling that this is completely irrelevant, I have tried a boot
>>>>> with my network unplugged and
>>>>> get the same error.
>>>>>
>>>>> Stopping overclocking sounds like a good test. I'll look into how to
>>>>> do that and report back. If you
>>>>> know how to capture my "blue screen" info prior to the reboot, that
>>>>> would be most helpful.
>>>>>
>>>>> Thanks.
>>>> Control Panels : System : Advanced : Startup and Recovery : Settings
>>>>
>>>> Untick "Automatically restart"
>>>>
>>>> Click OK.
>>>>
>>>> Paul
>>>

[pbd22]

On Mar 25, 2:16*pm, Pauli Taglia > wrote:
> "Unknown" > wrote:
> >Point is, OP should KNOW if he is overclocking or not. (Unless he bought a
> >used computer).
>
> Or a custom-built gaming machine that came with overclocking preset.
>
>
>
> >"Paul" > wrote in message
> ...
> >> Unknown wrote:
> >>> Do you know what overclocking is?
>
> >> "Stopping overclocking sounds like a good test."
>
> >> That means the OP is headed in the right direction :-)
> >> What more can you say ?
>
> >> Overclocks are subject to electromigration failure, and
> >> there have been reports in the past, of steadily decreasing
> >> stable operating frequency. But this is information an
> >> overclocker would get from an enthusiast site and forum.
> >> I've even seen symptoms of this, on a P4.
>
> >>http://en.wikipedia.org/wiki/Electromigration
>
> >> * *Paul
>
> >>> "Paul" > wrote in message
> ...
> >>>> pbd22 wrote:
> >>>>> Thanks for the reply.
> >>>>> Yes, I have been trying to capture the blue screen information as, I
> >>>>> agree, this is the most
> >>>>> useful info. Unfortunately it flickers the blue screen for a tenth of
> >>>>> a second and then reboots
> >>>>> itself. I am trying to find a setting that says something to the
> >>>>> effect of "don't reboot on error"
> >>>>> but don't know if it exists?
>
> >>>>> The only thing I have recently changed is the addition of an 8 port
> >>>>> switch (replacing a 4). Despite
> >>>>> my feeling that this is completely irrelevant, I have tried a boot
> >>>>> with my network unplugged and
> >>>>> get the same error.
>
> >>>>> Stopping overclocking sounds like a good test. I'll look into how to
> >>>>> do that and report back. If you
> >>>>> know how to capture my "blue screen" info prior to the reboot, that
> >>>>> would be most helpful.
>
> >>>>> Thanks.
> >>>> Control Panels : System : Advanced : Startup and Recovery : Settings
>
> >>>> * *Untick "Automatically restart"
>
> >>>> Click OK.
>
> >>>> * *Paul- Hide quoted text -
>
> - Show quoted text -

Paul - thanks for pointing that out.

The error is: 0x000000F4.

I have done some hard disk checks and am starting to think
that my hard drive needs to be replaced but its odd b/c everything
was working fine and then went haywire all of a sudden.

I have tried removing all but one memory card, disconnecting all
peripherials, checking to make sure my HDD is in "master" setting
(installing the OS on a slave HDD seems to cause this error) and
the error still occurs.

I know what overclocking is. To Pauli's point - this is an ASUS
gaming system with everything preset for gaming. I was wondering if
the
overclocking preset might have been overheating some components and
causing the stop error. I think this is a resonable train of thought.

Pauli, Paul, or LVTravel - if you have further suggestions, I am all
ears.

Thanks.

[Paul]

pbd22 wrote:

>
> Paul - thanks for pointing that out.
>
> The error is: 0x000000F4.
>
> I have done some hard disk checks and am starting to think
> that my hard drive needs to be replaced but its odd b/c everything
> was working fine and then went haywire all of a sudden.
>
> I have tried removing all but one memory card, disconnecting all
> peripherials, checking to make sure my HDD is in "master" setting
> (installing the OS on a slave HDD seems to cause this error) and
> the error still occurs.
>
> I know what overclocking is. To Pauli's point - this is an ASUS
> gaming system with everything preset for gaming. I was wondering if
> the
> overclocking preset might have been overheating some components and
> causing the stop error. I think this is a resonable train of thought.
>
> Pauli, Paul, or LVTravel - if you have further suggestions, I am all
> ears.
>
> Thanks.

That's weird. There was a report of one of those yesterday.

http://aumha.org/a/stop.htm

0x000000F4: CRITICAL_OBJECT_TERMINATION

It seems relatively obscure, but search on the 0x000000F4 and
see if there are more of them lately. Maybe this is related
to some recent update or something you added to the system.

Paul

[pbd22]

Thanks Paul.

This issue was resolved by reinstalling my mobo drivers.
A recent MS update may have thrown something off -
not sure what happened there. But, after reinstalling my
mobo drivers the system has been very stable.

Problem solved - thanks for your help.

Peter