Meine Idee ist nun,
eine gleiche Platte zu besorgen und dann die Platienen zu tauschen.
Könnte das gehen oder mach dich die andere Platte damit auch noch kaputt
?
Beiträge von extrabreit
-
-
Tja....ähm das Problem hat sich erledigt, Die Platte "C" hat den Geist
aufgegeben.Hatte die Speicher nochmal ersetzt und danach lief der
eigentlich ohne Probleme.Gestern dann wollte ich den einschalten und nix
war mehr .Der hat die Platte nicht mehr erkannt.Auch in einem anderen PC
wurde die Platte nicht mehr erkannt.Die Platine der FP roch auch etwas
seltsam. Es sind aber keine Verschmorungen zu erkennen. Es ist die
Hitachi Sata 160 GB Platte.Ärgerlich ist nur, dass alles Daten
und Einstellungen erst mal futsch sind und natürlich die Sicherung auf
der Partition "D" liegen....auf der gleichen Platte Meine Idee ist nun,
eine gleiche Platte zu besorgen und dann die Platienen zu tauschen.
Könnte das gehen oder mach dich die andere Platte damit auch noch kaputt
? -
keine ahnung auf der FP sind mehrere bootsysteme vorhanden aber keines funktioniert
-
Daten und Programme
-
HD Tune: Hitachi HDS721016CLA382 Health
ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 100 100 16 0 Ok
(02) Throughput Performance 121 121 54 152 Ok
(03) Spin Up Time 119 119 24 12648641 Ok
(04) Start/Stop Count 100 100 0 3616 Ok
(05) Reallocated Sector Count 100 100 5 0 Ok
(07) Seek Error Rate 100 100 67 0 Ok
(08) Seek Time Performance 136 136 20 32 Ok
(09) Power On Hours Count 99 99 0 7352 Ok
(0A) Spin Retry Count 100 100 60 0 Ok
(0C) Power Cycle Count 100 100 0 3113 Ok
(C0) Power Off Retract Count 97 97 0 3617 Ok
(C1) Load Cycle Count 97 97 0 3617 Ok
(C2) Temperature 142 142 0 983082 Ok
(C4) Reallocated Event Count 100 100 0 0 Ok
(C5) Current Pending Sector 100 100 0 0 Ok
(C6) Offline Uncorrectable 100 100 0 0 Ok
(C7) Ultra DMA CRC Error Count 200 200 0 263 OkPower On Time : 7352
Health Status : Ok -
HD Tune: ST380211AS Health
ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 106 88 6 192623116 Ok
(03) Spin Up Time 95 95 0 0 Ok
(04) Start/Stop Count 93 93 20 7804 Ok
(05) Reallocated Sector Count 100 100 36 0 Ok
(07) Seek Error Rate 89 60 30 810158051 Ok
(09) Power On Hours Count 80 80 0 18155 Ok
(0A) Spin Retry Count 100 100 97 0 Ok
(0C) Power Cycle Count 93 93 20 7739 Ok
(BB) (unknown attribute) 100 100 0 0 Ok
(BD) (unknown attribute) 100 100 0 0 Ok
(BE) Airflow Temperature 56 51 45 756416556 Ok
(C2) Temperature 44 49 0 44 Ok
(C3) Hardware ECC Recovered 47 45 0 36433463 Ok
(C5) Current Pending Sector 100 100 0 0 Ok
(C6) Offline Uncorrectable 100 100 0 0 Ok
(C7) Ultra DMA CRC Error Count 200 200 0 0 Ok
(C8) Write Error Rate 100 253 0 0 Ok
(CA) TA Counter Increased 100 253 0 0 OkPower On Time : 18155
Health Status : Ok -
HD Tune: MDT MD1200JB-00GVA0 Health
ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 200 200 51 0 Ok
(03) Spin Up Time 168 157 21 4108 Ok
(04) Start/Stop Count 90 90 40 10524 Ok
(05) Reallocated Sector Count 200 200 140 0 Ok
(07) Seek Error Rate 200 200 51 0 Ok
(09) Power On Hours Count 66 66 0 25327 Ok
(0A) Spin Retry Count 100 100 51 0 Ok
(0B) Calibration Retry Count 100 100 51 0 Ok
(0C) Power Cycle Count 92 92 0 8338 Ok
(C2) Temperature 117 101 0 33 Ok
(C4) Reallocated Event Count 200 200 0 0 Ok
(C5) Current Pending Sector 200 200 0 0 Ok
(C6) Offline Uncorrectable 200 200 0 0 Ok
(C7) Ultra DMA CRC Error Count 200 253 0 149 Ok
(C8) Write Error Rate 200 200 51 0 OkPower On Time : 25327
Health Status : Ok -
Nö, kommt nicht
-
beim start von linux umbuntu kommt das bootmenü nur bis hier
root@kids-laptop:~#

-
1x SATA 160 GB als start FP 1x 80 GB SATA Daten 1x IDI FP mit Daten
-
On
Mon 13.01.2014 20:18:17 GMT your computer crashed
crash dump file:
C:\Windows\Minidump\011314-21578-01.dmp
This was probably caused by the
following module: win32k.sys (win32k+0x46EDF)
Bugcheck code: 0x3B
(0xC0000005, 0xFFFFF96000046EDF, 0xFFFFF88005EF7EC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path:
C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description:
Mehrbenutzer-Win32-Treiber
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 that cannot be identified at this time.
On
Mon 13.01.2014 19:18:55 GMT your computer crashed
crash dump file:
C:\Windows\Minidump\011314-22140-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B
(0xC0000005, 0xFFFFF800033BCA9B, 0xFFFFF8800502BFC0, 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 that cannot be identified at
this time.
On Sun 12.01.2014 21:47:02 GMT your computer
crashed
crash dump file: C:\Windows\Minidump\011214-23843-01.dmp
This
was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x44
(0xFFFFFA8002EF3010, 0xEAE, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
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 a driver has tried to
requested an IRP be completed that is already complete.
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.
On
Sun 12.01.2014 21:42:50 GMT your computer crashed
crash dump file:
C:\Windows\Minidump\011214-23296-01.dmp
This was probably caused by the
following module: spsys.sys (Unloaded_spsys.sys+0x68EC0)
Bugcheck
code: 0x3B (0xC0000005, 0xFFFFF960000A6E70, 0xFFFFF8800633FEC0, 0x0)
Error:
SYSTEM_SERVICE_EXCEPTION
file path:
C:\Windows\system32\drivers\spsys.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: security
processor
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 that cannot be
identified at this time.
Google query: Microsoft Corporation
SYSTEM_SERVICE_EXCEPTION
On Sun 12.01.2014 00:49:50 GMT your computer
crashed
crash dump file: C:\Windows\Minidump\011214-27062-01.dmp
This
was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B
(0xC0000005, 0xFFFFF800032EE061, 0xFFFFF88005240530, 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 that cannot be identified at
this time.Conclusion
29 crash dumps
have been found and analyzed. Only 10 are included in this report. 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:spsys.sys (security processor, Microsoft
Corporation)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. -
On
Mon 13.01.2014 20:42:10 GMT your computer crashed
crash dump file:
C:\Windows\Minidump\011314-27046-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x10,
0x2, 0x0, 0xFFFFF80003251923)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
On
Mon 13.01.2014 20:39:59 GMT your computer crashed
crash dump file:
C:\Windows\Minidump\011314-24890-01.dmp
This was probably caused by the
following module: win32k.sys (win32k+0xE26CD)
Bugcheck code: 0x3B
(0xC0000005, 0xFFFFF960001526CD, 0xFFFFF88002622C70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path:
C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description:
Mehrbenutzer-Win32-Treiber
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 that cannot be identified at this time. -
System Information (local)
computer name:
HB-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows
dir: C:\Windows
Hardware: VIAK8T, K8T800-8237
CPU: AuthenticAMD AMD
Sempron(tm) Processor 3400+ AMD586, level: 15
1 logical processors, active
mask: 1
RAM: 2144919552 total
VM: 2147352576, free:
1925586944
Crash Dump Analysis
Crash dump
directory: C:\Windows\MinidumpCrash dumps are enabled on your
computer.
On
Wed 15.01.2014 09:55:54 GMT your computer crashed
crash dump file:
C:\Windows\Minidump\011514-24187-01.dmp
This was probably caused by the
following module: ntfs.sys
(Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88002F2A618,
0xFFFFF88002F29E70, 0xFFFFF80003299527)
Error: NTFS_FILE_SYSTEM
file path:
C:\Windows\system32\drivers\ntfs.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description:
NT-Dateisystemtreiber
Bug check description: This indicates a problem
occurred in the NTFS file system.
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.
On Tue 14.01.2014 17:51:41 GMT your computer
crashed
crash dump file: C:\Windows\Minidump\011414-21703-01.dmp
This
was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x18 (0x0,
0xFFFFFA80034814C0, 0x2, 0xFFFFF8A00766914F)
Error: REFERENCE_BY_POINTER
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 the reference count of an
object is illegal for the current state of the object.
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.
On
Mon 13.01.2014 23:40:44 GMT your computer crashed
crash dump file:
C:\Windows\Minidump\011414-20328-01.dmp
This was probably caused by the
following module: ataport.sys (0xFFFFF88001087C50)
Bugcheck code:
0xD1 (0x50, 0x2, 0x0, 0xFFFFF88001087C50)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path:
C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver
Extension
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 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. -
Na den PPS San nach anleitung
-
Normalerweise kein Problem, batterie überprüfen 2,83 volt hmm !
Egal vorsichtshalber Batterie gewechselt.... bios verliert immer noch die Daten.Board Kaputt ?
-
Ja, toll wenn das Board denn von DVD starten würde.
DVD LW wird im Bios erkannt,aber keine DVD startet...und ja ich habe auch schion das DVD LW gewechselt
Ich hatte hier noch eine FP mit win7 ulti 32 bit........von der FP hab ich win 7 starten können, keine ahnung wieso, im Geräte manager steht, das der RAID treiber fehlt. So wie ich das verstanden habe, ist das der treiber für die SATA FP.
Auf der ASUS Seite hab ich aber für win 7 dafür keine treiber gefunden. Ethernit funz auch nicht.
:idea:
-
Ich hab mir ein anderes Board zugelegt ASUS A8V deluxe.....ja ich weiss ist uralt aber ich hab hier ne CPU mit 4 Ghz und 4 SDram steckplätze. Ausserdem kann ich meine AGP Grafikkarte verwenden.Ich brauche den PC NICHT für Spiele.
Im alten Sysetem hatte ich 2 SATA FP eine mit 160 GB eine mit 80 GB auf der Platte "c" 160 GB ist win 7 64bit installiert. Auf der 2. sind nur Programme und Daten.
Dazu hab ich noch eine IDI FP mit 160 GB auch nur Daten installiert.Nu kriege ich das System aber nicht mit dem neuen Board zum laufen.Ich schrecke aber davor zurück zu formatiern und neu zu installieren weil dann alle meine einstellungen futsch sind. Ich hab auf der Platte "C" SATA 160 GB noch 50 GB platz.
Das Handbuch von ASUS A8V deluxe hab ich mir runtergeladen wegen der Einstellungen. Ich komme da aber irgendwie nicht weiter.
Jedenfalls hab ich das schon mal soweit, dass die SATA Platten gefunden werden. NUr das angeschlossene IDE DVD Laufwerk und die IDI FP findet der nicht.
Also ist auch im Moment an eine Win 7 start DVD nicht zu denken.Bin nu erstmal ratlos
-
http://www.arbeitvermitteln.de/images/PPS1.txt
http://www.arbeitvermitteln.de/images/PPS2.txtIch hab den Test die ganze Nacht durchlaufen lassen aber irgendwie war der morgens immer noch nicht fertig. Das ist das Ergebnis was der mir ausgespuckt hat
-
Da ist ein DVD Laufwerk drin und die DVDS /CDS laufen alle auf allen anderen PCs.
Alle Linus cds /DVDs erkennt das Laufwerk aber kein einziges Windows CD / DVD und Ja alle disks laufen auf anderen systemen
Ich komme auch nicht in den abgesicherten Modus egal welche Win FP ich rein mache
-
FP Kabel habe ich erneuert.
Ausgeschaltet wird der ganz normal durch runterfahren.ich hab aber eine mehrfachsteckdoes dran die ich abenda wenn der nicht mehr gebraucht wird abschalte.
Was mir aufgefallen ist, dass der ab und zu direkt startet wenn ich die stromleiste einschalte