Solved Random and very frequent BSODs during the past month

[cranburysquash]

I have been experiencing frequent - several times per day - crashes, for different reasons. Even had a failure while trying to register for this forum.

Any assistance greatly appreciated.

Crash log attached

 

[koolkat77]

Welcome to the forum cranburysquash,

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!:-

PxHelp20.sys Sat Feb 3 03:23:57 2007 (45C3ABED)
Sonic CD/DVD driver (used by many different CD/DVD programs)
Driver Reference Table - PxHelp20.sys

LVUSBSta.sys Thu May 10 10:00:54 2007 (464298F6)
Logitech QuickCam
Driver Reference Table - LVUSBSta.sys

LV302V32.SYS Thu May 10 10:09:48 2007 (46429B0C)
Logicool Qcam
Driver Reference Table - LV302V32.SYS

FNETURPX.SYS Sat Oct 4 08:26:51 2008 (48E6D46B)
FNet Turbo HDD USB Driver - Also part of AsRock XFastUSB package
Driver Reference Table - FNETURPX.SYS

Rt86win7.sys Thu Feb 26 15:04:22 2009 (49A65B16)
Realtek NIC
Driver Reference Table - Rt86win7.sys

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

netr61.sys Wed Apr 7 18:07:15 2010 (4BBC7573)
Ralink RT61 Turbo Wireless adapter (you may have a different manufacturer)
Driver Reference Table - netr61.sys

Remove this software!!

AsrAppCharger.sys Fri Jun 11 12:37:02 2010 (4C11D98E)
ASRock App Charger Likely BSOD cause.
Driver Reference Table - AsrAppCharger.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

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

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

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

Run Disk Check on your Hard Drive(s): http://www.sevenforums.com/tutorials/433-disk-check.html

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"]Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Tue Apr 15 20:17:29.002 2014 (UTC + 6:00)
System Uptime: 0 days 12:16:05.261
BugCheck 50, {fc360218, 0, 829596e5, 0}
Probably caused by : win32k.sys ( win32k!GreUpdateSpriteVisRgn+6b )
BUGCHECK_STR:  0x50
PROCESS_NAME:  scrnsave.scr
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Tue Apr 15 05:43:21.771 2014 (UTC + 6:00)
System Uptime: 0 days 3:54:11.943
BugCheck D1, {d, 2, 0, 999dc85a}
*** WARNING: Unable to verify timestamp for netr61.sys
*** ERROR: Module load completed but symbols could not be loaded for netr61.sys
Probably caused by : nwifi.sys ( nwifi!Dot11GetSenderAddr+8 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Mon Apr 14 20:41:24.154 2014 (UTC + 6:00)
System Uptime: 0 days 15:05:17.426
BugCheck A, {0, 2, 1, 83074188}
Probably caused by : ntkrnlmp.exe ( nt!KiUnlinkWaitBlocks+41 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Mon Apr 14 05:38:20.669 2014 (UTC + 6:00)
System Uptime: 0 days 3:16:44.841
BugCheck 1000007F, {8, 801c8000, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchFxe+47 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  uTorrent.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Mon Apr 14 02:20:29.867 2014 (UTC + 6:00)
System Uptime: 0 days 0:32:09.039
BugCheck 1A, {41284, f72d001, 8867, c0402000}
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+291 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  iTunes.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Sun Apr 13 15:31:47.422 2014 (UTC + 6:00)
System Uptime: 0 days 18:38:31.819
BugCheck 1000008E, {c0000005, 0, 88023c3c, 0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Sat Apr 12 05:00:13.963 2014 (UTC + 6:00)
System Uptime: 0 days 2:54:37.135
BugCheck 19, {20, aa3a0838, aa3a0938, a200065}
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
Probably caused by : luafv.sys ( luafv!LuafvNormalizeNameComponentEx+bb )
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  MediaServer.ex
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Fri Apr 11 20:37:22.384 2014 (UTC + 6:00)
System Uptime: 0 days 23:57:08.556
BugCheck C5, {4, 2, 1, 8312b8b7}
*** WARNING: Unable to verify timestamp for cfosspeed6.sys
*** ERROR: Module load completed but symbols could not be loaded for cfosspeed6.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+2c7 )
BUGCHECK_STR:  0xC5_2
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Thu Apr 10 20:39:57.299 2014 (UTC + 6:00)
System Uptime: 0 days 11:38:31.616
BugCheck 1000008E, {c0000005, 832636ea, c76bb954, 0}
*** WARNING: Unable to verify timestamp for Rt86win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt86win7.sys
Probably caused by : tcpip.sys ( tcpip!WfpAleTokenCleanupWorkQueueRoutine+21 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Wed Apr  9 18:38:29.065 2014 (UTC + 6:00)
System Uptime: 1 days 16:07:37.631
BugCheck 19, {3, 858167f8, 858167f8, 858163f8}
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+664 )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

 

[cranburysquash]

Hey koolkat - i removed the software you had indicated and my PC has not crashed as yet. I will work on updating the drivers as well. Though for the moment, things look positive.

Assuming that all continues to work without incident, I'll mark this problem as Solved.

Thanx for your quick reply.

 

[koolkat77]

Keep us posted.

Good luck.

 

[cranburysquash]

Just an update...the problem came back, I ran the memory diagnostics - lots of errors - and as a result have purchased new memory modules, installed today. Will see whether that resolves the issue...

If so, I'll come back during next week and mark Solved...

 

[koolkat77]

Thanks for the update

 

[cranburysquash]

OK, now been running for over 4 days with no crash! Definitely seems to point to the memory module being at fault.

 

[koolkat77]

Good luck! We'll be here if you need help.