Blue Screen crashes

[gerardmorrissey]

Hi, the BSOD has been happening for last few weeks & on average occurs between half hour to an hour after logging on---generally the more programmes running the more likely it is to happen....any help appreciated

 

[koolkat77]

Welcome to the Forum.

Norton is a known cause of 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

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

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


VSTCNXT6.SYS Thu Oct 16 06:52:22 2008 (48F69046)
Conexant SoftK56 Modem Driver
Driver Reference Table - VSTCNXT6.SYS

VSTAZL6.SYS Thu Oct 16 06:53:42 2008 (48F69096)
Conexant SoftK56 Modem Driver
Driver Reference Table - VSTAZL6.SYS

VSTDPV6.SYS Thu Oct 16 06:57:45 2008 (48F69189)
Conexant SoftK56 Modem Driver
Driver Reference Table - VSTDPV6.SYS

netw5v64.sys Thu Mar 26 22:21:24 2009 (49CBAB84)
Intel Wireless WiFi Link Driver
Driver Reference Table - netw5v64.sys

b57nd60a.sys Sun Apr 26 17:14:55 2009 (49F4422F)
Broadcom NetXtreme Gigabit Ethernet
Driver Reference Table - b57nd60a.sys

igdkmd64.sys Thu May 7 00:22:19 2009 (4A01D55B)
Intel Graphics driver
Driver Reference Table - igdkmd64.sys

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

Run a System file check (SFC): http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.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

Post screenshot(s) of your Hard Drive(s) using Crystal Disk Info Software: CrystalDiskInfo - Software - Crystal Dew World

Run a Hard Drive test: http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html


Run Disk Check on your Hard Drive(s): http://www.sevenforums.com/tutorials/433-disk-check.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.

Summary

Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Thu Feb 13 02:35:08.161 2014 (UTC + 6:00)
System Uptime: 0 days 0:11:55.049
BugCheck 116, {fffffa80027c84e0, fffff88004a27cb0, 0, c}
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+23cb0 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue Feb 11 04:30:52.937 2014 (UTC + 6:00)
System Uptime: 0 days 0:25:28.825
BugCheck 7A, {fffff6fc40006a98, ffffffffc0000185, 1a708860, fffff88000d53000}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7a_c0000185
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue Feb 11 04:04:31.928 2014 (UTC + 6:00)
System Uptime: 0 days 0:24:46.816
BugCheck 7A, {fffff6fc400085f0, ffffffffc0000185, 43bc1860, fffff880010bef44}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7a_c0000185
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue Feb 11 02:59:40.689 2014 (UTC + 6:00)
System Uptime: 0 days 0:30:39.577
BugCheck 7A, {fffff6fc50059b60, ffffffffc0000185, 2da8d880, fffff8a00b36cf46}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36c1a )
BUGCHECK_STR:  0x7a_c0000185
PROCESS_NAME:  ccSvcHst.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue Feb 11 02:26:15.028 2014 (UTC + 6:00)
System Uptime: 0 days 0:26:08.916
BugCheck 7A, {fffff6fc00017718, ffffffffc0000185, 65dc0860, fffff80002ee3dd4}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7a_c0000185
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon Jan 27 00:16:33.647 2014 (UTC + 6:00)
System Uptime: 0 days 3:48:18.535
BugCheck F4, {3, fffffa800546c1f0, fffffa800546c4d0, fffff80002fe0350}
Probably caused by : csrss.exe
BUGCHECK_STR:  0xF4_IOERR
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``