PROBLEMA Continue Schermate Blu su Windows 7

Cyberhackertp96

Nuovo Utente
18
0
Ciao a tutti, sono nuovo nel forum, mi sono appena iscritto per trovare un aiuto, da qualche giorno il mio computer non fa altro che fare schermate blu, per ogni qualsiasi genere di problema, fin'ora mi sono comparse IRQL_NOT_LESS_OR_EQUAL oppure MEMORY_MANAGMENT, molte di queste schermate una volta uscite fanno bloccare l' intera macchina anche nel momento della "cache dump", il sistema si blocca totalmente, al successivo riavvio, non parte il boot, il computer va a vuoto, oppure ieri sera è comparso BOOTMGR is corrupt, li ho spento il tutto e dopo un quarto d' ora l' ho riavviato, e il boot è partito con successo, poco dopo aver avviato windows ed aver avuto accesso si è bloccato tutto, ennesima schermata blu, e computer K.O., visto che in ogni caso devo sostituire l' hard disk con uno più capiente, che sia il caso di formattare totalmente Windows? o di sostituire qualche componente interno oltre all' hard disk?



la mia configurazione hardware è:

Mobo: ASUS M2N68-AM PLUS
Processore: AMD Athlon x3 2.90 GhZ
Ram: 2 Blocchi da 2 GB
HD: Maxtor 250GB
Scheda Video: Gigabyte GeForce 210 HD
Scheda Audio: Trust 7.1 Surround Sound Card SC-7600
Alimentatore: Matsuyama 800W
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,207
6,218
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 7 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows10x64pro
scarica whocrashed e posta la lettura del dmp
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,207
6,218
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 7 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows10x64pro
amico sono le ram scarica memtest dalla mia firma e fai girare qualche ora
 

Cyberhackertp96

Nuovo Utente
18
0
Grazie alla Modalità Provvisoria che dopo una settimana ha deciso di partire sono riuscito a fare tutto senza il problema della schermata blu, ti allego lo screenshot del dump report di whocrashed!

DMP.jpg
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,207
6,218
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 7 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows10x64pro
mi serve report copia e incolla ma se è come credo direi che è meglio fare un test della ram
 

Cyberhackertp96

Nuovo Utente
18
0
tramite il file contenuto nella tua firma ho creato una pen drive con il boot di memtest, adesso sto solo aspettando che il computer parta, perchè non fa nemmeno il "beep" dell' accensione, e questa cosa mi va girare le scatole..

- - - Updated - - -

mi serve report copia e incolla ma se è come credo direi che è meglio fare un test della ram

Et Voilà, ecco cio che chiedevi :)

[FONT=Segoe UI, Arial]Welcome to WhoCrashed (HOME EDITION) v 4.02
[/FONT]
[FONT=Segoe UI, Arial]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. It 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.
[/FONT]
[FONT=Segoe UI, Arial]To obtain technical support visit www.resplendence.com/support

[/FONT][FONT=Segoe UI, Arial]Click here to check if you have the latest version or if an update is available.

[/FONT][FONT=Segoe UI, Arial]Just click the Analyze button for a comprehensible report ...


[/FONT][FONT=Segoe UI, Arial]
Home Edition Notice

[/FONT]
[FONT=Segoe UI, Arial]This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
[/FONT]
[FONT=Segoe UI, Arial]
System Information (local)

[/FONT]
[FONT=Segoe UI, Arial]computer name: TOMMASO-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) II X3 435 Processor AMD586, level: 16
3 logical processors, active mask: 7
RAM: 4294221824 total
VM: 2147352576, free: 1830121472


[/FONT]
[FONT=Segoe UI, Arial]
Crash Dump Analysis

[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 02/09/2013 16:31:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090213-24086-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]????.sys[/FONT] (Unloaded_????+0x2B696F)
Bugcheck code: 0xA (0xFFFFF88003BC3187, 0x2, 0x1, 0xFFFFF80003E728E6)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: ????.sys .
Google query: [FONT=Segoe UI, Arial]????.sys IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Fri 30/08/2013 11:49:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083013-27861-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFF800030068DC, 0x8, 0xFFFFF800030068DC, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/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 invalid system memory has been referenced.
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 30/08/2013 11:42:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083013-25896-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0xD1 (0xFFFFF80003291A7A, 0x2, 0x8, 0xFFFFF80003291A7A)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/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 kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 23/08/2013 19:06:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082413-28532-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ci.dll[/FONT] (CI+0x6C187)
Bugcheck code: 0xD3 (0xFFFFF88000C6C187, 0x2, 0x1, 0xFFFFF80003E7C8E6)
Error: [FONT=Segoe UI, Arial]DRIVER_PORTION_MUST_BE_NONPAGED[/FONT]
file path: C:\Windows\system32\ci.dll
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Modulo di controllo dell'integrità del codice
Bug check description: This indicates that the system attempted to access pageable memory at a process IRQL that was too high.
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 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 05/08/2013 17:36:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-99793-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80003E9C18F)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 13/01/2013 21:03:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011313-34554-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x4B094C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80050BE038, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]WHEA_UNCORRECTABLE_ERROR[/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 bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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]
Conclusion

[/FONT]
[FONT=Segoe UI, Arial]6 crash dumps have been found and analyzed. 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:

[FONT=Segoe UI, Arial]????.sys [/FONT]

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.



[/FONT]
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,207
6,218
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 7 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows10x64pro
sembra essere la ram
 

Entra

oppure Accedi utilizzando

Hot: E3 2021, chi ti è piaciuto di più?

  • Ubisoft

    Voti: 17 18.3%
  • Gearbox

    Voti: 1 1.1%
  • Xbox & Bethesda

    Voti: 66 71.0%
  • Square Enix

    Voti: 3 3.2%
  • Capcom

    Voti: 5 5.4%
  • Nintendo

    Voti: 14 15.1%
  • Altro (Specificare)

    Voti: 8 8.6%

Discussioni Simili