Vista/7 - Schermate blu (bsod):individuazione cause dell'errore e possibili soluzioni

[bosstury]

Originariamente inviato da Eress

Evidentemente quei driver non sono buoni per il tuo pc, mettine altri

se me li farebbe mettere allora si... ad ogni avvio pc, ho schermate blu o errori critici e dopo poco si ripresentano le schermate blu... non ho modo ne di formattare ne di disinstallare,,

ps. mi sono appena accorto che anche con hdd staccato, facendo partire il lettore dvd col dvd dentro di seven, allo stesso punto da la stessa schermatablu

consigli ?

[Drakogian]

Che memorie RAM hai ?
Se ne hai due, prova a metterne una alla volta.
Hai provato a far partire il pC in Safe Mode premendo il ripetutamente il tasto F8 all'avvio ?

[bosstury]

sto rimando tutto al mittente, dove ho comprato, se la vede lui..
avevo provato a cambiare ram, vga, hdd... il poblema cambiava ma restava il fatto che il sistema non era stabile e delle schermate blu alla prima accensione, mi sono girate... quindi e la vede lui e se ce da cambiare qualcosa, la cambio..
non credo sia solo un problema software come si dice in giro per bad_poll_caller.....

[burkylando]

Ciao, ma nel visualizzatore eventi, viene riportato un crash di sistema, se si in quale paragrafo?

[valerioraikkonen]

ciao, ho acceso il pc e mentre windows 7 stava caricando il pc si è riavviato da solo....oggi mentre stava caricando si è bloccata la schermata e ho dovuto riavviare manualmente, qualche idee?


grazie per il vs aiuto

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: 80662000, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 82c86133, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82db4828
Unable to read MiSystemVaType memory at 82d94d80
 80662000 

FAULTING_IP: 
nt!memmove+33
82c86133 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  80decbe4 -- (.trap 0xffffffff80decbe4)
ErrCode = 00000002
eax=806429f2 ebx=00000014 ecx=0000021c edx=00000002 esi=80642180 edi=80662000
eip=82c86133 esp=80decc58 ebp=80decc60 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!memmove+0x33:
82c86133 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82c8da18 to 82cb3d87

STACK_TEXT:  
80decbcc 82c8da18 00000001 80662000 00000000 nt!MmAccessFault+0xbf
80decbcc 82c86133 00000001 80662000 00000000 nt!KiTrap0E+0xdc
80decc60 88206dab 80661e80 80642000 000009f2 nt!memmove+0x33
80deccb4 8820e1a1 8540a078 80642000 0000016a rdyboost!ST_STORE<SMD_TRAITS>::StCompactRegions+0x23b
80decd00 8820f971 00000000 8540a238 8540a008 rdyboost!ST_STORE<SMD_TRAITS>::StCompactionPerformInMem+0xb3
80decd14 8820fd4c 8540a050 8540a238 8540a008 rdyboost!ST_STORE<SMD_TRAITS>::StCompactionWorker+0x9f
80decd28 8820ff14 8540a008 8540a238 00000000 rdyboost!ST_STORE<SMD_TRAITS>::StWorkItemProcess+0x7c
80decd50 82e3d4b2 00000102 ab6b0d6a 00000000 rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+0xfe
80decd90 82cde999 8820fe16 8540a008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rdyboost!ST_STORE<SMD_TRAITS>::StCompactRegions+23b
88206dab eb05            jmp     rdyboost!ST_STORE<SMD_TRAITS>::StCompactRegions+0x242 (88206db2)

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  rdyboost!ST_STORE<SMD_TRAITS>::StCompactRegions+23b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rdyboost

IMAGE_NAME:  rdyboost.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce78e17

FAILURE_BUCKET_ID:  0x50_rdyboost!ST_STORE_SMD_TRAITS_::StCompactRegions+23b

BUCKET_ID:  0x50_rdyboost!ST_STORE_SMD_TRAITS_::StCompactRegions+23b

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

[Eress]

Vedi qui

http://windows7forums.com/windows-7-...ost-sys-2.html

[asura88]

ragazzi mi dite cosa posso fareeeee

http://i42.tinypic.com/4kdvzc.jpg

[Ordaz]

Originariamente inviato da asura88

ragazzi mi dite cosa posso fareeeee

http://i42.tinypic.com/4kdvzc.jpg

conviene che ci posti il file minidump. questo è l'errore generico e risalire da qui al problema è impossibile.

[asura88]

il minidump come lo faccio

[Eress]

http://www.hwupgrade.it/forum/showthread.php?t=1955371
Ridimensionate le immagini please

Originariamente inviato da Ordaz

conviene che ci posti il file minidump. questo è l'errore generico e risalire da qui al problema è impossibile.

controlla la ram per iniziare, scollega un banco alla volta e vedi come va.

[burkylando]

Originariamente inviato da burkylando

Ciao, ma nel visualizzatore eventi, viene riportato un crash di sistema, se si in quale paragrafo?

Potreste rispondermi?

[Eress]

Originariamente inviato da burkylando

Potreste rispondermi?

Nel paragrafo sistema evidentemente

[burkylando]

Originariamente inviato da Eress

Nel paragrafo sistema evidentemente

Si ma volevo sapere se c'era un modo per filtrare i risultati cercando il codice del crash, ne hanno uno in particolare di codice? Perchè sotto sistema ci sono tante voci.

[asura88]

perche il problema che mi fa è dovuto dalla ram?la dice del bios

[asura88]

ho fatto quello che mi avevi chiesto..

On Fri 23/03/2012 17:00:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032312-27440-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x37953)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88007D99953, 0xFFFFF8800CC11AD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.


On Fri 23/03/2012 17:00:14 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x26083)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88007D99953, 0xFFFFF8800CC11AD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.


On Thu 22/03/2012 19:32:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032212-18205-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x94765)
Bugcheck code: 0xC5 (0xA161A, 0x2, 0x1, 0xFFFFF800031B590D)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
Bug check description: This indicates that the system attempted to access invalid 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. 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 which cannot be identified at this time.


On Thu 22/03/2012 16:31:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032212-27814-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030DE145, 0xFFFFF88009F06F90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.

[Eress]

Originariamente inviato da burkylando

Si ma volevo sapere se c'era un modo per filtrare i risultati cercando il codice del crash, ne hanno uno in particolare di codice? Perchè sotto sistema ci sono tante voci.

Tocca controllarle tutte

Originariamente inviato da asura88

ho fatto quello che mi avevi chiesto..

Direi conflitto chiaramente collegato ai driver video/directX, prova a cambiare versione driver, se hai un preassemblato vai nel sito del costruttore

[Darksaw88]

Ciao ragazzi avevo il NB pieno di virus. Ho ripulito tutto ma appena si avvia Windows Vista mi fa sempre schermate blue uguale a questa:

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


Loading Dump File [C:\Documents and Settings\Paolo\Desktop\Minidump\Mini033012-02.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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18533.x86fre.vistasp2_gdr.111025-0338
Machine Name:
Kernel base = 0x82212000 PsLoadedModuleList = 0x82329c70
Debug session time: Fri Mar 30 16:54:50.083 2012 (UTC + 2:00)
System Uptime: 0 days 0:01:54.004
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, 8223d83c}

Probably caused by : raspptp.sys ( raspptp!FreeSockContextCommon+33 )

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

1: 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: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 8223d83c, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82349868
Unable to read MiSystemVaType memory at 82329420
 00000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExpRemoveGeneralLookaside+15
8223d83c 890f            mov     dword ptr [edi],ecx

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  8cdaac44 -- (.trap 0xffffffff8cdaac44)
ErrCode = 00000002
eax=00000002 ebx=8a3d3208 ecx=00000000 edx=00000000 esi=8a3d3140 edi=00000000
eip=8223d83c esp=8cdaacb8 ebp=8cdaacbc iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!ExpRemoveGeneralLookaside+0x15:
8223d83c 890f            mov     dword ptr [edi],ecx  ds:0023:00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8223d83c to 8225ffd9

STACK_TEXT:  
8cdaac44 8223d83c badb0d00 00000000 b58e531d nt!KiTrap0E+0x2e1
8cdaacbc 8222c5e8 82314200 8a3d3118 8cdaace4 nt!ExpRemoveGeneralLookaside+0x15
8cdaaccc 8f325c84 8a3d3140 00000004 8a3d3118 nt!ExDeleteNPagedLookasideList+0x13
8cdaace4 8f325f4e 8a3d3118 8a3d3118 872752b8 raspptp!FreeSockContextCommon+0x33
8cdaacf8 8f325cea 8a3d3118 8cdaad48 8f31ab8f raspptp!FreeSockHandle+0x78
8cdaad04 8f31ab8f 8a3d3118 8f328448 872752b8 raspptp!WskDestroySockContext+0x1f
8cdaad48 8f31aa1f 872752b8 8f328440 8cdaad7c raspptp!PptpInitialize+0x15b
8cdaad58 8f31a602 901b81f0 00000000 872615b8 raspptp!TapipPassiveProviderInitialize+0x12
8cdaad7c 823e7fe2 00000000 79f5fce8 00000000 raspptp!MainPassiveLevelThread+0x41
8cdaadc0 82250efe 8f31a5c1 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
raspptp!FreeSockContextCommon+33
8f325c84 8d4678          lea     eax,[esi+78h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  raspptp!FreeSockContextCommon+33

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: raspptp

IMAGE_NAME:  raspptp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  47919112

FAILURE_BUCKET_ID:  0xA_raspptp!FreeSockContextCommon+33

BUCKET_ID:  0xA_raspptp!FreeSockContextCommon+33

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

Grazie

[Eress]

Sempre che non sia una conseguenza dei virus o che ce ne siano ancora presenti, inizia dalla ram, scollega un banco alla volta e prova il pc

[albarossa2001]

salve, mio pc acer m5620 skvideo nvidia 8800gts, sistama operativo vista con service pack 2, vita del pc 3 anni circa,
all'inizio qualche volta si è verificato qualche BS nel 2009, ma molto molto raramente invece dal mese di aprile del 2012 sono diventati un giorno si un giorno no, spesso ed anche riavvii improvvisi senza BS, sia quando lo accendo che quando sto lavorando.
Ho aggiornato la scheda madre con ultimo disponibile, ho aggiornato tutti i driver possibili compreso la scheda video, ho fatto il testa della memoria per una intera notte!
Cosa potrebbe essere, cosa posso provare?
Allego gli ultimi dump di errori
https://rapidshare.com/files/3469723018/minidump.zip
Spero in un vostro aiuto, anche perchè purtroppo è un pc per lavoro- Grazie

[Eress]

Il problema riguarda la scheda video, probabilmente driver, prova ad aggiornarli o se sono già aggiornati, con un rollback degli stessi