Frequent BSOD's, Same PC Used to Freeze & Crash

[Quadzilla]

Hi,
Recently started experiencing BSOD's on my Dell Studio XPS w/Win Pro 7/64 bit, 12gb RAM. I used to have a problem w/the PC freezing & only way to fix was to turn it off w/power button to reset. No useful dump files were generated. I reinstalled my OS which helped for a while but then the PC started freezing again and now I'm experiencing true BSODs that display a message re creating a dump file. I've attached the output from the SF Diag. tool. Thanks for any assistance you can provide.

EDIT;Sorry all, I noticed after posting that the diagnostic tool had not finished when I thought it did, I'm uploading the updated .zip file, thanks.

 

[koolkat77]

Hello Quadzilla,

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

wdcsam64.sys Wed Apr 16 14:39:08 2008 (4805BB2C)
Western Digital SCSI Arcitecture Model (SAM) WDM driver [br] 2008 driver version has known BSOD issues in Windows
Driver Reference Table - wdcsam64.sys

k57nd60a.sys Thu Aug 6 17:44:32 2009 (4A7AC220)
Broadcom NetLink Gigabit Ethernet NDIS6.x Unified Driver
Driver Reference Table - k57nd60a.sys

HECIx64.sys Fri Sep 18 01:54:16 2009 (4AB293E8)
Intel Management Engine Interface
Driver Reference Table - HECIx64.sys

nusb3hub.sys Fri Nov 20 16:15:57 2009 (4B066C5D)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
Driver Reference Table - nusb3hub.sys

nusb3xhc.sys Fri Nov 20 16:16:01 2009 (4B066C61)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
Driver Reference Table - nusb3xhc.sys

atikmpag.sys Thu Jan 27 04:13:33 2011 (4D409C8D)
ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)
Driver Reference Table - atikmpag.sys

atikmdag.sys Thu Jan 27 04:48:28 2011 (4D40A4BC)
ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)
Driver Reference Table - atikmdag.sys

dtsoftbus01.sys Thu Jun 20 13:22:51 2013 (51C2ADCB)
Daemon Tools driver [br] Possible BSOD issues in Win7
Driver Reference Table - dtsoftbus01.sys

Daemon Tools/Alchohol is known to cause Blue Screens. Please remove it:

• How to remove sptd.sys from system
• Registry and SPTD problems

To perform a clean install of a driver, follow this tutorial:

• How to Clean Left Over Driver Files with Driver Sweeper

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-

• Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• How to Repair Windows 7 System Files with System File Checker

Post a screenshot of your Hard Drive(s) using Crystal Disk Info software:

• CrystalDiskInfo - Software - Crystal Dew World

Run a Hard Drive test:

• How to Use SeaTools for DOS and Windows Disk Check Utility

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

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• How to Run Disk Check in Windows 7

If that does not help, try memtest.

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.

BUGCHECK SUMMARY

[FONT="Lucida Console"]Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Sat Jun  7 00:46:20.102 2014 (UTC + 6:00)
System Uptime: 0 days 0:04:50.164
BugCheck 1E, {ffffffffc0000005, fffff80002ca7150, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Sat Jun  7 00:40:22.626 2014 (UTC + 6:00)
System Uptime: 0 days 0:04:53.015
BugCheck 1000007E, {ffffffffc0000005, fffff800020c025b, fffff88002316908, fffff88002316160}
Probably caused by : ntkrnlmp.exe ( nt!ExpScanGeneralLookasideList+a0 )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Fri Jun  6 21:00:55.994 2014 (UTC + 6:00)
System Uptime: 0 days 0:02:36.055
BugCheck 1E, {ffffffffc0000005, fffff80002ce73c9, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+169 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Wed Jun  4 03:18:59.959 2014 (UTC + 6:00)
System Uptime: 0 days 0:19:01.020
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]