- 205
- 7
- CPU
- Intel® Core™ i5-13500
- Dissipatore
- Thermalright Frozen Notte 240
- Scheda Madre
- MSI B760 Gaming Plus WiFi
- HDD
- Crucial P5 Plus
- RAM
- CORSAIR VENGEANCE DDR5 32GB
- GPU
- GeForce RTX™ 4070 12GB VERTO
- Monitor
- HP 2309 Wide LCD
- PSU
- LC-POWER LC6750M 750 Watt
- Case
- Deepcool CK560
- OS
- Windows 10
Ciao a tutti , ho comprato i componenti del mio nuovo pc e me li sono fatti assemblare da un tecnico. Ho cambiato case,alimentatore, scheda video e ho aggiunto un SSD ( ho tenuto la RAM e la mobo) Ora mi esce una schemata BSOD con questi log ( ho anche fatto un memtest)
:
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD FX(tm)-6350 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 8545513472 total
VM: 2147352576, free: 1891454976
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 23/02/2015 23:10:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022415-11559-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73E80)
Bugcheck code: 0x1A (0x41284, 0x8FC5001, 0x710A, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\022415-11559-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 Vista Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.22923.amd64fre.win7sp1_ldr.150113-1808
Kernel base = 0xfffff800`02e08000 PsLoadedModuleList = 0xfffff800`0304b890
Debug session time: Tue Feb 24 00:10:11.688 2015 (GMT+1)
System Uptime: 0 days 5:58:56.750
Loading Kernel Symbols
................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41284, 8fc5001, 710a, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4af3 )
Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 0000000008fc5001
Arg3: 000000000000710a
Arg4: fffff70001080000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41284
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_RC
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ed3897 to fffff80002e7be80
STACK_TEXT:
fffff880`0be520c8 fffff800`02ed3897 : 00000000`0000001a 00000000`00041284 00000000`08fc5001 00000000`0000710a : nt!KeBugCheckEx
fffff880`0be520d0 fffff800`02e95759 : fffffa80`070079f8 ffffffff`ffffffff fffffa80`09ed13c0 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x4af3
fffff880`0be52110 fffff800`02e70ceb : 90a00002`277fc867 fffff680`00047e28 ffffffff`ffffffff 000fffff`ffffffff : nt!MiTerminateWsle+0x29
fffff880`0be52150 fffff800`02e684e2 : fffffa80`08b26d80 fffff8a0`00000000 fffffa80`07007660 fffffa80`070079f8 : nt!MiDecommitPages+0x20b
fffff880`0be529e0 fffff800`02e7b113 : ffffffff`ffffffff 00000000`0990e670 00000000`0990e668 00000000`00004000 : nt!NtFreeVirtualMemory+0x382
fffff880`0be52ae0 00000000`7750cdda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0990e638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7750cdda
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4af3
fffff800`02ed3897 cc int 3
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 54b5f756
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4af3
FAILURE_BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4af3
BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4af3
Followup: MachineOwner
---------
Potreste aiutarmi a capire il problema? Il tecnico ha alzato dal bios la frequenza della ram tra le altre cose , non so se serva ma ve lo dico .
Grazie
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD FX(tm)-6350 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 8545513472 total
VM: 2147352576, free: 1891454976
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 23/02/2015 23:10:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022415-11559-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73E80)
Bugcheck code: 0x1A (0x41284, 0x8FC5001, 0x710A, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\022415-11559-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 Vista Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.22923.amd64fre.win7sp1_ldr.150113-1808
Kernel base = 0xfffff800`02e08000 PsLoadedModuleList = 0xfffff800`0304b890
Debug session time: Tue Feb 24 00:10:11.688 2015 (GMT+1)
System Uptime: 0 days 5:58:56.750
Loading Kernel Symbols
................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41284, 8fc5001, 710a, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4af3 )
Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 0000000008fc5001
Arg3: 000000000000710a
Arg4: fffff70001080000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41284
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_RC
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ed3897 to fffff80002e7be80
STACK_TEXT:
fffff880`0be520c8 fffff800`02ed3897 : 00000000`0000001a 00000000`00041284 00000000`08fc5001 00000000`0000710a : nt!KeBugCheckEx
fffff880`0be520d0 fffff800`02e95759 : fffffa80`070079f8 ffffffff`ffffffff fffffa80`09ed13c0 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x4af3
fffff880`0be52110 fffff800`02e70ceb : 90a00002`277fc867 fffff680`00047e28 ffffffff`ffffffff 000fffff`ffffffff : nt!MiTerminateWsle+0x29
fffff880`0be52150 fffff800`02e684e2 : fffffa80`08b26d80 fffff8a0`00000000 fffffa80`07007660 fffffa80`070079f8 : nt!MiDecommitPages+0x20b
fffff880`0be529e0 fffff800`02e7b113 : ffffffff`ffffffff 00000000`0990e670 00000000`0990e668 00000000`00004000 : nt!NtFreeVirtualMemory+0x382
fffff880`0be52ae0 00000000`7750cdda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0990e638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7750cdda
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4af3
fffff800`02ed3897 cc int 3
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 54b5f756
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4af3
FAILURE_BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4af3
BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4af3
Followup: MachineOwner
---------
Potreste aiutarmi a capire il problema? Il tecnico ha alzato dal bios la frequenza della ram tra le altre cose , non so se serva ma ve lo dico .
Grazie