Seemingly random BSOD

[rsw114]

Hi guys was wondering if you could help. I seem to be getting random BSODs. I can't track it to one particular event. Most recent crashes have been while downloading Elder Scrolls Online, Installing software and streaming a video clip.
At first I thought it might be due to an ethernet port drive issue but I have since uninstalled that driver and the BSODs persist.
I've been able to play games with no problems so any help would be much appreciated.

 

[koolkat77]

Welcome to the forum rsw114,

Reduce items at start-up: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

DAEMON Tools Pro Agent	"c:\program files (x86)\daemon tools pro\dtagent.exe" -autorun	aylith-PC\aylith	HKU\S-1-5-21-3866811646-1938984282-1831439309-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Daemon Tools/Alchohol is known to cause BSODs:
How to remove sptd.sys from system
Registry and SPTD problems | DAEMON Pro Help

Avast contributes in BSOD's. Please remove it for testing purpose. Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Run a System file check (SFC): http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!:-

xusb21.sys Fri Aug 14 04:10:17 2009 (4A848F49)
XBox USB wireless controller [br] BSOD issues in Win7 with 2009 driver (found in mid-2012)
Driver Reference Table - xusb21.sys

SaiU0CCC.sys Fri Apr 23 16:59:27 2010 (4BD17D8F)
Unknown driver - suspect it's part of Saitek device (Saitek HDD Filter Driver)
Driver Reference Table - SaiU0CCC.sys

bcmwlhigh664.sys Tue Apr 19 13:13:08 2011 (4DAD3604)
Broadcom 802.11 USB Network Adapter Driver
Driver Reference Table - bcmwlhigh664.sys

AxtuDrv.sys Thu May 19 13:42:38 2011 (4DD4C9EE)
Most likely the AsRock Extreme Tuner.[br]Driver found in C:\Windows\SysWOW64\Drivers\AxtuDrv.sys[br]
Driver Reference Table - AxtuDrv.sys

MBfilt64.sys Fri Jul 31 09:40:32 2009 (4A7267B0)
Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver) - Was found in the latest Win8 version available from Realtek on 07Sep2013
Driver Reference Table - MBfilt64.sys

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Perform a clean install of a driver following: How to Clean Left Over Driver Files with Driver Sweeper

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If this does not provide stability. Test RAM.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

BSOD BUGCHECK SUMMARY

[FONT="Lucida Console"]Debug session time: Tue Apr 15 18:27:34.524 2014 (UTC + 6:00)
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
System Uptime: 0 days 15:07:55.539
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4884 )
BugCheck C4, {91, 2, fffffa800b9cfb50, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
	the operating system. The only supported way to extend a kernel
	mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa800b9cfb50
Arg4: 0000000000000000
BUGCHECK_STR:  0xc4_91
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0xc4_91_nt!_??_::FNODOBFM::_string_+4884
MaxSpeed:     3300
CurrentSpeed: 3300
BiosVersion = P1.90
BiosReleaseDate = 07/12/2013
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Apr 15 03:18:57.752 2014 (UTC + 6:00)
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
System Uptime: 0 days 5:34:55.158
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )
BugCheck 1A, {41790, fffffa800442cbf0, ffff, 0}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa800442cbf0
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  Bethesda.net_L
FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8
MaxSpeed:     3300
CurrentSpeed: 3300
BiosVersion = P1.90
BiosReleaseDate = 07/12/2013
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Apr 14 21:35:15.801 2014 (UTC + 6:00)
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
System Uptime: 0 days 3:29:26.206
Probably caused by : memory_corruption ( nt!MmCopyToCachedPage+223 )
BugCheck 3B, {c0000005, fffff80002f06ff3, fffff88009ebf8e0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002f06ff3, Address of the instruction which caused the bugcheck
Arg3: fffff88009ebf8e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!MmCopyToCachedPage+223
MaxSpeed:     3300
CurrentSpeed: 3300
BiosVersion = P1.90
BiosReleaseDate = 07/12/2013
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Apr 14 18:05:27.087 2014 (UTC + 6:00)
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
System Uptime: 0 days 20:35:26.491
Probably caused by : win32k.sys ( win32k!EngTextOut+11e )
BugCheck 50, {fffff9c0c230f0e4, 0, fffff960000346e2, 5}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Bugcheck code 00000050
Arguments: 
Arg1: fffff9c0c230f0e4, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960000346e2, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!EngTextOut+11e
MaxSpeed:     3300
CurrentSpeed: 3300
BiosVersion = P1.90
BiosReleaseDate = 07/12/2013
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

 

[rsw114]

Thanks for the reply koolkat77 I'll do what you suggested and post any updates to the situation.