I've been suffering the BSOD

[BobT]

Hi,
I've been suffering the BSOD crash thing and decided to try your sfc/scannow suggestion in option two
several times with restarts and also downloaded the system update readiness tool.

I've attached the zipped file to see if anyone could possibly please enlighten me as to the best way to go with this one. Thanks.

View attachment 332879

 

[essenbe]

BobT would you please run the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html and use option #2 and just click the 'Grab All' button then give it a few minutes to do its work. Thanks.

 

[BobT]

Thanks essenbe,
Here's the file hopefully.

 

[essenbe]

thanks BobT, I guess. Darn, you have BSODs going back to 2011. A whole lot of them, but I'm certain you know that. I ran the 5 most recent ones, and 3 of them were this

[CODEDEBUG_FLR_IMAGE_TIMESTAMP: 531590fb
IMAGE_VERSION: 6.1.7601.18409
STACK_COMMAND: .cxr 0xfffff880028fed50 ; kb
IMAGE_NAME: memory_corruption][/CODE]

To me, this is the most serious, as it will make much of what the debugger unreliable.

I also got these

athrx
start             end                 module name
fffff880`05616000 fffff880`05785000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Wed Jul 08 19:49:13 2009 (4A553E89)
    CheckSum:         0016D79F
    ImageSize:        0016F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This is your Atheros network adapter driver, the driver is obviously pretty old, see if you can update it.

intelppm
start             end                 module name
fffff880`04bcb000 fffff880`04be1000   intelppm   (pdb symbols)          c:\symcache\intelppm.pdb\08BB31C0378D48EC8CB513240E096A171\intelppm.pdb
    Loaded symbol image file: intelppm.sys
    Mapped memory image file: c:\symcache\intelppm.sys\4A5BC0FD16000\intelppm.sys
    Image path: \SystemRoot\system32\DRIVERS\intelppm.sys
    Image name: intelppm.sys
    Timestamp:        Mon Jul 13 18:19:25 2009 (4A5BC0FD)
    CheckSum:         0000F4EC
    ImageSize:        00016000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation

Intel Processor driver

SYMBOL_NAME:  USBSTOR!USBSTOR_SyncSendUsbRequest+c7
FOLLOWUP_NAME:  MachineOwner
IMAGE_NAME:  hardware
DEBUG_FLR_IMAGE_TIMESTAMP:  0
IMAGE_VERSION:  6.1.7601.17577
STACK_COMMAND:  .cxr 0xfffff88007379c80 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {7, 16da9c, 16dadc, 0}

USB mass storage driver

Please fill out your System Specs​

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

A couple of those come from Windows Update, so please make sure your Windows Updates are all installed. Check your computer on the Manufacturer's web site and see if you can update some of the motherboard drivers with more current Windows 7 Drivers.

Because we had 3 dump files blaming Memory Corruption please:
​

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask​

 

[BobT]

Thanks essenbe,

I'm on nights at the moment so not much spare time, so have not yet downloaded and ran your memory test. I did manage to get updates for a lot of the drivers, downloaded all the latest windows updates, uninstalled old and installed new antivirus software, ran disk cleanup, file cleanup and windows own memory test and so far, it's found no errors and the machine has been working fine again.
Will come back with more when I get more time to do further checks.

 

[essenbe]

As long as you're not having BSODs, there is little reason to run a lot of checks. If you have BSODs, go back to my previous post and run that particular test, the Windows test is not very comprehensive. Be careful with disk cleanup utilities, including the Windows one. They can delete error reporting which we will need if debugging is necessary.

There is no hurry. Just whenever it is convinent for you. We are open 24/7. So whenever you feel like it and if you are running well, I would leave it alone.