Forum Clubic

Rapport d'un BSOD

Bonsoir,

Gros souci avec l’audio sous W7 depuis que je suis passé en 64bits. Non seulement j’ai des sortes de “grillons numériques” qui passent dans les hp par moments, mais voilà que les BSOD se succèdent les uns aux autres…

Je soupçonne ma carte son, une tascam us-122l, d’être totalement incompatible avec le 64 bits, ce malgré l’installation de l’ultime driver, officiellement compatible. Même Asio4All, un driver “dédié” MAO, n’a pas résolu le souci.

Absolument TOUS mes drivers sont à jours (vérifié avec ma-config.com).

Voici le rapport de Whocrashed, qui fait suite à un BSOD tout frais. Si quelqu’un a un tuyau…

[quote=""]

On Sun 08/04/2012 20:27:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040812-19578-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x16F4B)
Bugcheck code: 0xFE (0x4, 0xFFFFFA8004108010, 0xFFFFFA8003D95010, 0xFFFFFA80054C7010)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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 Sun 08/04/2012 11:32:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040812-19484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFFA8007E9E000, 0x0, 0xFFFFF880041F5A98, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.

On Sun 08/04/2012 11:32:39 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tscusb2a.sys (tscusb2a+0x9A98)
Bugcheck code: 0x50 (0xFFFFFA8007E9E000, 0x0, 0xFFFFF880041F5A98, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\tscusb2a.sys
product: TASCAM US-122L/144 WDM Driver
company: TASCAM
description: TASCAM US-122L/144 WDM Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: tscusb2a.sys (TASCAM US-122L/144 WDM Driver, TASCAM).
Google query: tscusb2a.sys TASCAM PAGE_FAULT_IN_NONPAGED_AREA

On Sun 08/04/2012 08:51:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040812-25646-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFFA8008625000, 0x0, 0xFFFFF88003C6AA98, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.

On Sat 07/04/2012 21:11:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040712-18813-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFFA8007ECD000, 0x0, 0xFFFFF88005F48A98, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.

On Sat 07/04/2012 18:49:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040712-19593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFFA8009D13000, 0x0, 0xFFFFF88005F1AA98, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.


Conclusion

6 crash dumps have been found and analyzed. 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:

tscusb2a.sys (TASCAM US-122L/144 WDM Driver, TASCAM)

[quote=""]

PS: ma config

  • OS : MS Windows 7 Home Premium 64-bit SP1
  • CM : Asus M5A78L-M LX V2
  • proco : AMD FX™-4170 Quad-Core Processor
  • ram : DDR3 Corsair 4Go
  • carte son : Tascam Us-122L
  • driver audio alternatif : Asio4all
    Edité le 08/04/2012 à 22:48

Je rajoute au passage des extraits du rapport fourni par ma-config.com :

[quote=""]

Source du crash rtndpt60.sys+FB603010
Chemin C:\Windows\system32\drivers\rtndpt60.sys
Description Realtek NDIS Protocol Driver
Version du produit 6.0.717.2009
Compagnie Realtek

Source du crash ntoskrnl.exe+7CD40
Chemin C:\Windows\system32\ntoskrnl.exe
Description NT Kernel & System
Version du produit 6.1.7601.17727
Compagnie Microsoft Corporation
Taille 3.73 Mo

Source du crash ntoskrnl.exe+7CD40
Chemin C:\Windows\system32\ntoskrnl.exe
Description NT Kernel & System
Version du produit 6.1.7601.17727
Compagnie Microsoft Corporation
Taille 3.73 Mo

Source du crash usbport.sys+12AED
Chemin C:\Windows\system32\drivers\usbport.sys
Description Pilote de port USB 1.1 & 2.0
Version du produit 6.1.7601.17586
Compagnie Microsoft Corporation

Source du crash ntoskrnl.exe+7CD40
Chemin C:\Windows\system32\ntoskrnl.exe
Description NT Kernel & System
Version du produit 6.1.7601.17727
Compagnie Microsoft Corporation
Taille 3.73 Mo

Bonjour .

voir ce site de référence sur les bug check code

msdn.microsoft.com…

Merci pour le lien.

Donc, si je résume les bug check code :

0xFE (0x4, 0xFFFFFA8004108010, 0xFFFFFA8003D95010, 0xFFFFFA80054C7010) --> The caller has submitted an IRP that is already pending in the USB bus driver.

Cela signifie-t-il que sur ce crash, il y a eu conflit entre le driver natif de la tascam et le driver Asio4all ?

0x50 --> This indicates that invalid system memory has been referenced.

Problème de mémoire, problème avec du hardware. Je ne sais pas trop comment l’interpréter, si ce n’est que la gestion de mémoire est foireuse entre la Tascam et Seven…

Bon, maintenant… que faire de tout cela ?.. Avant de changer de carte, je vais tenter de lancer Asio4all pour la MAO, et de le desactiver dès que j’ai besoin d’autre chose. A voir si ça tient, mais j’ai comme un doute…

Ah… petit test très concluant :

En ouvrant l’interface d’Asio4all, en activant la tascam et le chipset son de la CM, gros BSOD…
J’ai donc désinstallé le chipset de la CM.

Maintenant, reste à voir comment se comporte asio4all sur la durée… je crains le retour des grillons dans le casque !

Arf… re-BSOD !

Mon erreur ?

Cubase passant par asio4all, et libérant ce pilote si un autre programme passe au premier plan, j’ai voulu aller sur le net.
Lorsque je suis revenu sous Cubase… BSOD…

Il va donc me falloir “couper” asio4all dès que je quitte Cubase…

A suivre !