Hello and welcome :) .
Driver verifier has caught a handful of drivers:Please update the drivers or remove if not in use.
Code:
lmvm FNETTBOH_305
start end module name
fffff880`065d1000 fffff880`065de000 FNETTBOH_305 T (no symbols)
Loaded symbol image file: FNETTBOH_305.SYS
Image path: \SystemRoot\System32\drivers\FNETTBOH_305.SYS
Image name: FNETTBOH_305.SYS
Timestamp: Fri May 13 08:09:28 2011 (4DCCBD08)
CheckSum: 0000CF94
ImageSize: 0000D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Code:
lmvm iusb3hub
start end module name
fffff880`06547000 fffff880`065a4000 iusb3hub T (no symbols)
Loaded symbol image file: iusb3hub.sys
Image path: \SystemRoot\system32\DRIVERS\iusb3hub.sys
Image name: iusb3hub.sys
Timestamp: Mon Feb 27 12:56:50 2012 (4F4B6172)
CheckSum: 0005A7DB
ImageSize: 0005D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Code:
lmvm MBfilt64
start end module name
fffff880`06d5b000 fffff880`06d69000 MBfilt64 T (no symbols)
Loaded symbol image file: MBfilt64.sys
Image path: \SystemRoot\system32\drivers\MBfilt64.sys
Image name: MBfilt64.sys
Timestamp: Fri Jul 31 06:40:32 2009 (4A7267B0)
CheckSum: 0000FF02
ImageSize: 0000E000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Code:
lmvm ISCTD64
start end module name
fffff880`0542b000 fffff880`0543c000 ISCTD64 T (no symbols)
Loaded symbol image file: ISCTD64.sys
Image path: \SystemRoot\system32\DRIVERS\ISCTD64.sys
Image name: ISCTD64.sys
Timestamp: Tue Nov 27 21:52:34 2012 (50B51A02)
CheckSum: 00016374
ImageSize: 00011000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Code:
lmvm MijXfilt
start end module name
fffff880`07b65000 fffff880`07b87000 MijXfilt T (no symbols)
Loaded symbol image file: MijXfilt.sys
Image path: \SystemRoot\system32\DRIVERS\MijXfilt.sys
Image name: MijXfilt.sys
Timestamp: Sat May 12 07:27:12 2012 (4FADE6A0)
CheckSum: 00022009
ImageSize: 00022000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Please remove Avast Anti-Virus as it was involved in several bugchecks.
I'm a bit worried about this stack;
Code:
2: kd> k
Child-SP RetAddr Call Site
fffff880`0c425218 fffff800`030dc129 nt!KeBugCheckEx
fffff880`0c425220 fffff800`030dada0 nt!KiBugCheckDispatch+0x69
fffff880`0c425360 fffff880`01a839a0 nt!KiPageFault+0x260
fffff880`0c4254f0 fffff880`01a81bf8 tcpip!memcmp+0x90
fffff880`0c4254f8 fffff880`0198c312 tcpip!IpGetAllInterfaceParameters+0x88
fffff880`0c425578 00000000`018ff040 NETIO!NsiGetParameterEx+0x386
fffff880`0c4256c8 fffffa80`0d52b840 0x18ff040
fffff880`0c4256d0 00000000`00000000 0xfffffa80`0d52b840
That looks suspicious to me, as I couldn't unassemble backwards the return address
I can't look further into it.
Code:
ub 00000000`018ff040
^ Unable to find valid previous instruction for 'ub 00000000`018ff040'
I suggest scanning for infections:
The most predominant driver in the dumps is ScpVBus.sys
Code:
lmvm ScpVBus
start end module name
fffff880`05ae5000 fffff880`05af3000 ScpVBus T (no symbols)
Loaded symbol image file: ScpVBus.sys
Image path: \SystemRoot\system32\DRIVERS\ScpVBus.sys
Image name: ScpVBus.sys
Timestamp: Mon May 06 00:31:26 2013 (5186CFAE)
CheckSum: 0000E3B0
ImageSize: 0000E000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
I wasn't able to find anything reliable online regarding the origin of the driver
but I can see it's location in your PC, can you shed some light?
Code:
c:\users\markus\downloads\scpserver\
Now as for the SLI issues,
What is the make an model of you PSU?
Fill out this form and post back the result:
Good practice, open up the case and re-seat all types of connection.
- SATA Cables (HDD/SSD/ODD).
- SATA-Power.
- Motherboard 24-pin.
- Motherboard 4/8-pin (CPU).
- Re-seat the RAM.
- Re-seat the GPU.
Make sure that every slot / cable head is free of dust or other obstruction.
Make sure that every connection is seating properly and firmly in-place.
- Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
Post back with the results :) .