מסך כחול מזה תקופה ארוכה - תמיכה טכנית למחשבים - HWzone פורומים
עבור לתוכן
  • צור חשבון

מסך כחול מזה תקופה ארוכה

zoriza

נוצר על ידי zoriza
ב תמיכה טכנית למחשבים

Recommended Posts

zoriza Zone Wannabe

zoriza

פורסם
פורסם

הבאתי לפני כ-3 שבועות את המחשב לתיקון לאחר מספר רב של פעמים שהופיע מסך כחול . הם טענו שמקור הבעיה היה מכיוון שמערכת ההפעלה Vista אינה פועלת עם צורב SATA וטענו לטענתם שהתקנתי בפוקס את Vista ולכן הם החליפו לי צורב . חזרתי הביית ומייד מגלה שוב מסך כחול תוך כדי הפעלת המערכת . פניתי אליהם שוב , ובסופו של דבר החליפו מעבד , כמובן שגם זה לא עזר . הם טענו שהם עשו את כל הבדיקות ( מאמץ , זיכרון , דיסק קשיח וכו' ) וטענו שלא היית שום תקלה .

amd d.c 4600 2.4

4*512 667

300gb hitachi

gefroce 8500 512mb

msi 9kn ultraf 570

ניסיתי מגוון גרסאות של מערכות הפעלה והרצתי אינספור בדיקות אך לא התגלו שום שגיאות . במצב בטוח לא הופיע מעולם מסך כחול , מידי פעם היית שגיאה 00.....ובסוף הספרה 9 , מידי פעם sql,memory וכו' .

help !

*אני חייב לציין שלאחר שהקנתי מבלי להתקין שום דבר אחר עדין מופיע מסך כחול .

קישור לתוכן
שתף באתרים אחרים
zoriza Zone Wannabe

zoriza

פורסם
  • מחבר
פורסם

מסך כחול יכול להיגרם ממאות בעיות שונות.

עיין בסטיקי לגבי ניתוח של קבצי DUMP.

פירוט קובץ דאמפ :


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


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

Symbol search path is: SRV*c:\websymbols*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free  compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.070227-2300
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sat Jan 10 13:55:22.828 2009 (GMT+2)
System Uptime: 0 days 0:05:30.572
Loading Kernel Symbols
...............................................................
.............................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                       *
*            Bugcheck Analysis                  *
*                                       *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {1c, 2, 1, 8053fa25}

Probably caused by : memory_corruption ( nt!MiDecrementCloneBlockReference+a )

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

0: 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: 0000001c, 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: 8053fa25, address which referenced memory

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


WRITE_ADDRESS: 0000001c 

CURRENT_IRQL: 2

FAULTING_IP: 
nt!MiDecrementCloneBlockReference+a
8053fa25 ff4b1c     dec   dword ptr [ebx+1Ch]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: drwtsn32.exe

LAST_CONTROL_TRANSFER: from 80529fcb to 8053fa25

STACK_TEXT: 
b6a2eaa0 80529fcb 00000000 e1003600 87a25020 nt!MiDecrementCloneBlockReference+0xa
b6a2ead8 804f11e3 c000a198 02866000 00000000 nt!MiDeletePte+0x324
b6a2eb9c 804f521d e130cc58 02a95fff 00000000 nt!MiDeleteVirtualAddresses+0x162
b6a2ec48 805006c1 87a25020 87c717a8 87a25158 nt!MiRemoveMappedView+0x211
b6a2ec80 8058dfca 00a25020 87ae9bf8 87ae9e40 nt!MmCleanProcessAddressSpace+0x26e
b6a2ed08 805739b4 00000000 87ae9bf8 00000000 nt!PspExitThread+0x621
b6a2ed28 8058e369 87ae9bf8 00000000 b6a2ed64 nt!PspTerminateThreadByPointer+0x52
b6a2ed54 804dd99f 00000000 00000000 0006ff2c nt!NtTerminateProcess+0x118
b6a2ed54 7c90eb94 00000000 00000000 0006ff2c nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0006ff2c 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP: 
nt!MiDecrementCloneBlockReference+a
8053fa25 ff4b1c     dec   dword ptr [ebx+1Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiDecrementCloneBlockReference+a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 45e550ef

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiDecrementCloneBlockReference+a

BUCKET_ID: 0xA_nt!MiDecrementCloneBlockReference+a

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

קישור לתוכן
שתף באתרים אחרים
zoriza Zone Wannabe

zoriza

פורסם
  • מחבר
פורסם

לבדוק עכשיו מה אומר דאמפ חדש.



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


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

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.      *
* Use .symfix to have the debugger choose a symbol path.          *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                  *
* The Symbol Path can be set by:                  *
*  using the _NT_SYMBOL_PATH environment variable.         *
*  using the -y <symbol_path> argument when starting the debugger. *
*  using .sympath and .sympath+                  *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3.3264) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Jan 12 19:15:13.750 2009 (GMT+2)
System Uptime: 0 days 0:02:07.484
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                  *
* The Symbol Path can be set by:                  *
*  using the _NT_SYMBOL_PATH environment variable.         *
*  using the -y <symbol_path> argument when starting the debugger. *
*  using .sympath and .sympath+                  *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
.........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                       *
*            Bugcheck Analysis                  *
*                                       *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {24, 2, 0, 80515da9}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                  ***
***                                  ***
***  Your debugger is not using the correct symbols         ***
***                                  ***
***  In order for this command to work properly, your symbol path  ***
***  must point to .pdb files that have full type information.   ***
***                                  ***
***  Certain .pdb files (such as the public OS symbols) do not   ***
***  contain the required information. Contact the group that   ***
***  provided you with these symbols if you need this command to  ***
***  work.                             ***
***                                  ***
***  Type referenced: nt!_KPRCB                   ***
***                                  ***
*************************************************************************
*************************************************************************
***                                  ***
***                                  ***
***  Your debugger is not using the correct symbols         ***
***                                  ***
***  In order for this command to work properly, your symbol path  ***
***  must point to .pdb files that have full type information.   ***
***                                  ***
***  Certain .pdb files (such as the public OS symbols) do not   ***
***  contain the required information. Contact the group that   ***
***  provided you with these symbols if you need this command to  ***
***  work.                             ***
***                                  ***
***  Type referenced: nt!_KPRCB                   ***
***                                  ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                  *
* The Symbol Path can be set by:                  *
*  using the _NT_SYMBOL_PATH environment variable.         *
*  using the -y <symbol_path> argument when starting the debugger. *
*  using .sympath and .sympath+                  *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                  *
* The Symbol Path can be set by:                  *
*  using the _NT_SYMBOL_PATH environment variable.         *
*  using the -y <symbol_path> argument when starting the debugger. *
*  using .sympath and .sympath+                  *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+3eda9 )

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: 00000024, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 80515da9, address which referenced memory

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                  ***
***                                  ***
***  Your debugger is not using the correct symbols         ***
***                                  ***
***  In order for this command to work properly, your symbol path  ***
***  must point to .pdb files that have full type information.   ***
***                                  ***
***  Certain .pdb files (such as the public OS symbols) do not   ***
***  contain the required information. Contact the group that   ***
***  provided you with these symbols if you need this command to  ***
***  work.                             ***
***                                  ***
***  Type referenced: nt!_KPRCB                   ***
***                                  ***
*************************************************************************
*************************************************************************
***                                  ***
***                                  ***
***  Your debugger is not using the correct symbols         ***
***                                  ***
***  In order for this command to work properly, your symbol path  ***
***  must point to .pdb files that have full type information.   ***
***                                  ***
***  Certain .pdb files (such as the public OS symbols) do not   ***
***  contain the required information. Contact the group that   ***
***  provided you with these symbols if you need this command to  ***
***  work.                             ***
***                                  ***
***  Type referenced: nt!_KPRCB                   ***
***                                  ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                  *
* The Symbol Path can be set by:                  *
*  using the _NT_SYMBOL_PATH environment variable.         *
*  using the -y <symbol_path> argument when starting the debugger. *
*  using .sympath and .sympath+                  *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                  *
* The Symbol Path can be set by:                  *
*  using the _NT_SYMBOL_PATH environment variable.         *
*  using the -y <symbol_path> argument when starting the debugger. *
*  using .sympath and .sympath+                  *
*********************************************************************

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 474ffa09

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 00000024 

CURRENT_IRQL: 2

FAULTING_IP: 
nt+3eda9
80515da9 395e24     cmp   dword ptr [esi+24h],ebx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 80516537 to 80515da9

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
b706dc60 80516537 00231000 c0001188 89833938 nt+0x3eda9
b706dce0 80520ad0 00000000 00231000 c0001188 nt+0x3f537
b706dd4c 80544578 00000001 00231000 00000001 nt+0x49ad0
b706dd64 7e1e283d badb0d00 0022fb98 00000000 nt+0x6d578
b706dd68 badb0d00 0022fb98 00000000 00000000 0x7e1e283d
b706dd6c 0022fb98 00000000 00000000 00000000 0xbadb0d00
b706dd70 00000000 00000000 00000000 00000000 0x22fb98


STACK_COMMAND: kb

FOLLOWUP_IP: 
nt+3eda9
80515da9 395e24     cmp   dword ptr [esi+24h],ebx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+3eda9

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

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



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


Loading Dump File [C:\WINDOWS\Minidump\Mini011209-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.     *
* Use .symfix to have the debugger choose a symbol path.         *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                 *
* The Symbol Path can be set by:                  *
* using the _NT_SYMBOL_PATH environment variable.        *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+                  *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3.3264) MP (2 procs) Free  compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Jan 12 19:18:07.875 2009 (GMT+2)
System Uptime: 0 days 0:02:28.597
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                 *
* The Symbol Path can be set by:                  *
* using the _NT_SYMBOL_PATH environment variable.        *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+                  *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
.........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                      *
*            Bugcheck Analysis                  *
*                                      *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {1c, 2, 1, 80525789}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                 ***
***                                 ***
***  Your debugger is not using the correct symbols        ***
***                                 ***
***  In order for this command to work properly, your symbol path ***
***  must point to .pdb files that have full type information.   ***
***                                 ***
***  Certain .pdb files (such as the public OS symbols) do not   ***
***  contain the required information. Contact the group that   ***
***  provided you with these symbols if you need this command to  ***
***  work.                             ***
***                                 ***
***  Type referenced: nt!_KPRCB                  ***
***                                 ***
*************************************************************************
*************************************************************************
***                                 ***
***                                 ***
***  Your debugger is not using the correct symbols        ***
***                                 ***
***  In order for this command to work properly, your symbol path ***
***  must point to .pdb files that have full type information.   ***
***                                 ***
***  Certain .pdb files (such as the public OS symbols) do not   ***
***  contain the required information. Contact the group that   ***
***  provided you with these symbols if you need this command to  ***
***  work.                             ***
***                                 ***
***  Type referenced: nt!_KPRCB                  ***
***                                 ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                 *
* The Symbol Path can be set by:                  *
* using the _NT_SYMBOL_PATH environment variable.        *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+                  *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                 *
* The Symbol Path can be set by:                  *
* using the _NT_SYMBOL_PATH environment variable.        *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+                  *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+4e789 )

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

0: 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: 0000001c, 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: 80525789, address which referenced memory

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                 ***
***                                 ***
***  Your debugger is not using the correct symbols        ***
***                                 ***
***  In order for this command to work properly, your symbol path ***
***  must point to .pdb files that have full type information.   ***
***                                 ***
***  Certain .pdb files (such as the public OS symbols) do not   ***
***  contain the required information. Contact the group that   ***
***  provided you with these symbols if you need this command to  ***
***  work.                             ***
***                                 ***
***  Type referenced: nt!_KPRCB                  ***
***                                 ***
*************************************************************************
*************************************************************************
***                                 ***
***                                 ***
***  Your debugger is not using the correct symbols        ***
***                                 ***
***  In order for this command to work properly, your symbol path ***
***  must point to .pdb files that have full type information.   ***
***                                 ***
***  Certain .pdb files (such as the public OS symbols) do not   ***
***  contain the required information. Contact the group that   ***
***  provided you with these symbols if you need this command to  ***
***  work.                             ***
***                                 ***
***  Type referenced: nt!_KPRCB                  ***
***                                 ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                 *
* The Symbol Path can be set by:                  *
* using the _NT_SYMBOL_PATH environment variable.        *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+                  *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                 *
* The Symbol Path can be set by:                  *
* using the _NT_SYMBOL_PATH environment variable.        *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+                  *
*********************************************************************

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 474ffa09

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 0000001c 

CURRENT_IRQL: 2

FAULTING_IP: 
nt+4e789
80525789 ff4b1c     dec  dword ptr [ebx+1Ch]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 80523d1c to 80525789

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
b6a2bb40 80523d1c 00000000 00000000 898e6c28 nt+0x4e789
b6a2bb7c 80523fa0 00000000 01233000 00000000 nt+0x4cd1c
b6a2bc44 8051a1c5 e2a453a0 012b1fff 00000000 nt+0x4cfa0
b6a2bcf4 805b2d71 898e6c28 89880df8 b6a2bd64 nt+0x431c5
b6a2bd38 805b2e60 87cb9588 881bc6e8 00000000 nt+0xdbd71
b6a2bd54 8054161c ffffffff 898e6c28 00e5bca4 nt+0xdbe60
b6a2bd64 7c90e4f4 badb0d00 00e5bc94 00000000 nt+0x6a61c
b6a2bd68 badb0d00 00e5bc94 00000000 00000000 0x7c90e4f4
b6a2bd6c 00e5bc94 00000000 00000000 00000000 0xbadb0d00
b6a2bd70 00000000 00000000 00000000 00000000 0xe5bc94


STACK_COMMAND: kb

FOLLOWUP_IP: 
nt+4e789
80525789 ff4b1c     dec  dword ptr [ebx+1Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+4e789

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

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

קישור לתוכן
שתף באתרים אחרים
Ivan Zone Master

Ivan

פורסם
פורסם

אנליזה לא טובה בגלל לא נטען SYMBOLE TABLE

תריץ עוד פעם נכון.

שגיאה IRQL_NOT_LESS_OR_EQUAL בגלל דרייבר

איזה ? אי אפשר לדעת.

לחשוד בדריבר בלי חתימה. לריץ הפקודה

sigverif

ותקבל רשימה של דריברים לא חתומים. אולי 1 מהם סיבה. לנסות

לעדכן אותם. ולעדכן בכל עידכונים קריטים שיש.

קישור לתוכן
שתף באתרים אחרים

ארכיון

דיון זה הועבר לארכיון ולא ניתן להוסיף בו תגובות חדשות.

עבור לרשימת הדיונים
×
  • צור חדש...