BSOD - Minidumps for analysis

Computer is seems to be randomly blue screening.  Please point me in the correct direction =)
Who is Participating?

Debug report
Mini051806-02.dmp BugCheck 100000D1, {deadfaee, 2, 1, f79c897a}
Probably caused by : usbuhci.sys ( usbuhci!UhciMapAsyncTransferToTds+1e0 ) <-- Faulty ram or firmware error of M/B

Mini051806-03.dmp BugCheck 1000008E, {c0000005, 8057bfac, ee2ecc08, 0}
Probably caused by : ntoskrnl.exe ( nt!IopXxxControlFile+1d1 )   <--- Faulty ram

Mini051806-04.dmp BugCheck 100000D1, {200004, 2, 0, ee93e51b}
Probably caused by : PRISMUSB.sys ( PRISMUSB+4999 ) <-- Crashes at tcpip and it is the sign of faulty ram

From the stack trace of the last minidump is crashed at tcpip.  Tcpip is a stable program. It crashes only if hardware errros.  All the minidumps are crashed with various symptoms and it is the sign of hardware error. Run memtest to stress test the ram.

8054fd8c ee960c49 00200000 00000000 806ee720 tcpip!FreeRBChain+0xd
8054fdb0 ee940ce8 09d8f800 00000002 00000000 tcpip!CloseTCB+0x37d
8054fdcc ee9424f7 82d8f800 00000002 00000000 tcpip!DerefTCB+0x60
8054fde8 ee942530 82d8f800 00000000 00000000 tcpip!GracefulClose+0xab
8054fe70 ee937ef5 82a261f0 6900a8c0 5c75a5c2 tcpip!TCPRcv+0x1401
8054fed0 ee937b19 00000020 82a261f0 ee93a076 tcpip!DeliverToUser+0x18e
8054ff4c ee937836 ee9773f0 82a261f0 829460b8 tcpip!DeliverToUserEx+0x95f
80550004 ee936922 82a261f0 829460cc 0000001a tcpip!IPRcvPacket+0x6cb
80550044 ee93b4ad 00000000 82952000 829460aa tcpip!ARPRcvIndicationNew+0x149
80550074 f7560c72 82a44e70 82952000 829460aa tcpip!ARPRcv+0x42
805500a8 f6fc65d7 82a6a008 82952000 00000000 NDIS!EthFilterDprIndicateReceive+0x17c
805500e8 f7560bd6 82ab4008 82952000 829460aa psched!ClReceiveIndication+0x21b
8055011c ee6a1999 82a2c008 82952000 829460aa NDIS!EthFilterDprIndicateReceive+0xe0
WARNING: Stack unwind information not available. Following frames may be wrong.
80550168 ee69edba 82952000 82946074 829460aa PRISMUSB+0x4999
805501ac 804dbbd4 8295f3c8 8295f3a0 70cc7732 PRISMUSB+0x1dba
805501d0 804dbb4d 00000000 0000000e 00000000 nt!KiRetireDpcList+0x46
805501d4 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x26
The 2nd dump pointed to ntoskrnl.exe, which is kind of generic.
The other 2 however both pointed to a USB driver as the problem. One had usbuhci.sys, and the other prismusb.sys as the most likely causes of the crash.
So at first look, I'm guessing it's been caused by either bad drivers for your USB controllers, or more likely a bad device or device driver for something USB you have connected. Prismusb.sys is associated with USB network cards, so if using one that would be the first place I'd look. First try updating drivers for it, and if still crashing, tye replacing the device itself.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.