Lots of BSODs - crash address ntoskrnl.exe+75bc0

Kaxpix · 27 Oct 2013

I seem to be getting seemingly random bluescreens, mainly during booting or after 20-30 minutes.
It will blue screen about 10 times, then work fine for days on end.

The blue screen bug check strings seem to vary:
9/16/2013 13:42 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff804`022dc0ea 00000000`00000008 fffff804`022dc0ea 00000000`00000005 umbus.sys umbus.sys+e81f00 ntoskrnl.exe+75b80 x64 8 15 7601 276,400 9/16/2013 13:45
9/16/2013 14:50 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff804`02506004 00000000`00000000 fffff800`0327ed40 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+75b80 ntoskrnl.exe+75b80 x64 8 15 7601 264,612 9/17/2013 8:26
10/17/2013 6:37 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 00000000`00640a70 00000000`00000000 00000000`77146183 00000000`00000008 iusb3xhc.sys iusb3xhc.sys+2b6aae0 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/17/2013 6:38
10/17/2013 8:15 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff904`c06840f4 00000000`00000000 fffff960`0018278d 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+75bc0 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/17/2013 8:16
10/17/2013 11:25 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff880`0120715c fffff880`06fef980 00000000`00000000 fltmgr.sys fltmgr.sys+715c ntoskrnl.exe+75bc0 x64 8 15 7601 319,560 10/17/2013 11:28
10/18/2013 7:30 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff804`02ec80ea 00000000`00000008 fffff804`02ec80ea 00000000`00000005 igdkmd64.sys igdkmd64.sys+3819f00 ntoskrnl.exe+75bc0 x64 8 15 7601 319,560 10/18/2013 7:34
10/20/2013 16:02 MEMORY_MANAGEMENT 0x0000001a 00000000`00041284 fffff980`0ddcc001 00000000`00000000 fffff780`c0000000 ntoskrnl.exe ntoskrnl.exe+75bc0 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/20/2013 16:14
10/21/2013 6:16 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02e42a15 fffff880`06df58f0 00000000`00000000 RTKVHD64.sys RTKVHD64.sys+fde8f0 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/21/2013 6:16
10/21/2013 6:19 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff683`fd7f5b00 00000000`00000000 fffff800`02e99f42 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+75bc0 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/21/2013 6:25
10/21/2013 8:15 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff804`02ed40ea 00000000`00000008 fffff804`02ed40ea 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+75bc0 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/21/2013 8:16
10/21/2013 12:34 NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`066a5d18 fffff880`066a5570 fffff880`016dffa0 Ntfs.sys Ntfs.sys+4688 ntoskrnl.exe+75bc0 x64 8 15 7601 319,560 10/21/2013 12:39
10/22/2013 6:11 MEMORY_MANAGEMENT 0x0000001a 00000000`00041790 fffffa80`04528bc0 00000000`0000ffff 00000000`00000000 RTKVHD64.sys RTKVHD64.sys+1ccb4d8 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/22/2013 6:20
10/22/2013 6:20 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a4`009ae3ec 00000000`00000000 fffff800`0315cac0 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+75bc0 ntoskrnl.exe+75bc0 x64 8 15 7601 319,384 10/22/2013 6:23
10/25/2013 6:21 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffffa80`cb4991a8 00000000`00000000 fffff800`02feb3e0 00000000`00000005 AgileVpn.sys AgileVpn.sys+258e760 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/25/2013 6:24
10/25/2013 6:25 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff680`023b0658 00000000`00000000 fffff800`02e985d7 00000000`00000002 usbhub.sys usbhub.sys+2da2ed0 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/25/2013 6:32
10/25/2013 6:36 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff704`01088e00 00000000`00000000 fffff800`02ecd7d6 00000000`00000005 luafv.sys luafv.sys+62d320 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/25/2013 6:41
10/25/2013 6:42 KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff800`031a89d9 00000000`00000000 00000040`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/25/2013 6:43
10/25/2013 6:43 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`031a5399 fffff880`07b42d90 00000000`00000000 iusb3xhc.sys iusb3xhc.sys+2856d90 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/25/2013 6:45
10/25/2013 6:46 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff904`c211dac8 00000000`00000000 fffff960`00256ead 00000000`00000005 iusb3xhc.sys iusb3xhc.sys+1902500 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/25/2013 6:54
10/25/2013 6:55 MEMORY_MANAGEMENT 0x0000001a 00000000`00041201 fffff680`0008d080 e7400006`9e077867 fffffa80`1016f300 serscan.sys serscan.sys+2b9e9e0 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/25/2013 6:57
10/25/2013 6:58 MEMORY_MANAGEMENT 0x0000001a 00000000`00041284 00000000`34347001 00000000`00009570 fffff700`01080000 RTKVHD64.sys RTKVHD64.sys+177b190 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/25/2013 7:01
10/25/2013 7:02 MEMORY_MANAGEMENT 0x0000001a 00000000`00041790 fffffa80`0a7bcbc0 00000000`0000ffff 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/25/2013 7:03
10/25/2013 7:10 MEMORY_MANAGEMENT 0x0000001a 00000000`00041284 00000000`261e5001 00000000`00012186 fffff700`01080000 fltmgr.sys fltmgr.sys+44f2 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/25/2013 7:15
10/25/2013 7:16 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8e0`0dc5e5f8 00000000`00000000 fffff800`031581b9 00000000`00000005 serscan.sys serscan.sys+2a6b5e0 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/25/2013 7:21
10/25/2013 7:23 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8e0`041d9d70 00000000`00000000 fffff800`031276a4 00000000`00000005 HDAudBus.sys HDAudBus.sys+fef72d70 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/25/2013 7:35
10/25/2013 7:35 MEMORY_MANAGEMENT 0x0000001a 00000000`00041790 fffffa80`0a55db40 00000000`0000ffff 00000000`00000000 HDAudBus.sys HDAudBus.sys+2a4d7b8 ntoskrnl.exe+75bc0 x64 8 15 7601 319,496 10/25/2013 7:36

I've tried running a memtest for about 4 cycles and it came back fine. I've also ran prime95 for 30 hours and furmark for 2 hours.

I've updated the intel graphics card driver to the latest version. The bios and other drivers are all the latest available from gigabyte.
I've also done a sfc /scannow which came back fine. I also ran chkdsk a few times to clear out any errors (caused by the improper shutdowns).

I'm not really sure whats causing the problem and really appreciate your feedback.

Arc · 27 Oct 2013

Hi Kaxpix.

Yes, you have experienced a real lot of BSODs. Please perform the following, which will help us to go for the further troubleshooting in case.

Make it sure that the Samsung 840 series SSD is running with the up-to date firmware. See here: Samsung SSD (Solid State Drive) 840 series | Samsung SSD Website

ESET is failing there ....

Code:

fffff880`0264a6f8  fffff880`04a8e600Unable to load image epfwwfpr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for epfwwfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for epfwwfpr.sys
 epfwwfpr+0x1f600

Description here: Driver Reference Table - epfwwfpr.sys

Uninstall ESET, at least as a test. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

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.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Then let us know how it is running. We need to take necessary actions depending on the situation then.

Kaxpix · 27 Oct 2013

Hi Arc,

Yes the samsung is running the latest firmware, I also double checked by using the samsung magician.

I did give the system a full mbam scan earlier in the day and it came back clean.

I'll try running memtest for a longer time period and uninstalling eset.

Thanks.

Kaxpix · 30 Oct 2013

I've uninstalled eset and installed microsoft security essentials, but still seem to be having the issue.

I've attached an updated report with the new bsods that happened.

Kaxpix · 30 Oct 2013

I also ran Windows Memory Diagnostic and it came back with this: "The Windows Memory Diagnostic tested the computer's memory and detected no errors"

Arc · 31 Oct 2013

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.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If memtest 56+ shows no 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.