Solved

BSOD Crash - nvsnpu.sys

Posted on 2006-11-30
17
1,546 Views
Last Modified: 2012-05-05
Hi,
I am currently experiencing a BSOD crash every so often with a message about NVSNPU.sys which I understand is to do with the nVidia ethernet. From reading on here and google I understand it is to do with a firewall but I am unsure on what I need to change really and if that is even the same problem. Could someone please take a look at the following screenshot and suggest any thing to try or any other diagnostics which will help me to identify what the exact problem is.

KVM Screenshot of the BSOD: http://supremacygaming.net/uploads/bsod.JPG

Thanks.
0
Comment
Question by:talkster5
  • 13
  • 4
17 Comments
 
LVL 3

Author Comment

by:talkster5
ID: 18048836
On the other similar questions on experts-exchange people have been posting minidumps which seem to help solve the problem. If someone wants these can they please let me know how to generate them and I will get them uploaded straight away.

Thanks.
0
 
LVL 3

Author Comment

by:talkster5
ID: 18050224
I found out how to use the minidump files so here is some of the output they were asking for on another question:

Result of "lm tn":

start    end        module name
80800000 80a53000   nt       ntkrpamp.exe Fri Mar 25 00:28:04 2005 (42435B14)
80a53000 80a7f000   hal      halaacpi.dll Fri Mar 25 00:28:37 2005 (42435B35)
b3cfb000 b3d2b000   kmixer   kmixer.sys   Fri Mar 25 00:30:30 2005 (42435BA6)
b3dcb000 b3ddd000   DMusic   DMusic.sys   Fri Mar 25 00:30:24 2005 (42435BA0)
b3ddd000 b3df1000   swmidi   swmidi.sys   Fri Mar 25 00:30:30 2005 (42435BA6)
b3df1000 b3e19000   aec      aec.sys      Wed Sep 29 18:24:23 2004 (415AEFC7)
b3e19000 b3e2c000   sysaudio sysaudio.sys Fri Mar 25 00:40:23 2005 (42435DF7)
b3e2c000 b3e47000   wdmaud   wdmaud.sys   Fri Mar 25 00:40:49 2005 (42435E11)
b3f5f000 b3f8c000   RDPWD    RDPWD.SYS    Wed Jun 15 16:33:14 2005 (42B04A3A)
b420c000 b4278000   srv      srv.sys      Fri Sep 01 15:32:26 2006 (44F8447A)
b42a0000 b42f0000   HTTP     HTTP.sys     Fri Mar 25 00:40:36 2005 (42435E04)
b49b8000 b49c0000   drmkaud  drmkaud.sys  Tue Mar 25 07:09:54 2003 (3E8000C2)
b588e000 b58a6080   dump_nvata dump_nvata.sys Fri Aug 12 22:31:10 2005 (42FD151E)
b6f28000 b6f29e00   splitter splitter.sys Fri Mar 25 00:30:31 2005 (42435BA7)
b7944000 b794e000   Dxapi    Dxapi.sys    Tue Mar 25 07:06:01 2003 (3E7FFFD9)
b7984000 b798d000   dump_WMILIB dump_WMILIB.SYS Tue Mar 25 07:13:00 2003 (3E80017C)
b7d0a000 b7d11000   parvdm   parvdm.sys   Tue Mar 25 07:03:49 2003 (3E7FFF55)
b7d92000 b7d9d000   TDTCP    TDTCP.SYS    Fri Mar 25 00:27:15 2005 (42435AE3)
b9120000 b9131000   Fips     Fips.SYS     Fri Mar 25 00:40:33 2005 (42435E01)
b9131000 b91b1000   mrxsmb   mrxsmb.sys   Mon May 08 18:18:45 2006 (445F7D75)
b91b1000 b91ea000   rdbss    rdbss.sys    Mon May 08 18:18:53 2006 (445F7D7D)
b91ea000 b9214000   afd      afd.sys      Fri Mar 25 00:40:43 2005 (42435E0B)
b9214000 b9245000   netbt    netbt.sys    Fri Mar 25 00:40:31 2005 (42435DFF)
b9245000 b926c000   ipnat    ipnat.sys    Fri Mar 25 00:34:00 2005 (42435C78)
b926c000 b92cd000   tcpip    tcpip.sys    Wed May 24 02:02:22 2006 (4473B09E)
b92cd000 b92e6000   ipsec    ipsec.sys    Fri Mar 25 00:40:49 2005 (42435E11)
b92e6000 b9345f80   Senfilt  Senfilt.sys  Thu Aug 11 18:43:27 2005 (42FB8E3F)
b9346000 b9365380   AEAudio  AEAudio.sys  Sat Mar 05 02:53:09 2005 (42291F15)
b9366000 b938c000   ADIHdAud ADIHdAud.sys Wed Oct 05 22:21:08 2005 (434443C4)
b938c000 b93a0000   usbhub   usbhub.sys   Fri Mar 25 00:30:46 2005 (42435BB6)
b93c0000 b9400000   update   update.sys   Fri Mar 25 00:40:27 2005 (42435DFB)
b9410000 b9418480   oreans32 oreans32.sys Fri Dec 16 12:28:09 2005 (43A2B2D9)
b9420000 b942d000   Npfs     Npfs.SYS     Fri Mar 25 00:30:04 2005 (42435B8C)
b9430000 b943b000   Msfs     Msfs.SYS     Fri Mar 25 00:30:04 2005 (42435B8C)
b9440000 b944d000   wanarp   wanarp.sys   Fri Mar 25 00:34:07 2005 (42435C7F)
b9450000 b945d000   netbios  netbios.sys  Fri Mar 25 00:33:21 2005 (42435C51)
b9490000 b949a000   flpydisk flpydisk.sys Tue Mar 25 07:04:32 2003 (3E7FFF80)
b96b1000 b96b9500   NVENETFD NVENETFD.sys Sat Jul 30 01:11:01 2005 (42EAC595)
b96c1000 b96cf000   NDProxy  NDProxy.SYS  Fri Mar 25 00:34:13 2005 (42435C85)
b96d1000 b96da000   mssmbios mssmbios.sys Fri Mar 25 00:34:14 2005 (42435C86)
b96e1000 b96f0000   termdd   termdd.sys   Fri Mar 25 00:27:15 2005 (42435AE3)
b9939000 b9970000   rdpdr    rdpdr.sys    Fri Mar 25 00:30:20 2005 (42435B9C)
b9970000 b9984000   psched   psched.sys   Fri Mar 25 00:33:35 2005 (42435C5F)
b9984000 b9997000   raspptp  raspptp.sys  Fri Mar 25 00:40:43 2005 (42435E0B)
b9997000 b99b1000   ndiswan  ndiswan.sys  Fri Mar 25 00:40:46 2005 (42435E0E)
b99b1000 b99c6000   rasl2tp  rasl2tp.sys  Fri Mar 25 00:40:29 2005 (42435DFD)
b99c6000 b99ee000   ks       ks.sys       Fri Mar 25 00:41:03 2005 (42435E1F)
b99ee000 b9a03000   drmk     drmk.sys     Fri Mar 25 00:30:34 2005 (42435BAA)
b9a03000 b9a2c000   portcls  portcls.sys  Fri Mar 25 00:40:46 2005 (42435E0E)
b9a2c000 b9a3f000   i8042prt i8042prt.sys Fri Mar 25 00:41:05 2005 (42435E21)
b9a3f000 b9a57000   parport  parport.sys  Fri Mar 25 00:28:25 2005 (42435B29)
b9a57000 b9a6c000   serial   serial.sys   Fri Mar 25 00:28:29 2005 (42435B2D)
b9a6c000 b9aa2280   NVSNPU   NVSNPU.SYS   Sat Jul 30 01:10:31 2005 (42EAC577)
b9aa3000 b9aec900   NVNRM    NVNRM.SYS    Sat Jul 30 01:10:44 2005 (42EAC584)
b9aed000 b9b15000   HDAudBus HDAudBus.sys Thu May 26 16:46:29 2005 (4295EF55)
b9b15000 b9b3f000   USBPORT  USBPORT.SYS  Fri Mar 25 00:30:43 2005 (42435BB3)
b9b3f000 b9b5a000   VIDEOPRT VIDEOPRT.SYS Fri Mar 25 00:29:53 2005 (42435B81)
b9b64000 b9b6a300   HIDPARSE HIDPARSE.SYS Fri Mar 25 00:30:36 2005 (42435BAC)
b9b6c000 b9b73000   Beep     Beep.SYS     Tue Mar 25 07:03:04 2003 (3E7FFF28)
b9b74000 b9b7b000   Null     Null.SYS     Tue Mar 25 07:03:05 2003 (3E7FFF29)
b9b7c000 b9b84000   Fs_Rec   Fs_Rec.SYS   Tue Mar 25 07:08:36 2003 (3E800074)
ba0ab000 ba0b4000   raspti   raspti.sys   Fri Mar 25 00:34:16 2005 (42435C88)
ba0bb000 ba0c6000   ptilink  ptilink.sys  Fri Mar 25 00:28:25 2005 (42435B29)
ba0cb000 ba0d9000   msgpc    msgpc.sys    Fri Mar 25 00:33:31 2005 (42435C5B)
ba0db000 ba0e6000   TDI      TDI.SYS      Fri Mar 25 00:35:34 2005 (42435CD6)
ba0eb000 ba0fa000   raspppoe raspppoe.sys Fri Mar 25 00:34:16 2005 (42435C88)
ba0fb000 ba104000   ndistapi ndistapi.sys Fri Mar 25 00:34:11 2005 (42435C83)
ba10b000 ba115000   kbdclass kbdclass.sys Tue Mar 25 07:03:10 2003 (3E7FFF2E)
ba11b000 ba125000   mouclass mouclass.sys Tue Mar 25 07:03:09 2003 (3E7FFF2D)
ba12b000 ba135000   serenum  serenum.sys  Fri Mar 25 00:28:27 2005 (42435B2B)
ba179000 ba17a420   ASACPI   ASACPI.sys   Fri Aug 13 03:52:52 2004 (411C2D04)
bafc0000 bafc2780   gameenum gameenum.sys Tue Mar 25 07:10:22 2003 (3E8000DE)
bafc4000 bafc7280   nvnetbus nvnetbus.sys Sat Jul 30 01:11:03 2005 (42EAC597)
bf800000 bf9d0000   win32k   win32k.sys   Thu Oct 06 01:37:08 2005 (434471B4)
bf9d0000 bf9e6000   dxg      dxg.sys      Fri Mar 25 00:27:25 2005 (42435AED)
bff40000 bff48000   framebuf framebuf.dll Tue Mar 25 09:46:25 2003 (3E802571)
bff60000 bff7e000   RDPDD    RDPDD.dll    Fri Mar 25 02:30:48 2005 (424377D8)
f720c000 f722b000   Mup      Mup.sys      Fri Mar 25 00:40:49 2005 (42435E11)
f722b000 f7252000   KSecDD   KSecDD.sys   Fri Mar 25 00:28:53 2005 (42435B45)
f7252000 f7277000   fltmgr   fltmgr.sys   Mon Aug 21 10:59:45 2006 (44E98411)
f7277000 f728a000   CLASSPNP CLASSPNP.SYS Fri Mar 25 00:40:23 2005 (42435DF7)
f728a000 f72a2080   nvata    nvata.sys    Fri Aug 12 22:31:10 2005 (42FD151E)
f72a3000 f72bf000   atapi    atapi.sys    Fri Mar 25 00:28:49 2005 (42435B41)
f72bf000 f72e9000   volsnap  volsnap.sys  Fri Mar 25 00:29:10 2005 (42435B56)
f72e9000 f7315000   dmio     dmio.sys     Fri Mar 25 00:30:02 2005 (42435B8A)
f7315000 f733c000   ftdisk   ftdisk.sys   Fri Mar 25 00:29:00 2005 (42435B4C)
f733c000 f7352000   pci      pci.sys      Fri Mar 25 00:34:14 2005 (42435C86)
f7352000 f7386000   ACPI     ACPI.sys     Fri Mar 25 00:34:09 2005 (42435C81)
f7487000 f7490000   WMILIB   WMILIB.SYS   Tue Mar 25 07:13:00 2003 (3E80017C)
f7497000 f74a6000   isapnp   isapnp.sys   Tue Mar 25 07:16:35 2003 (3E800253)
f74a7000 f74b5f00   ohci1394 ohci1394.sys Fri Mar 25 00:31:18 2005 (42435BD6)
f74b7000 f74c4200   1394BUS  1394BUS.SYS  Fri Mar 25 00:31:17 2005 (42435BD5)
f74c7000 f74d4000   PCIIDEX  PCIIDEX.SYS  Fri Mar 25 00:28:48 2005 (42435B40)
f74d7000 f74e7000   MountMgr MountMgr.sys Fri Mar 25 00:27:23 2005 (42435AEB)
f74e7000 f74f2000   PartMgr  PartMgr.sys  Fri Mar 25 00:40:34 2005 (42435E02)
f74f7000 f7507000   disk     disk.sys     Fri Mar 25 00:28:58 2005 (42435B4A)
f7507000 f7513000   Dfs      Dfs.sys      Fri Mar 25 00:30:28 2005 (42435BA4)
f7517000 f7521000   crcdisk  crcdisk.sys  Fri Mar 25 00:29:40 2005 (42435B74)
f75e7000 f75f5000   processr processr.sys Fri Mar 25 00:28:39 2005 (42435B37)
f75f7000 f7603000   vgapnp   vgapnp.sys   Fri Mar 25 00:29:55 2005 (42435B83)
f7607000 f7610000   watchdog watchdog.sys Fri Mar 25 00:30:19 2005 (42435B9B)
f7647000 f7652000   fdc      fdc.sys      Fri Mar 25 00:28:43 2005 (42435B3B)
f76d1000 f7707000   NDIS     NDIS.sys     Fri Mar 25 00:40:26 2005 (42435DFA)
f7707000 f770f000   kdcom    kdcom.dll    Tue Mar 25 07:08:00 2003 (3E800050)
f770f000 f7717000   BOOTVID  BOOTVID.dll  Tue Mar 25 07:07:58 2003 (3E80004E)
f7717000 f771e000   pciide   pciide.sys   Tue Mar 25 07:04:46 2003 (3E7FFF8E)
f771f000 f7726000   dmload   dmload.sys   Tue Mar 25 07:08:08 2003 (3E800058)
f7757000 f775e000   dxgthk   dxgthk.sys   Tue Mar 25 07:05:52 2003 (3E7FFFD0)
f7777000 f777f000   RDPCDD   RDPCDD.sys   Tue Mar 25 07:03:05 2003 (3E7FFF29)
f777f000 f7787000   mnmdd    mnmdd.SYS    Tue Mar 25 07:07:53 2003 (3E800049)
f779f000 f77a7000   audstub  audstub.sys  Tue Mar 25 07:09:12 2003 (3E800098)
f77af000 f77b5a00   usbehci  usbehci.sys  Fri Mar 25 00:30:43 2005 (42435BB3)
f77df000 f77e3400   usbohci  usbohci.sys  Fri Mar 25 00:30:45 2005 (42435BB5)
f77ff000 f7807000   rasacd   rasacd.sys   Tue Mar 25 07:11:50 2003 (3E800136)
f780f000 f7817000   msmpu401 msmpu401.sys Tue Mar 25 07:09:16 2003 (3E80009C)
f79b9000 f79ba280   swenum   swenum.sys   Fri Mar 25 00:27:42 2005 (42435AFE)
f79bb000 f79bc580   USBD     USBD.SYS     Tue Mar 25 07:10:39 2003 (3E8000EF)
f7b4a000 f7bdf000   Ntfs     Ntfs.sys     Fri Mar 25 00:40:29 2005 (42435DFD)

Unloaded modules:
b9460000 b946e000   imapi.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
b91d6000 b91ea000   redbook.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
b9470000 b947c000   vga.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
b9480000 b9489000   kbdhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
b92d1000 b92e6000   cdrom.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
b9b84000 b9b8c000   Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
0
 
LVL 3

Author Comment

by:talkster5
ID: 18050229
Result of "!thread":

GetPointerFromAddress: unable to read from 8089c298
THREAD 89e6a4b0  Cid 0004.0084  Teb: 00000000 Win32Thread: 00000000 RUNNING on processor 0
Not impersonating
GetUlongFromAddress: unable to read from 808ab934
Owning Process            89f9b818       Image:         System
ffdf0000: Unable to get shared data
Wait Start TickCount      11979        
Context Switch Count      3251            
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.0000
KernelTime                00:00:00.0000
Start Address NDIS!ndisWorkerThread (0xf76da005)
Stack Init f7943000 Current f7942d04 Base f7943000 Limit f7940000 Call 0
Priority 9 BasePriority 8 PriorityDecrement 0
ChildEBP RetAddr  Args to Child              
f79429e8 8095cab5 e2419870 e1003cc4 00000010 nt!memmove+0x154
f79429fc 8095f3ce 00000010 e2419870 e1003cc4 nt!RtlCopySid+0x29 (FPO: [Non-Fpo])
f7942aa4 8096ab21 00000000 0000000c f7942afc nt!RtlpNewSecurityObject+0x15a (FPO: [Non-Fpo])
f7942ad0 80937675 00000000 00000000 f7942afc nt!SeAssignSecurity+0x4f (FPO: [Non-Fpo])
f7942b00 8093ac6f f7942c1c 00000000 89e21870 nt!ObAssignSecurity+0x35 (FPO: [Non-Fpo])
f7942bf0 809492e3 89e21870 f7942c1c 00000000 nt!ObInsertObject+0x503 (FPO: [Non-Fpo])
f7942d4c 80949ea9 f7942db4 001f03ff 00000000 nt!PspCreateThread+0x5c9 (FPO: [Non-Fpo])
f7942d80 f76da058 f7942db4 001f03ff 00000000 nt!PsCreateSystemThread+0x33 (FPO: [Non-Fpo])
f7942dac 80948bb2 00001334 00000000 00000000 NDIS!ndisWorkerThread+0x4a (FPO: [Non-Fpo])
f7942ddc 8088d4d2 f76da005 00000000 00000000 nt!PspSystemThreadStartup+0x2e (FPO: [Non-Fpo])
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
0
 
LVL 20

Expert Comment

by:cpc2004
ID: 18050418
Hi,

Your debug report is incomplete. I want the output of !analyze -v. One minidump is insufficient to determine the root cause. If you have another minidump,  attach the dedbug report here.  

cpc2004
0
 
LVL 3

Author Comment

by:talkster5
ID: 18050483
Hi,
First Dump:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 80881c14, The address that the exception occurred at
Arg3: f7942918, Exception Record Address
Arg4: f7942614, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nt!memmove+154
80881c14 301c88          xor     byte ptr [eax+ecx*4],bl

EXCEPTION_RECORD:  f7942918 -- (.exr fffffffff7942918)
ExceptionAddress: 80881c14 (nt!memmove+0x00000154)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 00000104
Attempt to write to address 00000104

CONTEXT:  f7942614 -- (.cxr fffffffff7942614)
eax=000000f4 ebx=f7942a1c ecx=00000004 edx=00000000 esi=e1003cd4 edi=e2419880
eip=80881c14 esp=f79429e0 ebp=f79429e8 iopl=0         nv up ei ng nz ac po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010293
nt!memmove+0x154:
80881c14 301c88          xor     byte ptr [eax+ecx*4],bl    ds:0023:00000104=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  3

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

WRITE_ADDRESS:  00000104

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 8095cab5 to 80881c14

STACK_TEXT:  
f79429e8 8095cab5 e2419870 e1003cc4 00000010 nt!memmove+0x154
f79429fc 8095f3ce 00000010 e2419870 e1003cc4 nt!RtlCopySid+0x29
f7942aa4 8096ab21 00000000 0000000c f7942afc nt!RtlpNewSecurityObject+0x15a
f7942ad0 80937675 00000000 00000000 f7942afc nt!SeAssignSecurity+0x4f
f7942b00 8093ac6f f7942c1c 00000000 89e21870 nt!ObAssignSecurity+0x35
f7942bf0 809492e3 89e21870 f7942c1c 00000000 nt!ObInsertObject+0x503
f7942d4c 80949ea9 f7942db4 001f03ff 00000000 nt!PspCreateThread+0x5c9
f7942d80 f76da058 f7942db4 001f03ff 00000000 nt!PsCreateSystemThread+0x33
f7942dac 80948bb2 00001334 00000000 00000000 NDIS!ndisWorkerThread+0x4a
f7942ddc 8088d4d2 f76da005 00000000 00000000 nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    80881c0c - nt!memmove+14c
      [ 1c:0c ]
    80881d18 - nt!memmove+258 (+0x10c)
      [ 01:f4 ]
2 errors : !nt (80881c0c-80881d18)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

STACK_COMMAND:  .cxr 0xfffffffff7942614 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------





Second Dump:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 08108740, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: b9bbf197, address which referenced memory

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


WRITE_ADDRESS:  08108740

CURRENT_IRQL:  2

FAULTING_IP:
NVSNPU+12197
b9bbf197 832100          and     dword ptr [ecx],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Idle

LAST_CONTROL_TRANSFER:  from b9bb0c38 to b9bbf197

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
f78ae6dc b9bb0c38 898279f0 89828138 00000064 NVSNPU+0x12197
f78ae708 b9badb22 00000001 f78ae72c f78ae728 NVSNPU+0x3c38
f78ae720 b9bb694c 00000000 898280ec 00000010 NVSNPU+0xb22
f78ae738 b9bb6bc3 89820010 00000000 f78ae760 NVSNPU+0x994c
f78ae880 b9bb71dc 00000000 89828024 89820010 NVSNPU+0x9bc3
f78ae8dc b974ebc9 89827720 89827870 f78ae8fc NVSNPU+0xa1dc
f78ae91c b974ec56 89ff0d48 00000000 00000002 NVENETFD+0xbc9
f78ae93c f76ee804 89ff09a0 f78ae968 00000001 NVENETFD+0xc56
f78ae954 80a5824f 89ff0030 00000000 ff90c000 NDIS!ndisMProcessSGList+0x90
f78ae980 f76ee6fe ff90c000 89ff0030 87f6ea48 hal!HalAllocateCrashDumpRegisters+0x5
f78ae9d8 f76d249d 82047590 00000000 89969700 NDIS!ndisMAllocSGList+0xd9
f78ae9f4 b9aba6a8 89969700 820475c8 82047590 NDIS!ndisMSendX+0x1a0
f78aea24 f76d56c9 8996e6e8 820475c8 00000082 psched!MpSend+0x35a
f78aea4c b8f08f37 89813790 820475c8 88300518 NDIS!ndisMSendX+0x1d6
f78aea74 b8f0823a 89813858 820475c8 89d2b4e0 tcpip!ARPSendData+0x198
f78aea9c b8f08622 89d2b402 f78aeb02 00000001 tcpip!ARPTransmit+0x95
f78aebd8 b8f09c01 b8f41bb8 83cb3ce8 83cb3c80 tcpip!_IPTransmit+0x84f
f78aec48 b8f09050 1b7265c2 00000002 f7727a40 tcpip!TCPSend+0x5fa
f78aec6c b8f03b22 00000002 00000002 00000000 tcpip!ProcessPerCpuTCBDelayQ+0x95
f78aece8 b8f06fba b8f48978 00000000 f78aed50 tcpip!TCBTimeout+0xbeb
f78aecf8 80831cb2 b8f48988 b8f48978 f6c9388e tcpip!TCBTimeoutdpc+0xf
f78aed50 8088d28f 00000000 0000000e 00000000 nt!KiRetireDpcList+0xca
f78aed54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x37


STACK_COMMAND:  kb

FOLLOWUP_IP:
NVSNPU+12197
b9bbf197 832100          and     dword ptr [ecx],0

SYMBOL_STACK_INDEX:  0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NVSNPU

IMAGE_NAME:  NVSNPU.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  42eac577

SYMBOL_NAME:  NVSNPU+12197

FAILURE_BUCKET_ID:  0xD1_W_NVSNPU+12197

BUCKET_ID:  0xD1_W_NVSNPU+12197

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

Thanks.
0
 
LVL 3

Author Comment

by:talkster5
ID: 18050496
Ive got more as well. I have just realised though that the first dump I posed was not to do with the same error and was a different crash. I will find another one for the BSOD error I was getting and post it in a minute.
0
 
LVL 3

Author Comment

by:talkster5
ID: 18050501
Heres the correct one:


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0645b040, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: b9741197, address which referenced memory

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


WRITE_ADDRESS:  0645b040

CURRENT_IRQL:  2

FAULTING_IP:
NVSNPU+12197
b9741197 832100          and     dword ptr [ecx],0

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Idle

LAST_CONTROL_TRANSFER:  from b97326a2 to b9741197

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
f78ae860 b97326a2 898519f0 89885de0 000002d0 NVSNPU+0x12197
f78ae888 b972fbfc 000000a8 b9758044 89850720 NVSNPU+0x36a2
f78ae8dc b92b0bc9 89850720 89850870 f78ae8fc NVSNPU+0xbfc
f78ae91c b92b0c56 89ff03b0 00000000 00000002 NVENETFD+0xbc9
f78ae93c f76ee804 89ff0008 f78ae968 00000001 NVENETFD+0xc56
f78ae954 80a5824f 8965f9d0 00000000 fe03a000 NDIS!ndisMProcessSGList+0x90
f78ae980 f76ee6fe fe03a000 8965f9d0 890d7260 hal!HalAllocateCrashDumpRegisters+0x5
f78ae9d8 f76d249d 833b43c0 00000000 89991700 NDIS!ndisMAllocSGList+0xd9
f78ae9f4 b963c6a8 89991700 833b43f8 833b43c0 NDIS!ndisMSendX+0x1a0
f78aea24 f76d56c9 899956e8 833b43f8 00000082 psched!MpSend+0x35a
f78aea4c b8f24f37 89c0c978 833b43f8 83488570 NDIS!ndisMSendX+0x1d6
f78aea74 b8f2423a 8997a7a0 833b43f8 89797628 tcpip!ARPSendData+0x198
f78aea9c b8f24622 89797602 f78aeb02 00000001 tcpip!ARPTransmit+0x95
f78aebd8 b8f25c01 b8f5dbb8 856ce8c8 856ce860 tcpip!_IPTransmit+0x84f
f78aec48 b8f25050 860142bc 00000002 f7727a40 tcpip!TCPSend+0x5fa
f78aec6c b8f1fb22 00000002 00000002 00000000 tcpip!ProcessPerCpuTCBDelayQ+0x95
f78aece8 b8f22fba b8f64978 00000000 f78aed50 tcpip!TCBTimeout+0xbeb
f78aecf8 80831cb2 b8f64988 b8f64978 dc9dc568 tcpip!TCBTimeoutdpc+0xf
f78aed50 8088d28f 00000000 0000000e 00000000 nt!KiRetireDpcList+0xca
f78aed54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x37


STACK_COMMAND:  kb

FOLLOWUP_IP:
NVSNPU+12197
b9741197 832100          and     dword ptr [ecx],0

SYMBOL_STACK_INDEX:  0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NVSNPU

IMAGE_NAME:  NVSNPU.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  42eac577

SYMBOL_NAME:  NVSNPU+12197

FAILURE_BUCKET_ID:  0xD1_W_NVSNPU+12197

BUCKET_ID:  0xD1_W_NVSNPU+12197

Followup: MachineOwner
---------
0
 
LVL 20

Expert Comment

by:cpc2004
ID: 18050576
Hi,

The debug report shows that there have two memory corruption at nt!memmove and this is symptom of faulty ram. Run memtest to stress test the ram.

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    80881c0c - nt!memmove+14c
     [ 1c:0c ]
    80881d18 - nt!memmove+258 (+0x10c)
     [ 01:f4 ]
2 errors : !nt (80881c0c-80881d18)

MODULE_NAME: memory_corruption
IMAGE_NAME:  memory_corruption
FOLLOWUP_NAME:  memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MEMORY_CORRUPTOR:  LARGE
STACK_COMMAND:  .cxr 0xfffffffff7942614 ; kb
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
BUCKET_ID:  MEMORY_CORRUPTION_LARGE

cpc2004
0
Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

 
LVL 20

Expert Comment

by:cpc2004
ID: 18050592
Hi,

Hardware error occurs randomly and software usually have same symptoms (unless it is storage corruption). Your debug reports have 2 different crashes.  Attach more debug report here if you have. More diagnostic information is very useful to determine the root cause of the problem.

cpc2004
0
 
LVL 3

Author Comment

by:talkster5
ID: 18052341
Hi,
It crashed again during the night so here is another one from that:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 07b27040, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: b9a95197, address which referenced memory

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


WRITE_ADDRESS:  07b27040

CURRENT_IRQL:  2

FAULTING_IP:
NVSNPU+12197
b9a95197 832100          and     dword ptr [ecx],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Idle

LAST_CONTROL_TRANSFER:  from b9a866a2 to b9a95197

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
f78ae6ec b9a866a2 8981c9f0 8986d8c0 00000280 NVSNPU+0x12197
f78ae714 b9a83bfc 00000098 b9aac044 8981b720 NVSNPU+0x36a2
f78ae768 b9652bc9 8981b720 8981b870 f78ae788 NVSNPU+0xbfc
f78ae7a8 b9652c56 89ff03b0 00000000 00000002 NVENETFD+0xbc9
f78ae7c8 f76ee804 89ff0008 f78ae7f4 00000001 NVENETFD+0xc56
f78ae7e0 80a5824f 8962b9d0 00000000 85478000 NDIS!ndisMProcessSGList+0x90
f78ae80c f76ee6fe 85478000 8962b9d0 85a0c7b8 hal!HalAllocateCrashDumpRegisters+0x5
f78ae864 f76d249d 866b0be8 00000000 89970700 NDIS!ndisMAllocSGList+0xd9
f78ae880 b99906a8 89970700 866b0c20 866b0be8 NDIS!ndisMSendX+0x1a0
f78ae8b0 f76d56c9 899756e8 866b0c20 00000002 psched!MpSend+0x35a
f78ae8d8 b92b0f37 8995b7a0 866b0c20 00000000 NDIS!ndisMSendX+0x1d6
f78ae900 b92abdf8 8995a7a0 866b0c20 89e57908 tcpip!ARPSendData+0x198
f78ae928 b92ad0d5 8995a7a0 f78ae902 00000001 tcpip!ARPTransmit+0x11a
f78ae958 b92adcfc 893594a0 015570d9 866b0c20 tcpip!SendIPPacket+0x193
f78aeaa4 b92b1c01 b92e9bb8 85dba348 85dba2e0 tcpip!_IPTransmit+0x2914
f78aeb14 b92b1050 2f8e346c 00000002 00000040 tcpip!TCPSend+0x5fa
f78aeb38 b92b1898 00000002 00000002 f78aeb64 tcpip!ProcessPerCpuTCBDelayQ+0x95
f78aeb6c b92afcf3 00000002 b92afc01 b92afc94 tcpip!ProcessTCBDelayQ+0xc2
f78aeb78 b92afc94 00000000 89fe1358 b92afca0 tcpip!TCPRcvComplete+0x20
f78aeb84 b92afca0 f76f9343 8995a7a0 b99956a0 tcpip!IPRcvComplete+0x21
f78aeb88 f76f9343 8995a7a0 b99956a0 899756e8 tcpip!ARPRcvComplete+0x5
f78aebd8 b998f609 89de5470 8935e818 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5b1
f78aebec b998f7a0 89de5470 8935e818 00000001 psched!PsFlushReceiveQueue+0x15
f78aec10 b998fbaf 899756f0 00000000 89de5470 psched!PsEnqueueReceivePacket+0xda
f78aec28 f76f9343 899756e8 89ff0518 89ff0008 psched!ClReceiveComplete+0x13
f78aec78 b9655482 8962bad0 89ff0518 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5b1
f78aecb8 b9ac471b 00000001 89985630 b9ad74e0 NVENETFD+0x3482
f78aecd8 b9ac6d60 00000001 b9ac6d20 f7727a40 NVNRM+0xa71b
f78aecf8 80831cb2 899855b4 89985008 00000000 NVNRM+0xcd60
f78aed50 8088d28f 00000000 0000000e 00000000 nt!KiRetireDpcList+0xca
f78aed54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x37


STACK_COMMAND:  kb

FOLLOWUP_IP:
NVSNPU+12197
b9a95197 832100          and     dword ptr [ecx],0

SYMBOL_STACK_INDEX:  0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NVSNPU

IMAGE_NAME:  NVSNPU.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  42eac577

SYMBOL_NAME:  NVSNPU+12197

FAILURE_BUCKET_ID:  0xD1_W_NVSNPU+12197

BUCKET_ID:  0xD1_W_NVSNPU+12197

Followup: MachineOwner
---------
0
 
LVL 3

Author Comment

by:talkster5
ID: 18052446
I discovered that there were 2 firewalls running on the system which from google I understand to be a common problem which seems to cause these BSOD crash's for the nVidia ethernet drivers. I have now removed one of them and just running the system on the Windows Firewall so I will see if that makes any difference at all.
0
 
LVL 3

Author Comment

by:talkster5
ID: 18059782
Hi,
It just happened again so here is another dump file:


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 92388986, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: b9891197, address which referenced memory

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


WRITE_ADDRESS:  92388986

CURRENT_IRQL:  2

FAULTING_IP:
NVSNPU+12197
b9891197 832100          and     dword ptr [ecx],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  FileZilla.exe

LAST_CONTROL_TRANSFER:  from b9882829 to b9891197

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
f78b2ee8 b9882829 8988100a f78b2f08 00000268 NVSNPU+0x12197
f78b2f0c b987fc70 b98a7ff4 b98a8044 89521e60 NVSNPU+0x3829
f78b2f5c b98c071b 00000003 89995630 b98d34e0 NVSNPU+0xc70
f78b2f7c b98c2d60 00000001 b98c2d20 f7727a40 NVNRM+0xa71b
f78b2f9c 80831cb2 899955b4 89995008 00000000 NVNRM+0xcd60
f78b2ff4 8088cf9f b255af4c 00000000 00000000 nt!KiRetireDpcList+0xca
f78b2ff8 b255af4c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x3f
8088cf9f 00000000 0000000a bb837775 00000128 0xb255af4c


STACK_COMMAND:  kb

FOLLOWUP_IP:
NVSNPU+12197
b9891197 832100          and     dword ptr [ecx],0

SYMBOL_STACK_INDEX:  0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NVSNPU

IMAGE_NAME:  NVSNPU.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  42eac577

SYMBOL_NAME:  NVSNPU+12197

FAILURE_BUCKET_ID:  0xD1_W_NVSNPU+12197

BUCKET_ID:  0xD1_W_NVSNPU+12197

Followup: MachineOwner
0
 
LVL 20

Accepted Solution

by:
cpc2004 earned 500 total points
ID: 18060242
Three system crashes at NVSNPU (with exactly same instruction address) and one system crash with memory corruption.  Your windows is crashes with two culprits: faulty ram and software error at NVSNPU. Run memtest to stress test the ram and update NVSNIU.
0
 
LVL 3

Author Comment

by:talkster5
ID: 18061318
The crash because of the RAM has only ever happened once so I am not to concerned about that at the moment. A memory test has been run already anyway because of another problem a few weeks ago so that should not be the problem I wouldnt have thought. NVSNPU was also updated to the latest verison but the same thing still happened so I rolled it back again.
0
 
LVL 3

Author Comment

by:talkster5
ID: 18094320
Well the system lasted for 5 days without crashing this time compared to the usual less than 24 hours so I thought it may have been fixed. Here is the latest crash dump file:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 083a8040, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: b97d3197, address which referenced memory

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


WRITE_ADDRESS:  083a8040

CURRENT_IRQL:  2

FAULTING_IP:
NVSNPU+12197
b97d3197 832100          and     dword ptr [ecx],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Idle

LAST_CONTROL_TRANSFER:  from b97c46a2 to b97d3197

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
f78ae72c b97c46a2 898479f0 898aa070 000002d0 NVSNPU+0x12197
f78ae754 b97c1bfc 000000a8 b97ea044 89848720 NVSNPU+0x36a2
f78ae7a8 b92dcbc9 89848720 89848870 f78ae7c8 NVSNPU+0xbfc
f78ae7e8 b92dcc56 89ff0d48 00000000 00000002 NVENETFD+0xbc9
f78ae808 f76ee804 89ff09a0 f78ae834 00000001 NVENETFD+0xc56
f78ae820 80a5824f 89ff0030 00000000 88bb6000 NDIS!ndisMProcessSGList+0x90
f78ae84c f76ee6fe 88bb6000 89ff0030 88a6b340 hal!HalAllocateCrashDumpRegisters+0x5
f78ae8a4 f76d249d 87bf9020 00000000 8938c648 NDIS!ndisMAllocSGList+0xd9
f78ae8c0 b96ce6a8 8938c648 87bf9058 87bf9020 NDIS!ndisMSendX+0x1a0
f78ae8f0 f76d56c9 8998c6e8 87bf9058 00000082 psched!MpSend+0x35a
f78ae918 b8fa4f37 895136c8 87bf9058 87422f98 NDIS!ndisMSendX+0x1d6
f78ae940 b8fa423a 8950f7b8 87bf9058 89682700 tcpip!ARPSendData+0x198
f78ae968 b8fa4622 89682702 f78aea02 00000001 tcpip!ARPTransmit+0x95
f78aeaa4 b8fa5c01 b8fddbb8 88715c38 88715bd0 tcpip!_IPTransmit+0x84f
f78aeb14 b8fa5050 f4571b0f 00000002 00000040 tcpip!TCPSend+0x5fa
f78aeb38 b8fa5898 00000002 00000002 f78aeb64 tcpip!ProcessPerCpuTCBDelayQ+0x95
f78aeb6c b8fa3cf3 00000002 b8fa3c00 b8fa3c94 tcpip!ProcessTCBDelayQ+0xc2
f78aeb78 b8fa3c94 00000000 89fe1420 b8fa3ca0 tcpip!TCPRcvComplete+0x20
f78aeb84 b8fa3ca0 f76f9343 8950f7b8 b96d36a0 tcpip!IPRcvComplete+0x21
f78aeb88 f76f9343 8950f7b8 b96d36a0 8998c6e8 tcpip!ARPRcvComplete+0x5
f78aebd8 b96cd609 89eae130 89c0d4f8 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5b1
f78aebec b96cd7a0 89eae130 89c0d4f8 00000001 psched!PsFlushReceiveQueue+0x15
f78aec10 b96cdbaf 8998c6f0 00000000 89eae130 psched!PsEnqueueReceivePacket+0xda
f78aec28 f76f9343 8998c6e8 89ff0eb0 89ff09a0 psched!ClReceiveComplete+0x13
f78aec78 b92df482 89ff0130 89ff0eb0 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5b1
f78aecb8 b980271b 00000001 899ae630 b98154e0 NVENETFD+0x3482
f78aecd8 b9804d60 00000001 b9804d20 f7727a40 NVNRM+0xa71b
f78aecf8 80831cb2 899ae5b4 899ae008 00000000 NVNRM+0xcd60
f78aed50 8088d28f 00000000 0000000e 00000000 nt!KiRetireDpcList+0xca
f78aed54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x37


STACK_COMMAND:  kb

FOLLOWUP_IP:
NVSNPU+12197
b97d3197 832100          and     dword ptr [ecx],0

SYMBOL_STACK_INDEX:  0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NVSNPU

IMAGE_NAME:  NVSNPU.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  42eac577

SYMBOL_NAME:  NVSNPU+12197

FAILURE_BUCKET_ID:  0xD1_W_NVSNPU+12197

BUCKET_ID:  0xD1_W_NVSNPU+12197

Followup: MachineOwner
0
 
LVL 3

Author Comment

by:talkster5
ID: 18109238
I just went for reinstalling windows in the end so I am just waiting a few days to see how things go.
0
 
LVL 3

Author Comment

by:talkster5
ID: 18137283
Since the reinstall so far I have not had any problems that I am aware of. If I find it does happen again I will open a new question and see if I can find more information. Cheers for the help though.
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Join & Write a Comment

Organizations create, modify, and maintain huge amounts of data to help their businesses earn money and generally function.  Typically every network user within an organization has a bit of disk space to store in process items and personal files.   …
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
You have products, that come in variants and want to set different prices for them? Watch this micro tutorial that describes how to configure prices for Magento super attributes. Assigning simple products to configurable: We assigned simple products…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

8 Experts available now in Live!

Get 1:1 Help Now