Solved BSOD soon after start up and windows always recovers.

[Frasure]

BSOD soon after start *SOLVED*

I have been getting a BSOD soon after I start the computer up and once windows recovers it won't do it again until I restart the computer then soon after the restart it will happen again. I can work and play games on it practically all day with no troubles it just seems to be after I start it up and once it recovers it's good.

I have been doing a lot of reading in the forums and feel this is the place to post this I want to let you know I appreciate any help on this and thank you for your time.

==================================================
Dump File : 082613-12760-01.dmp
Crash Time : 8/26/2013 4:14:02 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff800`010c5058
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`031d9aa6
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75b80
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18205 (win7sp1_gdr.130708-1532)
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\082613-12760-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 7601
Dump File Size : 291,152
Dump File Time : 8/26/2013 4:15:08 AM
==================================================

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: FFFFF88002632440
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF80002EC5A83
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\082413-19063-01.dmp
C:\Users\TigSam\AppData\Local\Temp\WER-27596-0.sysdata.xml

 

[Northernsoul55]

Hi,

Your logs show:

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

fffff880`09e66418  fffff880`010d015f*** WARNING: Unable to verify timestamp 
for MpFilter.sys*** ERROR: Module load completed but symbols could not be 
loaded for [COLOR=red]MpFilter.sys[/COLOR]

MpFilter.sys is a Filter System Driver designed as the AntiMalware Engine
of MSE which is dependent on fltmgr.sys.

It is probable that there was a previous installation of an AM/AV application.
I would advise running the clean-up tool for any previously installed security
software using the link below:

:ar: Anti-malware Product Removal

Once completed re-install MSE and update. Observe the situation.

Run these tests:




SFC to check the integrity of all Windows 7 system files:

• Click on Start > Type in search cmd
  Right-click cmd after results are displayed and Run as Administrator
  Type SFC /scannow at the prompt
  (Note: There is a space between SFC and /scannow)

:ar: SFC Tutorial

   Note

Select option two. If any problems are found, run the scan 3 times and immediately
reboot the computer after each scan.

Also run :ar: chkdsk in an elevated command prompt in order to check for file system errors and bad sectors on your HDD:

• Click on Start>Type in search cmd
• Right click cmd and Run as Administrator
• At the command prompt please type: chkdsk /f/r
  (There is a space between chkdsk and /f/r

Test your memory:

I would firstly try re-seating the RAM, ensure they are free from dust, and seated properly.
Then run memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Tip

Run these tests overnight, pay particular attention to #3 in tutorial if errors occur

Post back any results.

cheers

Dave

 

[Frasure]

I would firstly try re-seating the RAM, ensure they are free from dust, and seated properly.
Then run memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Tip

Run these tests overnight, pay particular attention to #3 in tutorial if errors occur

Post back any results.

cheers

Dave

Thanks for you're help Dave! it was hardware. one of the memory modules was bad.

BTW - what a great forum I see people getting back up and running all over the place. again thanks for you're time, consider this one closed.

 

[Northernsoul55]

No problem, glad to help

Cheers

Dave