Intermittent BSOD Bugcheck code 0x3b

[rathburnmd1]

Had to breakdown my setup around the other day (new carpet being installed) and after getting everything set back up I began to get bluescreens (was using windows 8 at the time). I reformatted the drive and installed Windows 7 but have still been getting some intermittent BSOD, for example only one BSOD yesterday during the day (computer was in use all day) and then a BSOD overnight while I slept. I ran a memtest with no errors. I opened up the case and made sure everything was seated correctly and blew out the dust. I went back to old graphics drivers in case the new ones had some issue. Still can't seem to find the cause. I don't know what else to do so I am hoping someone here can help me figure this out!

 

[YoYo155]

Hello and welcome .
The bugchecks are all the same 0x3B (as you mentioned) with an NTSTATUS code of 0xc0000005
or Access Violation which happens when a driver attempts to access an address space
that it doesn't have the privilegesto, in other words it doesn't belong to that program.

These bugchecks has been linked to a GPU driver passing on bad data, yours is no exception
the common denominator between the bugchecks is nvlddmkm.sys.

Download and save Info.bat to the desktop.

Open an elevated command prompt and then type the following command:

cd C:\Users\<Username>\Desktop

Then type:

Info.bat

The batch file will begin to run, the SystemInfo.txt file will be saved to your C:\ partition,
the MSINFO32 file will simply open, therefore click File and then Save.
Chose the save location as your Desktop, and then copy the two files into a zipped folder.

Upload the zipped folder in your next post.
View attachment 291377



Please follow this detailed quote and update the driver.

Install the 314.22 WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Keep us posted.

 

[rathburnmd1]

After running the info.bat and saving, it only outputs one file which I am attaching. What is the other file that you wanted me to include?

Thank you so much for the help, I really appreciate it. I have done as requested with the graphics driver, will update if I have another BSOD.

 

[YoYo155]

After running the info.bat and saving, it only outputs one file which I am attaching. What is the other file that you wanted me to include?

Thank you so much for the help, I really appreciate it. I have done as requested with the graphics driver, will update if I have another BSOD.

Hi thanks , but that is not the file I was looking for.
The file is now located at:

C:\systeminfo.txt

Please upload that file .

 

[rathburnmd1]

Ah, sorry!

 

[YoYo155]

Thanks.
Update which ever way things turn up .

 

[rathburnmd1]

Just got another one, attaching the tool report.

 

[YoYo155]

Hi thanks for the update .
Those (you actually had three new dumps) bugchecks are almost identical to the rest, time for some tests.

BTW what is the make and model of your PSU?

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

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.

If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Like the quote states, let us know .

 

[rathburnmd1]

I have a Corsair Pro Series AX 850 PSU. I ran a pass of memtest without issue the other night (it takes about 2 hrs for a pass with the 32g of RAM I have). I will set that to run tonight before I go to bed. I went ahead and turned on Driver verifier, will update with anymore dumps.

Thanks again for all your help!

 

[YoYo155]

Thanks .
32GB is going to take a while..
It's important to not chage your PC usage habits just because driver Verifier is enabled, it even more important
to use the PC as you would normally to give a correct representation of what usually causes the bugchecks .

 

[rathburnmd1]

Yeah, that is what I figured. I am doing my normal thing of playing game with a stream open on another window and lots of firefox tabs open. Is it vitally important to do 8 passes of memtest or if I run it for 8 or so hours overnight will that suffice?

 

[YoYo155]

It's really up to you, it's your PC at the end of the day.
We tend to recommend a minimum of seven passes to gain at least some sort of confirmation
about the state of the RAM / slots.
I can tell you this though, RAM issues are usually all over the plac which isn't the situation we are dealing with
at the moment but we need to establish a baseline.

 

[rathburnmd1]

Okay, I will run it overnight and we will see where we are.

 

[rathburnmd1]

Had a power outage that interrupted the test last night, will run tonight and update. No crashes thus far with verifier on.

 

[rathburnmd1]

4 passes with no errors on Memtest last night. Been running verifier since two nights ago (except while sleeping) with no crashes.

 

[YoYo155]

OK, thanks .
You can disable DV now.

Just so we're on the same page, are you getting the BSODs while running some specific
app / game / idle?
The bugchecks don't reflect that, but they are mostly during chrome.

Is the card overclocked?
If it is, please STOP.

Test for thermals and stability:

• Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the card using Furmark.

I can see you have three monitors, two of which are connected
via the card's DVI and a third via an external DisplayPort.

Start by running just one monitor, using the DVI connection, for a few days then add
the other DVI and over time the third externalDP, that of course if you don't get any BSODs
in between.

I took a second look at the bugchecks and found some unfamiliar entries in the loaded / unloaded
module lists.

I also found that Driver Reference Table - RTCore64.sys is present in all of the dumps!
RTCore64, is a known BSOD cause with Windows 7.
Please remove it.

Please scan for possible infection and file corruption.

• Download TDSS-Killer and scan for rootkits.
• Download Kaspersky Rescue CD and scan for other types of infections. (a how-to tutorial)
• Follow this tutorial on how to use the SFC/ SCANNOW tool in Windows.

(*Kaspersky Rescue CD from a USB thumbdrive)

 

[rathburnmd1]

At first I thought it was related to Path of Exile since I have been playing a ton of that recently but I have had it BSOD a couple of times when I didn't have the game open (it BSOD'd one night while I was asleep with only chrome and mumble open).

Attaching the requested screenshots.

I got the EVGA video card program (which is the RTCore64 thing) because I thought maybe it was a heat problem with the card and that let me have better fan control and keep an eye on the heat. Will uninstall.

Thanks again for all the help!

 

[YoYo155]

Thanks for the added info .
How long did you run Furmark for, did you follow the steps demonstrated in the linked tutorial?
The temperature is normal for this type of GPU, that of-course is dependent upon the amount of time
the GPU was under load.

Start by uninstalling the GPU uitility (EVGA Precision), if that doesn't help try what is described
in post #16 regarding the monitors / ports.

Keep us informed .