BSOD

[djct]

I am getting frequent instances of BSOD. I have followed the instructions on your forum and created the dump file. I must confess that I am a relative novice and the information is not making much sense to me. So I hope you will bear with me and try to explain what I need to do to resolve the problem.

This is the first time I am using the forum. I hope my post is in the correct format.

 

[YoYo155]

Hi and welcome to SF .
Please run the SFDT (Seven Forum Diagnostic Tool) once again and let it run its course
as most files are missing.

For now test the HDD as the event log shows many many errors.

   Warning

The Following Method Should NOT Be Performed On An SSD!

Testing the HDD:

1. Perform a Disk Check | Disk Check
2. Then Post the results following | THIS METHOD
3. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
4. If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

If SeaTools For DOS does not recognize the drive;
Boot into the BIOS using the *Fxkey.
Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
Set it to IDE then save and exit usually by pressing the F10 key.
Now boot into SeaTools and it should detect the drives.
Start the Long Test and let it run.
Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
and change the SATA setting back to what it was in the first place.

• *Popular BIOS access keys.

 

[djct]

Thank you for prompt reply. I have rerun the SFDT and attach the new zipped folder. I have not run the hard disk test as my drive is an SSD.

djct

 

[YoYo155]

Hi , sorry for the slow reply life got in the way.

Bugcheck:

BugCheck 1000009F, {4, 258, fffffa8003cd9660, fffff80004810740}

*** WARNING: Unable to verify timestamp for btfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for btfilter.sys
Implicit thread is now fffffa80`03cd9660
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[B]Probably caused by : [/B][COLOR=Red][U][B]btfilter.sys[/B][/U][/COLOR] ( btfilter+e373 )

• Driver Reference Table - btfilter.sys

We see that the issue mostly to an old Bluetooth driver;

lmvm btfilter
start             end                 module name
fffff880`060d0000 fffff880`0615f000   btfilter T (no symbols)           
    Loaded symbol image file: btfilter.sys
    Image path: \SystemRoot\system32\DRIVERS\btfilter.sys
    Image name: btfilter.sys
    Timestamp:        [COLOR=Red][U][B]Thu Jul 28 12:09:09 2011[/B][/U][/COLOR]

• Update the driver :: Download :: -
  
  Version: 8.0.0.218​
  Release: 2012-12-21

Avast anti virus is know to cause issues with Windows 7 and it's activity in the stack
is far from thin;

fffff880`0359fb68  fffff880`048d7e31 aswSP+0x2fe31
fffff880`0359fbc8  fffff880`048d7940 aswSP+0x2f940
fffff880`0359fbf8  fffff880`048dfe44 aswSP+0x37e44
fffff880`0359fc48  fffff880`048dfe44 aswSP+0x37e44
fffff880`0359fd78  fffff880`048d7940 aswSP+0x2f940
fffff880`0359fda8  fffff880`048d7e31 aswSP+0x2fe31
fffff880`0359fe08  fffff880`048d7940 aswSP+0x2f940
fffff880`0359fe38  fffff880`048dfe44 aswSP+0x37e44
fffff880`0359fe88  fffff880`048dfe44 aswSP+0x37e44
fffff880`0359ff58  fffff880`048d7940 aswSP+0x2f940
fffff880`0359ff88  fffff880`048d7e31 aswSP+0x2fe31
fffff880`0359ffe8  fffff880`048d7940 aswSP+0x2f940
fffff880`035a0018  fffff880`048dfe44 aswSP+0x37e44
fffff880`035a0068  fffff880`048dfe44 aswSP+0x37e44
fffff880`035a0160  fffff880`048f0770 aswSP+0x48770
fffff880`035a0168  fffff880`048f0ab0 aswSP+0x48ab0
fffff880`035a01b0  fffff880`048f0770 aswSP+0x48770
fffff880`035a01b8  fffff880`048f0ab0 aswSP+0x48ab0
fffff880`035a0288  fffff880`048b4e7e aswSP+0xce7e
fffff880`035a02a0  fffff880`048eca10 aswSP+0x44a10
fffff880`035a02d8  fffff880`048b4f67 aswSP+0xcf67
fffff880`035a02f8  fffff880`048bfb57 aswSP+0x17b57
fffff880`035a0308  fffff880`048b4814 aswSP+0xc814
fffff880`035a0338  fffff880`048c06e4 aswSP+0x186e4
fffff880`035a0348  fffff880`048eca10 aswSP+0x44a10
fffff880`035a03c8  fffff880`048b96e4 aswSP+0x116e4
fffff880`035a03f8  fffff880`048c7313 aswSP+0x1f313

• Driver Reference Table - aswSP.SYS
• Remove Avast using the Removal Tool.
• Install Microsoft Security Essentials as a reliable alternative.

Update your Intel drivers via the online utility :: Intel® Driver Update Utility ::

lmvm igdkmd64
start             end                 module name
fffff880`04c15000 fffff880`057d2660   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        [COLOR=Red][U][B]Fri Oct 21 20:29:55 2011[/B][/U][/COLOR]

• Driver Reference Table - igdkmd64.sys

Update these two drivers as well:

ASMMAP64.sys [COLOR=Red][U][B]Thu Jul 02 12:13:26 2009[/B]
[/U][/COLOR]atkwmiacpi64.sys [COLOR=Red][U][B]Wed Sep 07 04:44:52 2011[/B][/U][/COLOR]

• Driver Reference Table - ASMMAP64.sys
• Driver Reference Table - atkwmiacpi64.sys

ATKACPI driver and hotkey-related utilities - 2012.07.18 - Version V1.0.0020 :: Download ::

Your PC is regularly overheating;

Event[34936]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2013-09-07T11:47:40.169
  Event ID: 89
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: catherine-PC
  Description: 
ACPI thermal zone ACPI\ThermalZone\THRM has been enumerated.             
_PSV = 378K             
_TC1 = 2             
_TC2 = 10             
_TSP = 10000ms             
_AC0 = 0K             
_AC1 = 0K             
_AC2 = 0K             
_AC3 = 0K             
_AC4 = 0K             
_AC5 = 0K             
_AC6 = 0K             
_AC7 = 0K             
_AC8 = 0K             
_AC9 = 0K             
_[COLOR=Red][U][B]CRT = 376K[/B][/U][/COLOR]             
_HOT = 0K             
_PSL - see event data.

• Download Speccy and upload a Screenshot of the summary tab.

As I mentioned earlier the event log is filled with many storage errors, seeing now that
we are dealing with an SSD a different approach must be taken.

• If you have an SSD, make sure the following are up to date:
  1. SSD firmware
  2. BIOS Version
  3. Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
• Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627 for better security steps and scanning tools. Make sure to update the security software before running the full scan.

1. - Download SSD Toolkit.
2.    Warning

   Flashing the BIOS is a risky procedure. If you are uncomfortable
   performing it yourself have a technician perform it for you.
   Regardless, flashing is at your own risk.
   - Asus Support ::
   BIOS 214 - 2013.01.07 ::

   [B][COLOR=Blue][U]Current BIOS:[/U][/COLOR] [/B]Version/Date UX21E.209, 29/11/2011

3. Install using the online utility linked above : Intel® Driver Update Utility :.
4. Continue with the rest of the instructions detailed in the quote.

Keep us posted!