Forum |  HardWare.fr | News | Articles | PC | S'identifier | S'inscrire | Shop Recherche
2785 connectés 

  FORUM HardWare.fr
  Hardware
  Matériels & problèmes divers

  BSoD, mais pourquoi??

 


 Mot :   Pseudo :  
 
Bas de page
Auteur Sujet :

BSoD, mais pourquoi??

n°6893029
artois
Posté le 22-03-2009 à 13:48:12  profilanswer
 

Bonjour,  
 
Mon PC fait souvent des BSoD ou l'ecran se fige et plus rien ne repond.  
 
La RAM passe Memtest.  
 
Donc le probleme se situe ailleur  
 
Je vous colle ici mon fichier dump:  
 
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86  
Copyright (c) Microsoft Corporation. All rights reserved.  
 
 
Loading Dump File [C:\Windows\Minidump\Mini032209-01.dmp]  
Mini Kernel Dump File: Only registers and stack trace are available  
 
Symbol search path is: C:\symbols  
Executable search path is:  
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible  
Product: WinNt, suite: TerminalServer SingleUserTS  
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612  
Machine Name:  
Kernel base = 0x81c08000 PsLoadedModuleList = 0x81d1fc70  
Debug session time: Sun Mar 22 12:55:22.098 2009 (GMT+1)  
System Uptime: 0 days 0:10:39.873  
Loading Kernel Symbols  
...............................................................  
................................................................  
.......................  
Loading User Symbols  
Loading unloaded module list  
....  
************************************************************­*******************  
* *  
* Bugcheck Analysis *  
* *  
************************************************************­*******************  
 
Use !analyze -v to get detailed debugging information.  
 
BugCheck A, {13, 2, 1, 81caa5d0}  
 
Probably caused by : memory_corruption ( nt!MiInsertPageInFreeList+17d )  
 
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: 00000013, 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: 81caa5d0, address which referenced memory  
 
Debugging Details:  
------------------  
 
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d3f868  
Unable to read MiSystemVaType memory at 81d1f420  
00000013  
 
CURRENT_IRQL: 2  
 
FAULTING_IP:  
nt!MiInsertPageInFreeList+17d  
81caa5d0 83611400 and dword ptr [ecx+14h],0  
 
CUSTOMER_CRASH_COUNT: 1  
 
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT  
 
BUGCHECK_STR: 0xA  
 
PROCESS_NAME: System  
 
TRAP_FRAME: 8c153778 -- (.trap 0xffffffff8c153778)  
ErrCode = 00000002  
eax=0008e1cf ebx=8428f774 ecx=ffffffff edx=0000001b esi=0000001c edi=83d8b2a4  
eip=81caa5d0 esp=8c1537ec ebp=8c1537fc iopl=0 nv up ei pl nz na pe nc  
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210206  
nt!MiInsertPageInFreeList+0x17d:  
81caa5d0 83611400 and dword ptr [ecx+14h],0 ds:0023:00000013=????????  
Resetting default scope  
 
LAST_CONTROL_TRANSFER: from 81caa5d0 to 81c62d24  
 
STACK_TEXT:  
8c153778 81caa5d0 badb0d00 0000001b 8c1537a0 nt!KiTrap0E+0x2ac  
8c1537fc 81c459b5 0008e1cf 82e02028 83d8b2a4 nt!MiInsertPageInFreeList+0x17d  
8c153850 81c9d617 00000200 c059b000 ffffffff nt!MiPfnShareCountIsZero+0x3b4  
8c1538a4 81c4e1b7 b3600000 00000008 8c1538c4 nt!MiReturnSystemVa+0x2f4  
8c153974 81c4efca 00000200 00000000 842ff7d0 nt!MiReleaseSystemCacheView+0x22d  
8c153be4 81e30dc2 b3800000 a1039c08 00000000 nt!MmUnmapViewInSystemCache+0x5ab  
8c153c14 81c4fb13 842ff7d0 00000000 00000000 nt!CcUnmapVacb+0x170  
8c153c58 81c55dad 00000000 8c153c00 84e6cae0 nt!CcUnmapVacbArray+0x1cc  
8c153c74 81c55c5c 8c153c00 84e6cc48 84e6cb24 nt!CcUnmapAndPurge+0x32  
8c153ca0 81c491d4 00000001 84e6cc48 81d3e128 nt!CcDeleteSharedCacheMap+0x107  
8c153cec 81c42826 84e6cae0 8c153d10 00000000 nt!CcWriteBehind+0x582  
8c153d44 81c40445 84315188 00000000 85fe95a8 nt!CcWorkerThread+0x11e  
8c153d7c 81dddb18 84315188 389c8a8a 00000000 nt!ExpWorkerThread+0xfd  
8c153dc0 81c36a2e 81c40348 80000000 00000000 nt!PspSystemThreadStartup+0x9d  
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16  
 
 
STACK_COMMAND: kb  
 
FOLLOWUP_IP:  
nt!MiInsertPageInFreeList+17d  
81caa5d0 83611400 and dword ptr [ecx+14h],0  
 
SYMBOL_STACK_INDEX: 1  
 
SYMBOL_NAME: nt!MiInsertPageInFreeList+17d  
 
FOLLOWUP_NAME: MachineOwner  
 
MODULE_NAME: nt  
 
DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa  
 
IMAGE_NAME: memory_corruption  
 
FAILURE_BUCKET_ID: 0xA_nt!MiInsertPageInFreeList+17d  
 
BUCKET_ID: 0xA_nt!MiInsertPageInFreeList+17d  
 
Followup: MachineOwner  
---------  

Merci

mood
Publicité
Posté le 22-03-2009 à 13:48:12  profilanswer
 


Aller à :
Ajouter une réponse
  FORUM HardWare.fr
  Hardware
  Matériels & problèmes divers

  BSoD, mais pourquoi??

 

Sujets relatifs
BSoD lors lancement des jeuxProblème de bsod sur certains jeux
Nombreuses apparitions de BSOD.Mercibsod apres instal msi 4850
Erreur lors de l'installation de windows/BSODFreeze/bsod intempestif, y en a marre !!!
Problème BSOD inexpliqué sur PC HP8Go de RAM nécessitent des modifications du BIOS ? BSOD inside
Hd 4870 powercolor problème BSOD.gros probléme de BSOD depuis un changement de cm+cg
Plus de sujets relatifs à : BSoD, mais pourquoi??


Copyright © 1997-2025 Groupe LDLC (Signaler un contenu illicite / Données personnelles)