Doom9's Forum - View Single Post - madVR - high quality video renderer (GPU assisted)

franketto · 28th July 2018, 20:16

Instead the BSOD one has these:

3x Warning Kernel-PnP:

Code:

cannot load driver \Driver\VMSP for the device ROOT\VMS_VSMP\0000 
then for ROOT\VMS_VSMP\0001 and ROOT\VMS_VSMP\0002

Code:

Provider 

   [ Name]  Microsoft-Windows-Kernel-PnP 
   [ Guid]  {9C205A39-1250-487D-ABD7-E831C6290539} 
 
   EventID 219 
 
   Version 0 
 
   Level 3 
 
   Task 212 
 
   Opcode 0 
 
   Keywords 0x8000000000000000 
 
  - TimeCreated 

   [ SystemTime]  2018-06-15T11:57:47.536750800Z 
 
   EventRecordID 6018 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  4 
   [ ThreadID]  420 
 
   Channel System 
 
 
  - Security 

   [ UserID]  S-1-5-18 
 

- EventData 

  DriverNameLength 18 
  DriverName ROOT\VMS_VSMP\0000 
  Status 3221226092 
  FailureNameLength 12 
  FailureName \Driver\VMSP 
  Version 0

Then the Warning of pointing device not knows the monitor,

then an error Hyper-V-VmSwitch:
Failed to get Device VlanID Regkey for Physical NIC /DEVICE/{3E39B7FB-8071-4D58-A3CE-E6F29F1786E6}. vSwitch will be created on this Physical NIC without VlanID being inherited by HostVNic. Status = can't find object name.

Then another Warning of pointing device not knows the monitor,

Then again 4x Errors Hyper-V-VmSwitch:
-) The operation 'Get Info' failed on nic 37044452-FBC8-4E5B-B8BD-D5B3060C51F5 (Friendly Name: ). Status = Parametro non valido passato ad un servizio o ad una funzione..
-) The operation 'Get Info' failed on nic 37044452-FBC8-4E5B-B8BD-D5B3060C51F5 (Friendly Name: ). Status = Parametro non valido passato ad un servizio o ad una funzione..
-) Failed to connect NIC 37044452-FBC8-4E5B-B8BD-D5B3060C51F5 (Friendly Name: Opzione predefi) to port (Friendly Name: ) on switch C08CB7B8-9B3C-408E-8E30-5E16A3AEB444 (Friendly Name: Opzione predefinita), status = Impossibile trovare il nome dell'oggetto..
-) Failed to enable miniport NIC 37044452-FBC8-4E5B-B8BD-D5B3060C51F5 (Friendly Name: Opzione predefi), status = Impossibile trovare il nome dell'oggetto..

And finally the BugCheck:
Il computer è stato riavviato da un controllo errori. Controllo errori: 0x00000119 (0x0000000000100000, 0x0000000000000001, 0x0000000000000000, 0xffffe00a4b512000).
I dettagli sono stati salvati in: C:\WINDOWS\MEMORY.DMP. ID segnalazione: 77ea78e5-3300-41b2-887c-6fef0cb21c72.
Sadly I have not looked at the memory.dmp and I don't find it now...

So, that's all, let me know if you have some ideas or request some more details of these events and I'll post them.
Thank you a lot fot the patience and the support, I'm really upset with these crashes that don't let me use madVR!

28th July 2018, 20:16	#51872 \| Link
franketto Registered User Join Date: May 2014 Posts: 74	Instead the BSOD one has these: 3x Warning Kernel-PnP: Code: cannot load driver \Driver\VMSP for the device ROOT\VMS_VSMP\0000 then for ROOT\VMS_VSMP\0001 and ROOT\VMS_VSMP\0002 Code: Provider [ Name] Microsoft-Windows-Kernel-PnP [ Guid] {9C205A39-1250-487D-ABD7-E831C6290539} EventID 219 Version 0 Level 3 Task 212 Opcode 0 Keywords 0x8000000000000000 - TimeCreated [ SystemTime] 2018-06-15T11:57:47.536750800Z EventRecordID 6018 Correlation - Execution [ ProcessID] 4 [ ThreadID] 420 Channel System - Security [ UserID] S-1-5-18 - EventData DriverNameLength 18 DriverName ROOT\VMS_VSMP\0000 Status 3221226092 FailureNameLength 12 FailureName \Driver\VMSP Version 0 Then the Warning of pointing device not knows the monitor, then an error Hyper-V-VmSwitch: Failed to get Device VlanID Regkey for Physical NIC /DEVICE/{3E39B7FB-8071-4D58-A3CE-E6F29F1786E6}. vSwitch will be created on this Physical NIC without VlanID being inherited by HostVNic. Status = can't find object name. Then another Warning of pointing device not knows the monitor, Then again 4x Errors Hyper-V-VmSwitch: -) The operation 'Get Info' failed on nic 37044452-FBC8-4E5B-B8BD-D5B3060C51F5 (Friendly Name: ). Status = Parametro non valido passato ad un servizio o ad una funzione.. -) The operation 'Get Info' failed on nic 37044452-FBC8-4E5B-B8BD-D5B3060C51F5 (Friendly Name: ). Status = Parametro non valido passato ad un servizio o ad una funzione.. -) Failed to connect NIC 37044452-FBC8-4E5B-B8BD-D5B3060C51F5 (Friendly Name: Opzione predefi) to port (Friendly Name: ) on switch C08CB7B8-9B3C-408E-8E30-5E16A3AEB444 (Friendly Name: Opzione predefinita), status = Impossibile trovare il nome dell'oggetto.. -) Failed to enable miniport NIC 37044452-FBC8-4E5B-B8BD-D5B3060C51F5 (Friendly Name: Opzione predefi), status = Impossibile trovare il nome dell'oggetto.. And finally the BugCheck: Il computer è stato riavviato da un controllo errori. Controllo errori: 0x00000119 (0x0000000000100000, 0x0000000000000001, 0x0000000000000000, 0xffffe00a4b512000). I dettagli sono stati salvati in: C:\WINDOWS\MEMORY.DMP. ID segnalazione: 77ea78e5-3300-41b2-887c-6fef0cb21c72. Sadly I have not looked at the memory.dmp and I don't find it now... So, that's all, let me know if you have some ideas or request some more details of these events and I'll post them. Thank you a lot fot the patience and the support, I'm really upset with these crashes that don't let me use madVR!