Microsoft Windows Vista Community Forums - Vistaheads
Recommended Download



Welcome to the Microsoft Windows Vista Community Forums - Vistaheads, YOUR Largest Resource for Windows Vista related information.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so , join our community today!

If you have any problems with the registration process or your account login, please contact us.

Driver Scanner

bluescreen

microsoft.public.it.windows.vista






Speedup My PC
Reply
  #1 (permalink)  
Old 02-18-2009
Lino
 

Posts: n/a
bluescreen
Un mio amico ha un pc con il siustema operativo vista. Gli continua a dare
delle schermate blu, mentre sta lavorando in qualsiasi programma o collegato
ad internet.
Quando dÃ* il problema con la schermata blu il pc non si avvia subbito ma
dopo vario tentativi si riavvia.
Mi sono fatto mandare il file "dmp", e dal mio pc ho visto il file, da
quanto ho notato mi risulta problema harware.
Allego il test:
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\Mini021809-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Inaccessible path: 'c:\windows\i386'
Symbol search path is:
srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2
procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x81c49000 PsLoadedModuleList = 0x81d60c70
Debug session time: Wed Feb 18 11:15:15.583 2009 (GMT+1)
System Uptime: 0 days 0:11:45.304
Loading Kernel Symbols
.................................................. ..............
.................................................. ...............
.....
Loading User Symbols
Loading unloaded module list
.....
************************************************** *****************************
*
*
* Bugcheck Analysis
*
*
*
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 85d97020, b2000040, 800}

************************************************** ***********************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR
***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
************************************************** ***********************
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, Machine Check Exception
Arg2: 85d97020, Address of the WHEA_ERROR_RECORD structure.
Arg3: b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 00000800, Low order 32-bits of the MCi_STATUS value.

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

************************************************** ***********************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR
***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
************************************************** ***********************

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 7

STACK_TEXT:
81d3bf38 81c1c8b5 00000124 00000000 85d97020 nt!KeBugCheckEx+0x1e
81d3bf8c 81d09928 85d97020 847b4818 847b4818 hal!HalBugCheckSystem+0xe1
81d3bfb8 81c1c7c9 847b4818 00000000 81d3bff4 nt!WheaReportHwError+0x1d0
81d3bfc8 81c1cea7 00000003 847b4818 00000000 hal!HalpReportMachineCheck+0x31
81d3bff4 81c1899f 80154000 00000000 00000000 hal!HalpMcaExceptionHandler+0xf7
81d3bff4 00000000 80154000 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_GenuineIntel__UNKNOWN

BUCKET_ID: 0x124_GenuineIntel__UNKNOWN

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, Machine Check Exception
Arg2: 85d97020, Address of the WHEA_ERROR_RECORD structure.
Arg3: b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 00000800, Low order 32-bits of the MCi_STATUS value.

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

************************************************** ***********************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR
***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
************************************************** ***********************

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 7

STACK_TEXT:
81d3bf38 81c1c8b5 00000124 00000000 85d97020 nt!KeBugCheckEx+0x1e
81d3bf8c 81d09928 85d97020 847b4818 847b4818 hal!HalBugCheckSystem+0xe1
81d3bfb8 81c1c7c9 847b4818 00000000 81d3bff4 nt!WheaReportHwError+0x1d0
81d3bfc8 81c1cea7 00000003 847b4818 00000000 hal!HalpReportMachineCheck+0x31
81d3bff4 81c1899f 80154000 00000000 00000000 hal!HalpMcaExceptionHandler+0xf7
81d3bff4 00000000 80154000 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_GenuineIntel__UNKNOWN

BUCKET_ID: 0x124_GenuineIntel__UNKNOWN

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

Mi potete dare altre indicazioni, grazie

Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 02-18-2009
Elvis
 

Posts: n/a
Re: bluescreen
ciao
scarica questo

http://pharry.eu/data/ubcd411.iso

fatti un cd e fallo partire dal boot di avvio.

seleziona i componenti desiderati per il test (es. hard disk e ram)

fai sapere

ps. i driver del computer sono tutti aggiornati?

"Lino" <Lino@discussions.microsoft.com> ha scritto nel messaggio
news:0BC97A0D-F771-4286-96FD-4BA63243372E@microsoft.com...
> Un mio amico ha un pc con il siustema operativo vista. Gli continua a dare
> delle schermate blu, mentre sta lavorando in qualsiasi programma o
> collegato
> ad internet.
> Quando dÃ* il problema con la schermata blu il pc non si avvia subbito ma
> dopo vario tentativi si riavvia.
> Mi sono fatto mandare il file "dmp", e dal mio pc ho visto il file, da
> quanto ho notato mi risulta problema harware.
> Allego il test:
> Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [c:\Mini021809-01.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> WARNING: Inaccessible path: 'c:\windows\i386'
> Symbol search path is:
> srv*c:\symbols*http://msdl.microsoft.com/download/symbols
> Executable search path is: c:\windows\i386
> Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP
> (2
> procs) Free x86 compatible
> Product: WinNt, suite: TerminalServer SingleUserTS Personal
> Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
> Machine Name:
> Kernel base = 0x81c49000 PsLoadedModuleList = 0x81d60c70
> Debug session time: Wed Feb 18 11:15:15.583 2009 (GMT+1)
> System Uptime: 0 days 0:11:45.304
> Loading Kernel Symbols
> .................................................. .............
> .................................................. ..............
> ....
> Loading User Symbols
> Loading unloaded module list
> ....
> ************************************************** *****************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> ************************************************** *****************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 124, {0, 85d97020, b2000040, 800}
>
> ************************************************** ***********************
> *** ***
> *** ***
> *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
> *** ***
> ************************************************** ***********************
> ************************************************** ***********************
> *** ***
> *** ***
> *** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR
> ***
> *** ***
> ************************************************** ***********************
> ************************************************** ***********************
> *** ***
> *** ***
> *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
> *** ***
> ************************************************** ***********************
> ************************************************** ***********************
> *** ***
> *** ***
> *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
> *** ***
> ************************************************** ***********************
> ************************************************** ***********************
> *** ***
> *** ***
> *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
> *** ***
> ************************************************** ***********************
> 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, Machine Check Exception
> Arg2: 85d97020, Address of the WHEA_ERROR_RECORD structure.
> Arg3: b2000040, High order 32-bits of the MCi_STATUS value.
> Arg4: 00000800, Low order 32-bits of the MCi_STATUS value.
>
> Debugging Details:
> ------------------
>
> ************************************************** ***********************
> *** ***
> *** ***
> *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
> *** ***
> ************************************************** ***********************
> ************************************************** ***********************
> *** ***
> *** ***
> *** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR
> ***
> *** ***
> ************************************************** ***********************
> ************************************************** ***********************
> *** ***
> *** ***
> *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
> *** ***
> ************************************************** ***********************
> ************************************************** ***********************
> *** ***
> *** ***
> *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
> *** ***
> ************************************************** ***********************
> ************************************************** ***********************
> *** ***
> *** ***
> *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
> *** ***
> ************************************************** ***********************
>
> BUGCHECK_STR: 0x124_GenuineIntel
>
> CUSTOMER_CRASH_COUNT: 1
>
> DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
>
> PROCESS_NAME: System
>
> CURRENT_IRQL: 7
>
> STACK_TEXT:
> 81d3bf38 81c1c8b5 00000124 00000000 85d97020 nt!KeBugCheckEx+0x1e
> 81d3bf8c 81d09928 85d97020 847b4818 847b4818 hal!HalBugCheckSystem+0xe1
> 81d3bfb8 81c1c7c9 847b4818 00000000 81d3bff4 nt!WheaReportHwError+0x1d0
> 81d3bfc8 81c1cea7 00000003 847b4818 00000000
> hal!HalpReportMachineCheck+0x31
> 81d3bff4 81c1899f 80154000 00000000 00000000
> hal!HalpMcaExceptionHandler+0xf7
> 81d3bff4 00000000 80154000 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_GenuineIntel__UNKNOWN
>
> BUCKET_ID: 0x124_GenuineIntel__UNKNOWN
>
> 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, Machine Check Exception
> Arg2: 85d97020, Address of the WHEA_ERROR_RECORD structure.
> Arg3: b2000040, High order 32-bits of the MCi_STATUS value.
> Arg4: 00000800, Low order 32-bits of the MCi_STATUS value.
>
> Debugging Details:
> ------------------
>
> ************************************************** ***********************
> *** ***
> *** ***
> *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
> *** ***
> ************************************************** ***********************
> ************************************************** ***********************
> *** ***
> *** ***
> *** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR
> ***
> *** ***
> ************************************************** ***********************
> ************************************************** ***********************
> *** ***
> *** ***
> *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
> *** ***
> ************************************************** ***********************
> ************************************************** ***********************
> *** ***
> *** ***
> *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
> *** ***
> ************************************************** ***********************
> ************************************************** ***********************
> *** ***
> *** ***
> *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
> *** ***
> ************************************************** ***********************
>
> BUGCHECK_STR: 0x124_GenuineIntel
>
> CUSTOMER_CRASH_COUNT: 1
>
> DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
>
> PROCESS_NAME: System
>
> CURRENT_IRQL: 7
>
> STACK_TEXT:
> 81d3bf38 81c1c8b5 00000124 00000000 85d97020 nt!KeBugCheckEx+0x1e
> 81d3bf8c 81d09928 85d97020 847b4818 847b4818 hal!HalBugCheckSystem+0xe1
> 81d3bfb8 81c1c7c9 847b4818 00000000 81d3bff4 nt!WheaReportHwError+0x1d0
> 81d3bfc8 81c1cea7 00000003 847b4818 00000000
> hal!HalpReportMachineCheck+0x31
> 81d3bff4 81c1899f 80154000 00000000 00000000
> hal!HalpMcaExceptionHandler+0xf7
> 81d3bff4 00000000 80154000 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_GenuineIntel__UNKNOWN
>
> BUCKET_ID: 0x124_GenuineIntel__UNKNOWN
>
> Followup: MachineOwner
> ---------
>
> Mi potete dare altre indicazioni, grazie
>

Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Bluescreen Elsharif microsoft.public.windows.vista.general 2 09-23-2008 03:40
Bluescreen Peter Schultz microsoft.public.de.windows.vista.sonstiges 7 04-13-2008 22:19
bluescreen baga microsoft.public.it.windows.vista 12 01-08-2008 21:11
BlueScreen Nourredine SEDDIKI microsoft.public.de.windows.vista.multimedia 0 09-14-2007 22:52




All times are GMT +1. The time now is 23:24.




Driver Scanner - Free Scan Now

Vistaheads.com is part of the Heads Network. See also XPHeads.com , Win7Heads.com and Win8Heads.com.


Design by Vjacheslav Trushkin for phpBBStyles.com.
Powered by vBulletin® Version 3.6.7
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.6.0 RC 2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120