PROBLEMA bluescreen

Baiobilli

Nuovo Utente
4
0
Ciao a tutti, premetto che non sono molto pratico, uso il pc principalmente per giocare e mi sono fatto assemblare questo pc da un amico. il mio pc: processore: intel core i7-3770 CPU @ 3.40GHz 8 GB RAM CORSAIR DDR3 windows 7 professional 64 bit scheda video: MSI 680 GTX TWIN FROZR scheda madre: MSI Z77A-GD55 Z77 DDR3 1155 AT HD: 1 SAMSUNG 128GB SSD 830 NOTEBOOK (gira praticamente solo windows) 1 SAMSUNG SH-222BB/BEBE 22X SATA da 2TB (ci installo solo i giochi) molto spesso mi da dei bluescreen (in vari momenti) tipo gli ultimi che mi sta dando sono quando aggiorno giochi da Steam (in particolare Arma 3), aggiorna tranquillo poi alla fine va in bluescreen, riavvio ed e' come se mi disinstallasse il gioco, probabilmente si corrompe qualche file e devo reinstallarlo. Ma a volte mi ha dato dei bluescreen mentre si spegneva, arrestavo il sistema schermata blu di spegnimento e zac bluescreen. A volte addirittura stando in scrivania senza fare nulla, a volte giocando a Battlefield 3, a volte dopo averci giocato per un bel po chiudo il gioco, esco da origin e zac bluescreen. Tengo i driver del sistema operativo, della scehda video e della scheda madre abbastanza aggiornati, l'unica cosa che non ho mai aggiornato e' il BIOS. Leggendo un po di forum ho installato Whocrashed, aggiornando dei driver che mi aveva consigliato qualcosina ho risolto nel senso che non mi da piu dei bluescreen in certe situazioni, ma quando aggiorno da Steam i giochi o li installo da zero sono quasi certo parta il blueascreen alla fine dell'installazione o dell'aggiornamento. Vi linko solo le ultime scansioni di settembre: [FONT=Segoe UI, Arial]windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Intel586, level: 6 8 logical processors, active mask: 255 RAM: 8541028352 total VM: 2147352576, free: 1932382208 [/FONT] [FONT=Segoe UI, Arial]
Crash Dump Analysis

[/FONT] [FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT] [FONT=Segoe UI, Arial]Crash dumps are enabled on your computer. [/FONT] [FONT=Segoe UI, Arial]On Mon 23/09/2013 19:56:51 GMT your computer crashed crash dump file: C:\Windows\Minidump\092313-7035-01.dmp This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75B80) Bugcheck code: 0x4E (0x99, 0x119AD5, 0x2, 0x11A4D4) Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT] file path: C:\Windows\system32\ntoskrnl.exe product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT] company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT] description: NT Kernel & System Bug check description: This indicates that the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time. [/FONT] [FONT=Segoe UI, Arial]On Mon 23/09/2013 19:56:51 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs+0x7B9A7) Bugcheck code: 0x4E (0x99, 0x119AD5, 0x2, 0x11A4D4) Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT] file path: C:\Windows\system32\drivers\ntfs.sys product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT] company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT] description: Driver file system NT Bug check description: This indicates that the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. [/FONT] [FONT=Segoe UI, Arial]On Mon 23/09/2013 18:40:29 GMT your computer crashed crash dump file: C:\Windows\Minidump\092313-8876-01.dmp This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75B80) Bugcheck code: 0x4E (0x99, 0x155F01, 0x7, 0x1) Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT] file path: C:\Windows\system32\ntoskrnl.exe product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT] company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT] description: NT Kernel & System Bug check description: This indicates that the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time. [/FONT] [FONT=Segoe UI, Arial]On Tue 17/09/2013 20:34:51 GMT your computer crashed crash dump file: C:\Windows\Minidump\091713-7238-01.dmp This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75B80) Bugcheck code: 0x4E (0x99, 0x2BF01, 0x7, 0x1) Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT] file path: C:\Windows\system32\ntoskrnl.exe product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT] company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT] description: NT Kernel & System Bug check description: This indicates that the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time. [/FONT] [FONT=Segoe UI, Arial]On Tue 17/09/2013 19:45:45 GMT your computer crashed crash dump file: C:\Windows\Minidump\091713-7347-01.dmp This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75B80) Bugcheck code: 0x4E (0x99, 0x13B47B, 0x3, 0x1346ED) Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT] file path: C:\Windows\system32\ntoskrnl.exe product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT] company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT] description: NT Kernel & System Bug check description: This indicates that the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time. [/FONT] [FONT=Segoe UI, Arial]On Sat 07/09/2013 16:00:15 GMT your computer crashed crash dump file: C:\Windows\Minidump\090713-7020-01.dmp This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75B80) Bugcheck code: 0x1A (0x8887, 0xFFFFFA800563D030, 0xFFFFFA800531F000, 0x502) Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT] file path: C:\Windows\system32\ntoskrnl.exe product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT] company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT] 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 that cannot be identified at this time. [/FONT] [FONT=Segoe UI, Arial]On Sun 01/09/2013 03:25:49 GMT your computer crashed crash dump file: C:\Windows\Minidump\090113-6895-01.dmp This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75B80) Bugcheck code: 0x4E (0x99, 0x8724A, 0x0, 0x865CA) Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT] file path: C:\Windows\system32\ntoskrnl.exe product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT] company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT] description: NT Kernel & System Bug check description: This indicates that the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time. [/FONT] [FONT=Segoe UI, Arial]On Sun 01/09/2013 02:14:20 GMT your computer crashed crash dump file: C:\Windows\Minidump\090113-6957-01.dmp This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75B80) Bugcheck code: 0x4E (0x99, 0x18F1FC, 0x3, 0x182208) Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT] file path: C:\Windows\system32\ntoskrnl.exe product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT] company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT] description: NT Kernel & System Bug check description: This indicates that the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time[/FONT] Vi serai grato se mi deste una vostra opinione o dei consigli. Ringrazio in anticipo e tristemente vado a letto! :ciaociao:
 

Djinn

Nuovo Utente
112
11
CPU
Intel q6600 2,4ghz
Scheda Madre
Asus p5qd-turbo
Hard Disk
ssd 512 gb + WD green 2TB
RAM
16gb 1200mhz
Scheda Video
Nvidia
Scheda Audio
8-channel
Case
un calssico asus moddato
Sistema Operativo
windows-linux
0x4e è uno dei messaggi che compare in caso di RAM diffettosa o Driver compromessi. Prova a fare qualche test della Ram
 
  • Mi piace
Reactions: Baiobilli

Demianz88

Utente Attivo
584
101
CPU
i5 7600k
Dissipatore
Noctua NH-U9B SE2
Scheda Madre
Gigabyte Z270X Ultra Gaming
Hard Disk
Samsung 840 EVO 250GB
RAM
3200Mhz CL14 G.Skills Trident Z 2x8GB
Scheda Video
MSI GTX 1070 Gaming X
Monitor
ASUS VG248QE 24" 144Hz
Alimentatore
Seasonic G-550
Case
Masterbox 5 UK Edition
Sistema Operativo
windows 10 PRO, 64 bit
  • Mi piace
Reactions: Baiobilli

Baiobilli

Nuovo Utente
4
0
ok ho fatto il test ti allego l'immagine
nessun errore
ho tenuto entrambe le stecche di ram immaginando che avrei potuto poi ripeterlo una stecca per volta se avesse trovato errori, giusto?
cmq il b.screen si e' ripresentato durante il download dell'ultima patch di arma3 da steam
idee?

risultato.jpg
 

Entra

oppure Accedi utilizzando

Discussioni Simili

Hot del momento