BSOD caused by ntoskrnl.exe (nt+0x75BD0) (nt+0x75C00) and usbport.sys

[Lee Smith]

Hi there,

I finished building this custom computer about 2 weeks ago now, and almost ever since that day I've been having issues with bluescreens and lock-ups.

Firstly I've had quite a few BSOD during the last 2 weeks, I've enclosed 4 minidumps below which are from the last week and a bit, a lot of them seem to blame the ntoskrnl.exe for the problem however today I had a new one to do with a usbport.sys error which I also fail to understand the reason for.

This is the fourth custom build I've now done and I know how to properly install Windows and the updates and never to use the installation CD that comes with motherboards but to download the latest drivers and I do all of that but this is the first time I really need help figuring out a problem, I just can't figure out what exactly is causing my current issues, and I'd love to be able to just kick back and actually enjoy my new build at some point without worrying about whats going to happen next.

Also almost ever since day one I've had audio issues, after about 1-2 hours of watching a video or listening to music it slowly starts to crackle more and more until the point it becomes unlistenable, I've also encountered computer lock-ups at the point when it becomes unlistenable and then a hard reboot later the audio is absolutely fine again for another couples hours and then the same thing. I know it's not my headset causing the problem as I've tried it on another computer and it's perfectly fine, Also trying a second headset on here encountered the same issues.

If someone could take a quick look and maybe help me figure out what the problem(s) could be here I'd be very grateful to them.

 

[Arc]

Hello Lee ... mostly there are two reasons of the BSODs ... USB and Display.

About USB ... I am curious about one thing .....

c:\program files (x86)\renesas electronics\usb 3.0 host controller driver\application\rusb3mon.exe

Renesas Drivers. They does not exist in the system, but the program is present there? Can you clarify the situation?

Also, try to search for any possible updates of Intel(R) USB 3.0 eXtensible Host Controller, in https://downloadcenter.intel.com/default.aspx .

Is Silicone Labs USBXpress Development Kit any must for you? if so, update the driver from Technical Support - Mixed-Signal ICs | Silicon Labs , otherwise uninstall it.

Apply the latest version of nVidia display driver.
You may download it directly, from our forum link http://www.sevenforums.com/graphic-cards/602-latest-nvidia-forceware-video-drivers-windows-7-a.html; or you may opt for the Option 2 of Drivers- Download NVIDIA Drivers for “Automatically find drivers for my NVIDIA products” (it requires java installed).

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Let us know the results.

EDIT: Somehow I am feeling that you should disable Sleep.

• Start > Control Panel> Power Options
• Change power plan settings
• Put the computer to sleep > Never > Save changes.

And, Do you have any USB/PCI network adapter in use?

_______________________________________________________________________________
BSOD ANALYSIS:

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+77 )

Followup: MachineOwner
-----------------------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff80003376b75, fffff8800ac76e30, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+2ff )

Followup: MachineOwner
------------------------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff800031b8357, fffff8800b9a9a30, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+277 )

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

 

[Lee Smith]

Hi Arc and thank you for the quick reply,

So starting with the Renesas Drivers....my motherboard has Chipset + 2 Renesas uPD720210 USB 3.0 Hubs and was installed from the Gigabyte drivers page for my specific motherboard.

As for the "Silicone Labs USBXpress Development Kit" I'm honestly not even sure what that is or what it does so I'd definitely say that It's not a must for me and I will be uninstalling that right away.

I already have the latest Nvidia drivers (320.49) do you think stepping back to an older version maybe worth a shot?

I'm pretty sure the graphics card is in perfect condition, it came from a previous perfectly working system and has never given me any issues although I will run Furmark and post back the results of that.

I've followed your directions with the sleep state and that is now done and I have no USB or PCI network adapter in use.

 

[Lee Smith]

The "Silicone Labs USBXpress Development Kit" has now been removed, I've also just finished updating my "Intel(R) USB 3.0 eXtensible Host Controller" from version 2.0.0 to version 2.5.0.19 which is the latest listed on the website that you linked to.

Furmark test results after 30 minutes: Frames:40449 Time: 28.08 FPS:24 (min:22, max:24 avg:23)
GPU was at 99% Load, Memory was at 14% Load, Fan speed was 70% and the GPU got upto 81c but was at 80c for the majority and it passed fine without any crashes or artifacting.

I've also loaded optimized defaults in the bios although this has set my 2133mhz memory to 1333mhz

 

[Arc]

Well done. Very well done.
Now observe the situation. If it BSODs again (I hope so, as some network failures are still not detected) let us know as per the BSOD posting instructions. If it is display driver related again, we will try to roll it over to an older one.

 

[Lee Smith]

Thanks for the quick reply and help Arc, it was much appreciated.

Quick Update: I mentioned audio crackle issues which results in lock-ups in my original post and I believe after browsing through the Audio forums here it helped me figure out what was causing that, After downloading the DPC Latency Checker I found out that my Corsair Link software was actually accounting for over 3/4 of my latency and since removing that software I've not had a single audio crackle issue or lock-up now after 12 hours.

I'll also be posting this in the Audio forums here and of course the Corsair forums I just though I'd mention it here as it was in my original post, but none of this would have been fixed without the Sevenforums team.

 

[Arc]

You are welcome Lee

Let us know the situation after a few days.

 

[Lee Smith]

So over the weekend I got a couple more BSOD, although thankfully no more audio issues, I've attached both mini dumps into the below file, from what I can tell they are memory and Nvidia driver related again.

Any more thoughts/suggestions would be very welcome.

 

[x BlueRobot]

Hi Lee,

[COLOR=Red]BugCheck 1A[/COLOR], {[COLOR=Blue]41790[/COLOR], [COLOR=SeaGreen]fffffa800013ce60[/COLOR], [COLOR=DarkOrange]ffff[/COLOR], 0}

Probably caused by : win32k.sys ( win32k!FreeView+a2 )

Usual causes:  Device driver, memory, kernel

1: kd> [COLOR=SeaGreen]dt nt!_MMPFN fffffa800013ce60[/COLOR]
   +0x000 u1               : <unnamed-tag>
   +0x008 u2               : <unnamed-tag>
   +0x010 PteAddress       : 0xfffff6fb`40000040 _MMPTE
   +0x010 VolatilePteAddress : 0xfffff6fb`40000040 Void
   +0x010 Lock             : 0n1073741888
   +0x010 PteLong          : 0xfffff6fb`40000040
   +0x018 u3               : <unnamed-tag>
   +0x01c [COLOR=Red]UsedPageTableEntries : 0xffff[/COLOR] <-- Number of used PTE's seen in Parameter 3
   +0x01e VaType           : 0 ''
   +0x01f ViewCount        : 0 ''
   +0x020 OriginalPte      : _MMPTE
   +0x020 AweReferenceCount : 0n128
   +0x028 u4               : <unnamed-tag>

The other bugcheck indicated hardware as a probable cause, with the last failed instruction being the nVidia graphics driver. The reference count dropping below zero is usually caused by device drivers.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

You may need to enable the Special Pool option.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[Lee Smith]

Hi BlueRobot,

I ran Driver Verifier yesterday and found out after about 10 minutes my Nvidia driver would cause the display to freeze for about 15 seconds and then maybe 5 minutes later the display froze solid which needed a reboot to fix, so I've uninstalled my nvidia drivers and rolled back to the previous version which now seems to be better for now.

However with the Memtest86+ I had serious issues from the get-go, as soon as it booted up it started registering errors immediately and looking at the top where it shows your current memory config and speed etc it was all wrong, it was showing me as running a Triple Channel memory config which I don't, and it also showed my RAM as being a CAS 15 kit which again it just isn't so of course I had literally 5000 errors within minutes, I'm actually running my memory at 1600Mhz currently in dual channel with 1.5v (4 x 4gb DIMMs).

Windows and CPU-Z both show this correctly but I don't understand quite why Memtest86+ is showing it like that, I've ran it before on lots of different systems and never had that issue.

 

[x BlueRobot]

I'm not sure either, and it seems you either have bad RAM or a bad motherboard DIMM slot, I would begin testing each stick individually.