Vista BSOD

[Robert]

I have some regular BSOD crashes in Vista x86 (once a day)
They are not heat related. Temperatures of the CPU and GPU are fine.
I also used memtest, prime95 torture test and 3dmark 2005, but get no
errors. I also can play 3D games for hours without problems.
The crashes usually occur when doing something quite simple, like
opening a new window.

When I get a crash I often see that the harddisk led keeps burning and
Vista is unable to write the dump file (no warning, but nothing happens).
The BSOD alyways contains this error:

STOP: 0x00000124 (0x00000000, 0x866C6440, B2000000, 0X00070F0F)

When the BSOD did manage to make a dump I used the Windows Debugger to
get the following information.
Any suggestions are welcome.

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


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

Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Kernel base = 0x82000000 PsLoadedModuleList = 0x82111db0
Debug session time: Tue Jul 17 20:37:02.965 2007 (GMT+2)
System Uptime: 0 days 2:36:02.554
Loading Kernel Symbols
...........................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
...................................................
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 866c6440, b2000000, 70f0f}

Probably caused by : hardware

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

0: 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: 00000000, MCA_ASSERT
Arg2: 866c6440, Address of WHEA_ERROR_RECORD structure
Arg3: b2000000, High 32 bits of MCi_STATUS MSR for the MCA bank that had
the error
Arg4: 00070f0f, Low 32 bits of MCi_STATUS MSR for the MCA bank that had
the error

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


WHEA_ERROR_RECORD: !errrec ffffffff866c6440

BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: Idle

CURRENT_IRQL: 1c

STACK_TEXT:
820eef84 823a6e93 00000124 00000000 866c6440 nt!KeBugCheckEx+0x1e
820eefa0 820cecb6 866c6440 866c7ad8 00000001 hal!HalBugCheckSystem+0x37
820eefc0 823a6e52 866c7ad8 866c7bf0 820eeff4 nt!WheaReportHwError+0x10c
820eefd0 823a6f73 00000003 866c7ad8 00000000 hal!HalpReportMachineCheck+0x28
820eeff4 823a389f 80156000 00000000 00000000
hal!HalpMcaExceptionHandler+0xc3
820eeff4 00000000 80156000 00000000 00000000
hal!HalpMcaExceptionHandlerWrapper+0x77


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x124_AuthenticAMD

BUCKET_ID: 0x124_AuthenticAMD

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

 

[Michael Solomon]

"Robert" <noreply@news.xxx> wrote in message
news:469d1cbd$0$337$e4fe514c@news.xs4all.nl...
>I have some regular BSOD crashes in Vista x86 (once a day)
> They are not heat related. Temperatures of the CPU and GPU are fine.
> I also used memtest, prime95 torture test and 3dmark 2005, but get no
> errors. I also can play 3D games for hours without problems.
> The crashes usually occur when doing something quite simple, like opening
> a new window.
>
> When I get a crash I often see that the harddisk led keeps burning and
> Vista is unable to write the dump file (no warning, but nothing happens).
> The BSOD alyways contains this error:
>
> STOP: 0x00000124 (0x00000000, 0x866C6440, B2000000, 0X00070F0F)
>
> When the BSOD did manage to make a dump I used the Windows Debugger to get
> the following information.
> Any suggestions are welcome.
>
> Microsoft (R) Windows Debugger Version 6.7.0005.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\Windows\Minidump\Mini071707-01.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is:
> SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
> Executable search path is:
> Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
> Product: WinNt, suite: TerminalServer SingleUserTS
> Built by: 6000.16386.x86fre.vista_rtm.061101-2205
> Kernel base = 0x82000000 PsLoadedModuleList = 0x82111db0
> Debug session time: Tue Jul 17 20:37:02.965 2007 (GMT+2)
> System Uptime: 0 days 2:36:02.554
> Loading Kernel Symbols
> ..........................................................................................................................................................................
> Loading User Symbols
> Loading unloaded module list
> ..................................................
> *******************************************************************************
> * *
> * Bugcheck Analysis *
> * *
> *******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 124, {0, 866c6440, b2000000, 70f0f}
>
> Probably caused by : hardware
>
> Followup: MachineOwner
> ---------
>
> 0: 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: 00000000, MCA_ASSERT
> Arg2: 866c6440, Address of WHEA_ERROR_RECORD structure
> Arg3: b2000000, High 32 bits of MCi_STATUS MSR for the MCA bank that had
> the error
> Arg4: 00070f0f, Low 32 bits of MCi_STATUS MSR for the MCA bank that had
> the error
>
> Debugging Details:
> ------------------
>
>
> WHEA_ERROR_RECORD: !errrec ffffffff866c6440
>
> BUGCHECK_STR: 0x124_AuthenticAMD
>
> CUSTOMER_CRASH_COUNT: 1
>
> DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
>
> PROCESS_NAME: Idle
>
> CURRENT_IRQL: 1c
>
> STACK_TEXT:
> 820eef84 823a6e93 00000124 00000000 866c6440 nt!KeBugCheckEx+0x1e
> 820eefa0 820cecb6 866c6440 866c7ad8 00000001 hal!HalBugCheckSystem+0x37
> 820eefc0 823a6e52 866c7ad8 866c7bf0 820eeff4 nt!WheaReportHwError+0x10c
> 820eefd0 823a6f73 00000003 866c7ad8 00000000
> hal!HalpReportMachineCheck+0x28
> 820eeff4 823a389f 80156000 00000000 00000000
> hal!HalpMcaExceptionHandler+0xc3
> 820eeff4 00000000 80156000 00000000 00000000
> hal!HalpMcaExceptionHandlerWrapper+0x77
>
>
> STACK_COMMAND: kb
>
> FOLLOWUP_NAME: MachineOwner
>
> MODULE_NAME: hardware
>
> IMAGE_NAME: hardware
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 0
>
> FAILURE_BUCKET_ID: 0x124_AuthenticAMD
>
> BUCKET_ID: 0x124_AuthenticAMD
>
> Followup: MachineOwner
> ---------
First thing I would go would be to go to your hard drive manufacturer's
website, download their diagnostic tools, create their diagnostic disk as
usually instructed, boot from it and run their disk diagnostic. If that
checks out, make the websites of various manufacturer's of your hardware
devices, graphics card, soundcard, any other internal and external devices,
for the latest Vista compatible drivers.
--
Michael Solomon
Backup is a PC user's best friend
DTS-L.Org: http://www.dts-l.org/

 

[Lang Murphy]

"Robert" <noreply@news.xxx> wrote in message
news:469d1cbd$0$337$e4fe514c@news.xs4all.nl...
>I have some regular BSOD crashes in Vista x86 (once a day)
> They are not heat related. Temperatures of the CPU and GPU are fine.
> I also used memtest, prime95 torture test and 3dmark 2005, but get no
> errors. I also can play 3D games for hours without problems.
> The crashes usually occur when doing something quite simple, like opening
> a new window.
>
> When I get a crash I often see that the harddisk led keeps burning and
> Vista is unable to write the dump file (no warning, but nothing happens).
> The BSOD alyways contains this error:
>
> STOP: 0x00000124 (0x00000000, 0x866C6440, B2000000, 0X00070F0F)
>
> When the BSOD did manage to make a dump I used the Windows Debugger to get
> the following information.
> Any suggestions are welcome.
>

<snip>

> BugCheck 124, {0, 866c6440, b2000000, 70f0f}
>
> Probably caused by : hardware
>

<snip>

Googled your STOP number and found this -possible- solution. Not saying it
will fix it whatsoever, but give it a shot. If it works, sounds like it may
actually be a BIOS issue. Whether one can really consider that a hw issue...
dunno.

"In your BIOS try dis-abling the duel core technology. I had an animation
program running very choppy on my Core 2 Duo untill I disabled the duel core
and then all was good."

Good luck!

Lang

 

[Robert]

>> ---------
> First thing I would go would be to go to your hard drive manufacturer's
> website, download their diagnostic tools, create their diagnostic disk
> as usually instructed, boot from it and run their disk diagnostic. If
> that checks out, make the websites of various manufacturer's of your
> hardware devices, graphics card, soundcard, any other internal and
> external devices, for the latest Vista compatible drivers.

I have the latest BIOS and drivers for all my hardware components.
The only problem is that Nvidia never made any nforce drivers for my
nforce4 ultra that work well. So I am still using the default vista drivers.

I was just hoping if something can be seen from the debug info that
would point to a specific hardware component so I would know which
driver is the culprit.

The prime suspect for me is that NVidia SATA raid controller, but have
no way to confirm this.

 

[Michael Solomon]

"Robert" <noreply@news.xxx> wrote in message
news:469e6340$0$331$e4fe514c@news.xs4all.nl...
>>> ---------
>> First thing I would go would be to go to your hard drive manufacturer's
>> website, download their diagnostic tools, create their diagnostic disk as
>> usually instructed, boot from it and run their disk diagnostic. If that
>> checks out, make the websites of various manufacturer's of your hardware
>> devices, graphics card, soundcard, any other internal and external
>> devices, for the latest Vista compatible drivers.
>
> I have the latest BIOS and drivers for all my hardware components.
> The only problem is that Nvidia never made any nforce drivers for my
> nforce4 ultra that work well. So I am still using the default vista
> drivers.
>
> I was just hoping if something can be seen from the debug info that would
> point to a specific hardware component so I would know which driver is the
> culprit.
>
> The prime suspect for me is that NVidia SATA raid controller, but have no
> way to confirm this.
I'd say that controller is a likely candidate but I am still suspicious of
the fact no report was written to the hard drive. That may be a symptom of
the problem and while you've not mentioned other errors indicating
read/write issues, I'd check the health of the hard drive with the
manufacturer's disk tools to rule that out. If all is fine, I can tell you
we've seen a number of issues with regard to various nVidia hardware that
trace back to the lack of drivers or no more driver support.

--
Michael Solomon
Backup is a PC user's best friend
DTS-L.Org: http://www.dts-l.org/