B.s.o.d Windows 7 ultimate 64 bit

[pin2005]

ricevo questo errore cosa può essere?

Firma problema:
Nome evento problema: BlueScreen
Versione SO: 6.1.7600.2.0.0.256.1
ID impostazioni locali: 1040

Ulteriori informazioni sul problema:
BCCode: 1a
BCP1: 0000000000000403
BCP2: FFFFF68000003B58
BCP3: F3B0000126FF5025
BCP4: 00FFF8A000ED97A0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\112713-34101-01.dmp
C:\Users\Administrator\AppData\Local\Temp\WER-47736-0.sysdata.xml

Leggere l'informativa sulla privacy online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0410

Se l'informativa sulla privacy online non è disponibile, leggere quella offline:
C:\Windows\system32\it-IT\erofflps.txt

[Khronos]

l'unica cosa che serve di tutto lo scritto è

BCCode: 1a

poi servirebbe, come aiuto, sapere "cosa stavi facendo quando è crashato", e "se lo ha fatto più volte allo stesso modo".
aggiornati tutti i driver (specie i video e il chipset)?
overclock presente?

[Eress]

Serve il file dmp

http://www.hwupgrade.it/forum/showthread.php?t=1955371

Inizia comunque testando la ram.

[pin2005]

ecco il dmp

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


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


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800`0361d000 PsLoadedModuleList = 0xfffff800`03859e70
Debug session time: Wed Nov 27 19:39:51.558 2013 (UTC + 1:00)
System Uptime: 0 days 0:00:23.275
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
.......................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff68000003b58, f3b0000126ff5025, fff8a000ed97a0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31522 )

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

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff68000003b58
Arg3: f3b0000126ff5025
Arg4: 00fff8a000ed97a0

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


BUGCHECK_STR: 0x1a_403

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER: from fffff800036fde78 to fffff8000368c880

STACK_TEXT:
fffff880`0339fe18 fffff800`036fde78 : 00000000`0000001a 00000000`00000403 fffff680`00003b58 f3b00001`26ff5025 : nt!KeBugCheckEx
fffff880`0339fe20 fffff800`036bcf41 : 00000000`00000000 fffff680`00003ff8 fffffa80`039ee040 fffff800`036be31b : nt! ?? ::FNODOBFM::`string'+0x31522
fffff880`0339ffd0 fffff800`036bf9c9 : fffffa80`00000000 00000000`00cc8fff fffffa80`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x408
fffff880`033a0190 fffff800`039a0e90 : fffffa80`04f5c420 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`033a02b0 fffff800`039a129b : 00000000`00000000 00000000`00080000 fffffa80`00000001 fffff800`0368aa00 : nt!MiUnmapViewOfSection+0x1b0
fffff880`033a0370 fffff800`0368bad3 : 00000000`00000000 00000000`000037d6 fffffa80`039ee040 00000000`00000800 : nt!NtUnmapViewOfSection+0x5f
fffff880`033a03c0 fffff800`03688070 : fffff800`03a647e9 00000000`00000000 00000000`00000000 00000000`00100000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`033a0558 fffff800`03a647e9 : 00000000`00000000 00000000`00000000 00000000`00100000 fffff880`033a0918 : nt!KiServiceLinkage
fffff880`033a0560 fffff800`03a6492c : ffffffff`80000148 fffffa80`00100000 00000000`00080000 ffffffff`80000054 : nt!MmCheckSystemImage+0x319
fffff880`033a0690 fffff800`03a64b47 : ffffffff`80000148 fffff800`00000001 00000000`00000000 00000000`00000000 : nt!MiCreateSectionForDriver+0xcc
fffff880`033a0740 fffff800`03a703da : 00000000`00000000 fffff880`033a0918 fffffa80`03a03040 fffff880`031d4100 : nt!MiObtainSectionForDriver+0xd7
fffff880`033a07a0 fffff800`03a72ffd : fffff880`033a0918 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmLoadSystemImage+0x23a
fffff880`033a08c0 fffff800`03a739b5 : 00000000`00000001 00000000`00000000 fffffa80`03962310 00000000`00000000 : nt!IopLoadDriver+0x44d
fffff880`033a0b90 fffff800`03b06eeb : 00000000`00000000 ffffffff`80000050 00000000`00000000 00000000`00000000 : nt!IopLoadUnloadDriver+0x55
fffff880`033a0bd0 fffff800`0368bad3 : fffffa80`03a03040 fffff880`033a0f08 00000000`00000000 00000000`00000000 : nt!NtLoadDriver+0x189
fffff880`033a0c80 fffff800`03688070 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`033a0e18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+31522
fffff800`036fde78 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+31522

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5147dc36

IMAGE_VERSION: 6.1.7600.17273

FAILURE_BUCKET_ID: X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31522

BUCKET_ID: X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31522

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x1a_403_nt!_??_::fnodobfm::_string_+31522

FAILURE_ID_HASH: {062c2054-738e-d262-01a5-fdeba110699b}

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

2: kd> lmvm nt
start end module name
fffff800`0361d000 fffff800`03bf7000 nt (pdb symbols) c:\symbols\ntkrnlmp.pdb\2C39F687423840E793308F28C4FDE0CD2\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: c:\symbols\ntoskrnl.exe\5147DC365da000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Tue Mar 19 04:32:06 2013 (5147DC36)
CheckSum: 00548A5F
ImageSize: 005DA000
File version: 6.1.7600.17273
Product version: 6.1.7600.17273
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 6.1.7600.17273
FileVersion: 6.1.7600.17273 (win7_gdr.130318-1532)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.

[Eress]

Come detto prima, controlla la ram, memtest con un banco solo di ram collegato alla volta. O puoi semplicemente utilizzare il pc con un solo banco alla volta.

[pin2005]

ecco i test
http://i.imgur.com/TZXt6aS.jpg
http://i.imgur.com/TO93ddt.jpg
http://i.imgur.com/70lDMQY.jpg

[Eress]

La ram sembra a posto, anche se per averne l'assoluta certezza è sempre meglio procedere con un test diretto, utilizzando il pc con un solo banco di ram alla volta.
Se ultimamente hai aggiornato qualche driver importante, fai un rollback.

[pin2005]

http://i.imgur.com/7hMjs6J.jpg
questo è un crash di pochi giorni fa