|
|||||||
|
|
|
 |
|
|
Strumenti |
15-04-2012, 13:29
|
#1761 |
|
Senior Member
Iscritto dal: Oct 2006
Città: Colloredo di Monte Albano-UDINE-(FRIULI)
Messaggi: 1605
|
Scusate ma non ci capisco niente,potrebbe essere la cpu andata?
__________________
CASE NZXT H6 / Motherboard Aorus B650 Elite / CPU AMD Ryzen 7800X3D cooled with Noctua NH-U12A Chromax Black / RAM 32 GB G-Skill Trident Z DDR5 6000 Mhz / SSD Samsung 980 PRO / VGA Palit Games Rock 4070 Ti / MONITOR Msi MAG 271Q OLED / |
|
|
|
15-04-2012, 21:44
|
#1762 |
|
Bannato
Iscritto dal: Apr 2012
Messaggi: 3
|
puo darsi sia la ram andata!!!!
Ultima modifica di davide.licausi : 16-04-2012 alle 12:01. |
|
|
|
|
16-04-2012, 14:06
|
#1763 | |
|
Member
Iscritto dal: Mar 2009
Città: Latina
Messaggi: 296
|
Quote:
__________________
Cpu: Amd phenom II X4 955 BE 3.6 ghz + Scythe mugen rev 2 Sc.madre: Asus M4a77td-pro. Ram:8gb corsair vengeance 1600 mhz. Vga: Msi Nvidia gtx 560ti hawk. SSD: Crucial c300 128 gb (sistema). Hard disk: Seagate 1 tera;. Ali: cooler master 460 watts (si, regge a meraviglia). Case: cm 690 nvidia edition. |
|
|
|
|
|
16-04-2012, 16:24
|
#1764 | |
|
Senior Member
Iscritto dal: Oct 2006
Città: Colloredo di Monte Albano-UDINE-(FRIULI)
Messaggi: 1605
|
Quote:
__________________
CASE NZXT H6 / Motherboard Aorus B650 Elite / CPU AMD Ryzen 7800X3D cooled with Noctua NH-U12A Chromax Black / RAM 32 GB G-Skill Trident Z DDR5 6000 Mhz / SSD Samsung 980 PRO / VGA Palit Games Rock 4070 Ti / MONITOR Msi MAG 271Q OLED / |
|
|
|
|
|
16-04-2012, 16:57
|
#1765 |
|
Senior Member
Iscritto dal: Jan 2002
Messaggi: 6044
|
BSOD da DVD
A qualcuno è mai capitato che la copia di un file .avi da un dvd mandasse in crash Win7 al punto da generare una bsod?
|
|
|
|
|
16-04-2012, 20:01
|
#1767 | |
|
Member
Iscritto dal: Mar 2009
Città: Latina
Messaggi: 296
|
Quote:
la prova del nove sarebbe formattare, così riusciresti a capire se il problema sia hardware o software.
__________________
Cpu: Amd phenom II X4 955 BE 3.6 ghz + Scythe mugen rev 2 Sc.madre: Asus M4a77td-pro. Ram:8gb corsair vengeance 1600 mhz. Vga: Msi Nvidia gtx 560ti hawk. SSD: Crucial c300 128 gb (sistema). Hard disk: Seagate 1 tera;. Ali: cooler master 460 watts (si, regge a meraviglia). Case: cm 690 nvidia edition. |
|
|
|
|
|
16-04-2012, 23:03
|
#1768 | |
|
Senior Member
Iscritto dal: Feb 2008
Messaggi: 9598
|
Quote:
|
|
|
|
|
|
16-04-2012, 23:16
|
#1769 | |
|
Bannato
Iscritto dal: Apr 2012
Messaggi: 74
|
Quote:
|
|
|
|
|
|
17-04-2012, 05:59
|
#1770 |
|
Senior Member
Iscritto dal: Aug 2007
Messaggi: 1679
|
da quando ho preso il mio desktop pc (win 7 installato) il poc fa fatica a spengersi o a riavviarsi: dopo essersi disconnesso da win rimane fisso a lungo sulla schermata di win nera che dice
 vado a braccio) Chiusura in corso...pare che il problema a quanto dice Whocrashed risieda nel: ntoskrnl.exe come si risolve il problema? ho aggiornato driver, bios, pulito registro configurazione, etc.... ma il problema spesso si ripresenta (vedere sotto) Codice:
-------------------------------------------------------------------------------- Welcome to WhoCrashed Professional Edition v 3.01 -------------------------------------------------------------------------------- This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution. Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice. This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems. To obtain technical support visit www.resplendence.com/support To check if an update of this program is available, click here. Click the Analyze Local button to analyze this computer or the Analyze Remote button for a computer on the network... -------------------------------------------------------------------------------- System Information (local) -------------------------------------------------------------------------------- computer name: GIULIO-PCHOF windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: AuthenticAMD AMD A8-3800 APU with Radeon(tm) HD Graphics AMD586, level: 18 4 logical processors, active mask: 15 RAM: 3749847040 total VM: 2147352576, free: 1957838848 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Mon 02.04.2012 20:26:06 GMT your computer crashed crash dump file: C:\Windows\Minidump\040212-30950-01.dmp uptime: 1 day, 09:53:42 This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40) Bugcheck code: 0x9F (0x3, 0xFFFFFA8005C43060, 0xFFFFF80005407518, 0xFFFFFA800AEF03E0) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 02.04.2012 20:26:06 GMT your computer crashed crash dump file: C:\Windows\memory.dmp uptime: 1 day, 09:53:42 This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x9F (0x3, 0xFFFFFA8005C43060, 0xFFFFF80005407518, 0xFFFFFA800AEF03E0) Error: DRIVER_POWER_STATE_FAILURE Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 01.04.2012 10:31:35 GMT your computer crashed crash dump file: C:\Windows\Minidump\040112-22214-01.dmp uptime: 8 days, 22:50:52 This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40) Bugcheck code: 0x9F (0x3, 0xFFFFFA8005042060, 0xFFFFF80000B9C518, 0xFFFFFA800D1E78A0) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Thu 22.03.2012 17:14:57 GMT your computer crashed crash dump file: C:\Windows\Minidump\032212-16551-01.dmp uptime: 08:45:09 This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40) Bugcheck code: 0x9F (0x3, 0xFFFFFA8005EE2060, 0xFFFFF80005407518, 0xFFFFFA8003AD4770) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Thu 22.03.2012 08:28:59 GMT your computer crashed crash dump file: C:\Windows\Minidump\032212-19141-01.dmp uptime: 19:58:25 This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40) Bugcheck code: 0x9F (0x3, 0xFFFFFA800504F060, 0xFFFFF80000B9C518, 0xFFFFFA8008AC7C10) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 19.03.2012 12:29:43 GMT your computer crashed crash dump file: C:\Windows\Minidump\031912-18408-01.dmp uptime: 4 days, 05:18:38 This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40) Bugcheck code: 0x9F (0x3, 0xFFFFFA8005D22060, 0xFFFFF80005352518, 0xFFFFFA8005963470) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Wed 14.03.2012 21:52:17 GMT your computer crashed crash dump file: C:\Windows\Minidump\031412-17019-01.dmp uptime: 15:49:37 This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40) Bugcheck code: 0x9F (0x3, 0xFFFFFA8005CE6060, 0xFFFFF80000B9C518, 0xFFFFFA8008E8CC10) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Tue 13.03.2012 23:06:07 GMT your computer crashed crash dump file: C:\Windows\Minidump\031412-38235-01.dmp uptime: 15:39:40 This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x9F (0x3, 0xFFFFFA8005D24060, 0xFFFFF80005407518, 0xFFFFFA800D347C10) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Tue 06.03.2012 02:34:44 GMT your computer crashed crash dump file: C:\Windows\Minidump\030612-27331-01.dmp uptime: 3 days, 04:01:24 This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x9F (0x3, 0xFFFFFA8005C9E060, 0xFFFFF80000B9C518, 0xFFFFFA800476CC10) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 26.02.2012 19:06:19 GMT your computer crashed crash dump file: C:\Windows\Minidump\022612-17612-01.dmp uptime: 10:19:56 This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x9F (0x3, 0xFFFFFA80036CA060, 0xFFFFF80000B9C518, 0xFFFFFA8005AC2C10) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Fri 24.02.2012 08:45:31 GMT your computer crashed crash dump file: C:\Windows\Minidump\022412-22386-01.dmp uptime: 4 days, 16:47:43 This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x9F (0x3, 0xFFFFFA8005141060, 0xFFFFF80005407518, 0xFFFFFA8016A31850) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 05.02.2012 17:22:27 GMT your computer crashed crash dump file: C:\Windows\Minidump\020512-26114-01.dmp uptime: 6 days, 00:52:02 This was probably caused by the following module: atikmpag.sys (atikmpag+0x780C) Bugcheck code: 0x116 (0xFFFFFA800483D250, 0xFFFFF8800751580C, 0x0, 0x2) Error: VIDEO_TDR_ERROR file path: C:\Windows\system32\drivers\atikmpag.sys product: AMD driver company: Advanced Micro Devices, Inc. description: AMD multi-vendor Miniport Driver Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.). Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR On Fri 25.11.2011 00:47:06 GMT your computer crashed crash dump file: C:\Windows\Minidump\112511-18798-01.dmp uptime: 1 day, 17:57:56 This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x9F (0x3, 0xFFFFFA8005D00060, 0xFFFFF80000B9C518, 0xFFFFFA8009D3B1D0) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Thu 17.11.2011 23:50:22 GMT your computer crashed crash dump file: C:\Windows\Minidump\111811-22276-01.dmp uptime: 05:24:26 This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x9F (0x3, 0xFFFFFA8004FE9060, 0xFFFFF80005407518, 0xFFFFFA800431B2D0) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Tue 15.11.2011 00:08:10 GMT your computer crashed crash dump file: C:\Windows\Minidump\111511-18704-01.dmp uptime: 02:28:11 This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x9F (0x3, 0xFFFFFA8005A73060, 0xFFFFF80005407518, 0xFFFFFA8008C79650) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 21 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.) If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. |
|
|
|
|
17-04-2012, 06:33
|
#1771 |
|
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37089
|
Con quel tipo di problema la causa può essere driver come hw, inizia testando la ram scollegando un banco alla volta poi prova a riavviare e vedi come va.
|
|
|
|
|
17-04-2012, 07:26
|
#1772 | |
|
Bannato
Iscritto dal: Apr 2012
Messaggi: 74
|
Quote:
|
|
|
|
|
|
17-04-2012, 08:49
|
#1773 |
|
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37089
|
Va bene, ma in quell'altro modo sei più sicuro è un test che non può fallire
 in caso negativo puoi escludere le ram e passare ad altri componenti
|
|
|
|
|
17-04-2012, 12:55
|
#1774 | |
|
Senior Member
Iscritto dal: Aug 2007
Messaggi: 1679
|
Quote:
tra l'altro memtest l'avevo gia' scaricato ma ancora non lo avevo lanciato... c'e' un programma che dica quanti banchi di ram e di che tipo si ha senza aprire il case? sono pigro.. :-) l'altro problema e' che non so quali siano le esatte condizioni sotto le quali il problema si presenta. |
|
|
|
|
|
17-04-2012, 17:26
|
#1775 | |
|
Bannato
Iscritto dal: Apr 2012
Messaggi: 74
|
Quote:
|
|
|
|
|
|
17-04-2012, 23:29
|
#1776 | |
|
Senior Member
Iscritto dal: Aug 2007
Messaggi: 1679
|
Quote:
|
|
|
|
|
|
19-04-2012, 19:44
|
#1777 |
|
Senior Member
Iscritto dal: Feb 2008
Messaggi: 9598
|
sapreste aiutarmi a capire questo riavvio improvviso (pc in idle):
Codice:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\041912-17191-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`04208000 PsLoadedModuleList = 0xfffff800`0444d670
Debug session time: Thu Apr 19 20:16:30.877 2012 (UTC + 2:00)
System Uptime: 0 days 0:35:32.094
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {24, 2, 0, fffff8000428d6cb}
Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+22b )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000024, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000428d6cb, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800044b7100
0000000000000024
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiTimerWaitTest+22b
fffff800`0428d6cb 418b4624 mov eax,dword ptr [r14+24h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9c350 -- (.trap 0xfffff80000b9c350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800a326100 rbx=0000000000000000 rcx=fffffa8003da72a0
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000428d6cb rsp=fffff80000b9c4e8 rbp=fffffa80044a4328
r8=fffff800043fd001 r9=0000000000000004 r10=00000000000000df
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiTimerWaitTest+0x22b:
fffff800`0428d6cb 418b4624 mov eax,dword ptr [r14+24h] ds:de88:00000000`00000024=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800042841e9 to fffff80004284c40
STACK_TEXT:
fffff800`00b9c208 fffff800`042841e9 : 00000000`0000000a 00000000`00000024 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c210 fffff800`04282e60 : fffff800`043fae80 fffffa80`03d02c68 fffff800`044252c0 fffffa80`044a4328 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c350 fffff800`0428d6cb : fffffa80`093bde88 fffffa80`093bde78 fffff880`00f55f19 fffffa80`093b4520 : nt!KiPageFault+0x260
fffff800`00b9c4e8 fffff880`009f2180 : fffffa80`044a4320 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiTimerWaitTest+0x22b
fffff800`00b9c568 fffffa80`044a4320 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`0000000a : 0xfffff880`009f2180
fffff800`00b9c570 00000000`00000000 : 00000000`00000000 00000000`00000001 00000000`0000000a 00000000`00000000 : 0xfffffa80`044a4320
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTimerWaitTest+22b
fffff800`0428d6cb 418b4624 mov eax,dword ptr [r14+24h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiTimerWaitTest+22b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0xA_nt!KiTimerWaitTest+22b
BUCKET_ID: X64_0xA_nt!KiTimerWaitTest+22b
Followup: MachineOwner
---------
|
|
|
|
|
19-04-2012, 22:28
|
#1778 | |
|
Member
Iscritto dal: Mar 2009
Città: Latina
Messaggi: 296
|
Quote:
__________________
Cpu: Amd phenom II X4 955 BE 3.6 ghz + Scythe mugen rev 2 Sc.madre: Asus M4a77td-pro. Ram:8gb corsair vengeance 1600 mhz. Vga: Msi Nvidia gtx 560ti hawk. SSD: Crucial c300 128 gb (sistema). Hard disk: Seagate 1 tera;. Ali: cooler master 460 watts (si, regge a meraviglia). Case: cm 690 nvidia edition. |
|
|
|
|
|
21-04-2012, 17:14
|
#1779 |
|
Member
Iscritto dal: Jun 2009
Messaggi: 92
|
Ciao a tutti,
da questa mattina sto impazzendo dietro un BSOD: se faccio partire il portatile in modalità provvisoria funziona senza problemi, ho fatto scan disk completo e mem test di windows ma resta il problema: 042112-24835-01.dmp 21/04/2012 16:54:30 0x00000124 00000000`00000000 fffffa80`0a84a028 00000000`b2000000 00000000`00070150 hal.dll hal.dll+12a3b x64 C:\Windows\Minidump\042112-24835-01.dmp 8 15 7601 hal.dll hal.dll+12a3b fffff800`039f0000 fffff800`03a39000 0x00049000 0x4ce7c669 20/11/2010 15:00:25 ntoskrnl.exe ntoskrnl.exe+18cc43 fffff800`03408000 fffff800`039f0000 0x005e8000 0x4ec79dd2 19/11/2011 14:15:14 Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17727 (win7sp1_gdr.111118-2330) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe Sapete da cosa può dipendere? (non mi sembra di aver fatto aggiornamenti di driver o altro) Grazie infinite a chiunque possa aiutarmi!!  P.S.: al momento sto eseguendo anche qualche anti malware da modalità provvisoria.. |
|
|
|
|
21-04-2012, 17:31
|
#1780 |
|
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37089
|
Dal tipo di parametro sembra un errore HW, adesso aspetta la fine delle scansioni, ma potrebbe essersi guastato qualche componente
|
|
|
|
|
|
| Strumenti | |
|
|
Tutti gli orari sono GMT +1. Ora sono le: 19:14.
