Regelmässig BlueScreen plus CD brennen geht nicht mehr - dump attached

Hi @ll

Ich habe seit einigen Wochen folgendes Problem:

-CD brennen geht nicht mehr: Keine Fehlermeldung, Sanduhr (PC hängt bis ich die CD wieder rausnehme

-Regelmässiger BlueScreen, so ca. alle 1-4 Stunden

Ein Freund hat mir geholfen, ein dump file vom Blue Screen zu erstellen (siehe unten) und meinte, es könnte am WlAN oder Netzwerkadapter generell liegen. Habe heute von 0800-1800 den PC laufen lassen mit WLAN deaktiviert, ist nicht abgestürzt - habe allerdings während dieser Zeit nicht daran gearbeitet und das CD Problem ist damit auch nicht gelöst :-\ Any ideas? Kann jemand aus der unten angehängten Meldung etwas lesen? Danke



bafb8000 bafbba60 TPHKDRV Wed Mar 10 02:10:30 2004 (404E6B06)
bafbc000 bafbe280 rasacd Fri Aug 17 22:55:39 2001 (3B7D84CB)
bf800000 bf9c2200 win32k Thu Mar 08 14:47:34 2007 (45F013F6)
bf9c3000 bf9d4580 dxg Wed Aug 04 08:00:51 2004 (41107B93)
bf9d5000 bfa38000 ati2dvag Wed Feb 11 03:42:38 2004 (4029969E)
bfa38000 bfb0c400 ati3d1ag Wed Feb 11 03:34:11 2004 (402994A3)
bffa0000 bffe5c00 ATMFD Wed Aug 04 09:55:27 2004 (4110966F)
f7416000 f7442a80 NDIS Wed Aug 04 08:14:27 2004 (41107EC3)
f7443000 f7459780 KSecDD Wed Aug 04 07:59:45 2004 (41107B51)
f745a000 f746e560 drvmcdb Thu Nov 06 05:06:51 2003 (3FA9C8DB)
f746f000 f7480f00 sr Wed Aug 04 08:06:22 2004 (41107CDE)
f7481000 f74a0780 fltmgr Mon Aug 21 11:14:57 2006 (44E97991)
f74a1000 f74b8480 atapi Wed Aug 04 07:59:41 2004 (41107B4D)
f74b9000 f74d7d80 ftdisk Fri Aug 17 22:52:41 2001 (3B7D8419)
f74d8000 f74f5600 pcmcia Wed Aug 04 08:07:45 2004 (41107D31)
f74f6000 f7502880 rasl2tp Wed Aug 04 08:14:21 2004 (41107EBD)
f7506000 f7514b80 drmk Wed Aug 04 08:07:54 2004 (41107D3A)
f7516000 f7524100 redbook Wed Aug 04 07:59:34 2004 (41107B46)
f7526000 f7532180 cdrom Wed Aug 04 07:59:52 2004 (41107B58)
f7536000 f7540380 imapi Wed Aug 04 08:00:12 2004 (41107B6C)
f7556000 f7563000 i8042prt Wed Aug 04 08:14:36 2004 (41107ECC)
f7566000 f756fd00 intelppm Wed Aug 04 07:59:19 2004 (41107B37)
f7576000 f757e7e0 tfsncofs Wed Oct 22 21:41:30 2003 (3F96DD6A)
f7596000 f75a6a80 pci Wed Aug 04 08:07:45 2004 (41107D31)
f75a7000 f75d5180 ACPI Wed Aug 04 08:07:35 2004 (41107D27)
f75f7000 f75ffd80 isapnp Fri Aug 17 22:58:01 2001 (3B7D8559)
f7607000 f7611500 MountMgr Wed Aug 04 07:58:29 2004 (41107B05)
f7617000 f7624d60 Shockprf Wed Dec 17 05:50:09 2003 (3FDFE081)
f7627000 f7634200 VolSnap Wed Aug 04 08:00:14 2004 (41107B6E)
f7637000 f763fe00 disk Wed Aug 04 07:59:53 2004 (41107B59)
f7647000 f7653200 CLASSPNP Wed Aug 04 08:14:26 2004 (41107EC2)
f7657000 f7661580 agp440 Wed Aug 04 08:07:40 2004 (41107D2C)
f76a7000 f76b6000 APMDrive Thu Apr 14 17:26:37 2005 (425E8BAD)
f76c7000 f76d6900 Cdfs Wed Aug 04 08:14:09 2004 (41107EB1)
f76f7000 f7700540 drvnddm Sat Jun 21 01:55:12 2003 (3EF39EE0)
f7707000 f770d200 PCIIDEX Wed Aug 04 07:59:40 2004 (41107B4C)
f770f000 f7713900 PartMgr Sat Aug 18 03:32:23 2001 (3B7DC5A7)
f7717000 f771be20 PxHelp20 Mon Apr 25 21:48:02 2005 (426D4972)
f772f000 f7735800 usbehci Wed Aug 04 08:08:34 2004 (41107D62)
f7737000 f773d280 kbdclass Wed Aug 04 07:58:32 2004 (41107B08)
f773f000 f7744c00 mouclass Wed Aug 04 07:58:32 2004 (41107B08)
f7747000 f7748000 fdc unavailable (00000000)
f774f000 f7756000 nscirda Wed Aug 04 08:00:49 2004 (41107B91)
f7757000 f775e000 ibmpmdrv Thu Jul 03 04:54:03 2003 (3F039ACB)
f7767000 f776e680 Modem Wed Aug 04 08:08:04 2004 (41107D44)
f776f000 f7773c80 rasirda Fri Aug 17 22:51:29 2001 (3B7D83D1)
f7777000 f777b880 TDI Wed Aug 04 08:07:47 2004 (41107D33)
f777f000 f7783580 ptilink Fri Aug 17 22:49:53 2001 (3B7D8371)
f7787000 f778b080 raspti Fri Aug 17 22:55:32 2001 (3B7D84C4)
f779f000 f77a4a80 ssrtln Mon Jul 14 20:28:21 2003 (3F12F645)
f77a7000 f77ac200 vga Wed Aug 04 08:07:06 2004 (41107D0A)
f77af000 f77b3a80 Msfs Wed Aug 04 08:00:37 2004 (41107B85)
f77b7000 f77be880 Npfs Wed Aug 04 08:00:38 2004 (41107B86)
f77bf000 f77c5000 TSMAPIP Fri Jun 28 05:59:23 2002 (3D1BDF1B)
f77c7000 f77cf000 Tppwr Thu Dec 25 10:53:58 2003 (3FEAB3B6)
f77cf000 f77d5000 TDSMAPI Wed Oct 22 12:54:26 2003 (3F9661E2)
f77df000 f77e6b80 usbccgp Wed Aug 04 08:08:45 2004 (41107D6D)
f77e7000 f77ed180 HIDPARSE Wed Aug 04 08:08:15 2004 (41107D4F)
f77ef000 f77f5500 usbprint Wed Aug 04 08:01:23 2004 (41107BB3)
f77f7000 f77fd780 USBSTOR Wed Aug 04 08:08:44 2004 (41107D6C)
f77ff000 f7807000 Smapint Wed Dec 04 14:58:05 2002 (3DEE09ED)
f780f000 f7815420 tfsnboio Wed Oct 22 21:41:18 2003 (3F96DD5E)
f781f000 f7824000 usbuhci Wed Aug 04 08:08:34 2004 (41107D62)
f787c000 f7896580 Mup Wed Aug 04 08:15:20 2004 (41107EF8)
f7897000 f789a000 BOOTVID Fri Aug 17 22:49:09 2001 (3B7D8345)
f789b000 f789d480 compbatt Fri Aug 17 22:57:58 2001 (3B7D8556)
f789f000 f78a2f80 BATTC Fri Aug 17 22:57:52 2001 (3B7D8550)
f78a3000 f78a5f80 ACPIEC Fri Aug 17 22:57:55 2001 (3B7D8553)
f7927000 f7929580 ndistapi Fri Aug 17 22:55:29 2001 (3B7D84C1)
f7943000 f7946c80 mssmbios Wed Aug 04 08:07:47 2004 (41107D33)
f7947000 f7949580 vmnetadapter Thu Dec 16 09:13:25 2004 (41C143A5)
f794b000 f794d800 VMNET Thu Dec 16 09:13:19 2004 (41C1439F)
f7987000 f7988b80 kdcom Fri Aug 17 22:49:10 2001 (3B7D8346)
f7989000 f798a100 WMILIB Fri Aug 17 23:07:23 2001 (3B7D878B)
f798b000 f798c480 speedfan Sun Sep 24 15:28:47 2006 (4516880F)
f798d000 f798eda0 PenClass Mon Apr 09 23:44:59 2001 (3AD22D5B)
f7995000 f7996b80 ParVdm Fri Aug 17 22:49:49 2001 (3B7D836D)
f7997000 f7998400 EGATHDRV Mon Jun 23 12:47:13 2003 (3EF6DAB1)
f799f000 f79a08a0 tfsnpool Wed Oct 22 21:41:10 2003 (3F96DD56)
f79b7000 f79b8100 dump_WMILIB Fri Aug 17 23:07:23 2001 (3B7D878B)
f79d1000 f79d2280 USBD Fri Aug 17 23:02:58 2001 (3B7D8682)
f79d7000 f79d8100 swenum Wed Aug 04 07:58:41 2004 (41107B11)
f79db000 f79dd000 i2omgmt Wed Aug 04 08:00:50 2004 (41107B92)
f79dd000 f79de5c0 sscdbhk5 Mon Jul 14 20:28:38 2003 (3F12F656)
f79df000 f79e0f00 Fs_Rec Fri Aug 17 22:49:37 2001 (3B7D8361)
f79e1000 f79e2080 Beep Fri Aug 17 22:47:33 2001 (3B7D82E5)
f79e3000 f79e4080 mnmdd Fri Aug 17 22:57:28 2001 (3B7D8538)
f79e5000 f79e6080 RDPCDD Fri Aug 17 22:46:56 2001 (3B7D82C0)
f79f1000 f79f2800 SYMDNS Wed Oct 31 04:36:49 2007 (4727F851)
f79f9000 f79fa900 splitter Wed Jun 14 10:47:46 2006 (448FCD32)
f7a4f000 f7a4fd00 pciide Fri Aug 17 22:51:49 2001 (3B7D83E5)
f7a50000 f7a50d80 OPRGHDLR Fri Aug 17 22:57:55 2001 (3B7D8553)
f7a51000 f7a51680 giveio Thu Apr 04 04:33:25 1996 (316334F5)
f7a7e000 f7a7ed00 dxgthk Fri Aug 17 22:53:12 2001 (3B7D8438)
f7aad000 f7aad8a0 tfsndres Wed Oct 22 21:42:02 2003 (3F96DD8A)
f7b52000 f7bde400 Ntfs Fri Feb 09 12:10:31 2007 (45CC56A7)

Unloaded modules:
a53de000 a5409000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a53de000 a5409000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a53de000 a5409000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a53de000 a5409000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f79f3000 f79f5000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a555d000 a5588000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a56f8000 a5723000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a5953000 a597e000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f79ab000 f79ad000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b98cf000 b98d0000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a613f000 a616a000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a616a000 a618d000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a6c9f000 a6cac000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a65a8000 a65b6000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f79fb000 f79fd000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
baaa8000 baab4000 p3.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7797000 f779c000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
bafc0000 bafc3000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {f78af9d0, 2, 1, 804d9b68}

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : w70n51.sys ( w70n51+2a41e )

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

Finished dump check

C:\Program Files\Debugging Tools for Windows>

Hi,

von meiner Bluescreen-Problem-Zeit weiß ich noch folgendes: Ganz unten in der Dump-Datei findest Du in der Regel den Treiber, der den Absturz verursacht hat:

Probably caused by : w70n51.sys ( w70n51+2a41e )

In Deinem Fall ist es w70n51.sys.

Sinnvoll wäre hier, das Dumpfile von jedem Bluescreen zu prüfen, ob hier ständig dieser eine Treiber erscheint. Wenn ja, kannst Du mit Sicherheit sagen, dass es an diesem liegt. Sollte jedoch jedes Mal ein anderer Treiber drinstehen, kann es gut sein, dass es Probleme mit dem RAM gibt (war zumindest bei mir so).

Zu dem CD-Problem kann ich Dir leider nix sagen... :-\

Gruß,
Leon

Hi, ja danach hatte ich auch schon gesucht, und alle Treiberupdates geladen (WLAN Karte etc.) die bei Lenovo verfügbar sind. Komischerweise stürzt er jetzt immer noch ab, aber nur noch 1 x pro Woche, damit kann ich leben : Danke für den Hinweis