BSOD:s again..

Nippe · Nov 19, 2010

Programs stop working --> BSOD

When I start up computer it runs fine for a while, but when I try to start up program (ie. some games) they instantly crash and then desktop window manager /explorer stops working which leads to BSOD. If I shut down computer when this stuff starts to happen and restart, it works just perfectly with no errors o_o (I can't restart, have to shut down, power off cables and then boot again) And this happens every day it seems..

Im using Windows 7 Pro x64 (OEM) and have had BSOD:s since I built my PC (about a month ago)

zigzag3143 · Nov 19, 2010

Nippe said:
When I start up computer it runs fine for a while, but when I try to start up program (ie. some games) they instantly crash and then desktop window manager /explorer stops working which leads to BSOD. If I shut down computer when this stuff starts to happen and restart, it works just perfectly with no errors o_o (I can't restart, have to shut down, power off cables and then boot again) And this happens every day it seems..

Im using Windows 7 Pro x64 (OEM) and have had BSOD:s since I built my PC (about a month ago)

Love to help but no DMP files in upload. Try this method

If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

Nippe · Nov 19, 2010

Sorry just found that out and reuploaded.

zigzag3143 · Nov 19, 2010

Nippe said:
When I start up computer it runs fine for a while, but when I try to start up program (ie. some games) they instantly crash and then desktop window manager /explorer stops working which leads to BSOD. If I shut down computer when this stuff starts to happen and restart, it works just perfectly with no errors o_o (I can't restart, have to shut down, power off cables and then boot again) And this happens every day it seems..

Im using Windows 7 Pro x64 (OEM) and have had BSOD:s since I built my PC (about a month ago)

Doing them now back in 15

Ok where to start

1- ASACPI.sys (2005) is a huge (almost always) cause of BSOD's

ASACPI.sys Sun Mar 27 22:30:36 2005

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

2-Remove Avast and replace with Microsoft Security Essentials (and win 7 firewall)

http://www.avast.com/uninstall-utility

http://www.microsoft.com/security_essentials/

3-Hardware. After you fix the above this may resolve itself. IN the mean time there is a hardware problem.

Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Report\Windows_NT6_BSOD_jcgriff2\111910-20997-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03017000 PsLoadedModuleList = 0xfffff800`03254e50
Debug session time: Fri Nov 19 06:46:00.437 2010 (GMT-5)
System Uptime: 0 days 0:29:34.388
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff8000308e197, fffff8800b98d780, 0}

Probably caused by : hardware ( nt!SepNormalAccessCheck+367 )

Followup: MachineOwner
---------

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff8000308e197, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800b98d780, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
nt!SepNormalAccessCheck+367
fffff800`0308e197 61              ???

CONTEXT:  fffff8800b98d780 -- (.cxr 0xfffff8800b98d780)
rax=000007fffff7c000 rbx=fffffa8006c86b60 rcx=fffff8800b98e1f1
rdx=00000000000007ff rsi=fffffa8006c86c20 rdi=fffff880009b2180
rip=fffff8000308e197 rsp=fffff8800b98e150 rbp=fffffa8006c86b60
 r8=fffffa8008dc70e8  r9=0000000000000000 r10=ffffffffffffff7f
r11=fffffa8009f42b01 r12=0000000000000000 r13=0000000000000000
r14=0000000000000001 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!SepNormalAccessCheck+0x367:
fffff800`0308e197 61              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  2

MISALIGNED_IP: 
nt!SepNormalAccessCheck+367
fffff800`0308e197 61              ???

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8000308e197

STACK_TEXT:  
fffff880`0b98e150 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SepNormalAccessCheck+0x367


FOLLOWUP_IP: 
nt!SepNormalAccessCheck+367
fffff800`0308e197 61              ???

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!SepNormalAccessCheck+367

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff8800b98d780 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

Followup: MachineOwner
---------

7: kd> !sym noisy
noisy mode - symbol prompts on
7: kd> ,reload
       ^ Syntax error in ',reload'
7: kd> .reload
DBGHELP: C:\Symbols\ntoskrnl.exe\4C1C44A95dc000\ntoskrnl.exe - OK
DBGENG:  C:\Symbols\ntoskrnl.exe\4C1C44A95dc000\ntoskrnl.exe - Mapped image memory
DBGHELP: nt - public symbols  
         c:\symbols\ntkrnlmp.pdb\30092BE745B24FE2A311A936E7B7486F2\ntkrnlmp.pdb
Loading Kernel Symbols

Thanks

Ken

Nippe · Nov 19, 2010

Okay, installed that driver and made sure its right version now.. (Already installed MSE because tried to solve this problem before too and reports includes all crashes it seems) And I have Comodo firewall, do I have to remove that?

zigzag3143 · Nov 19, 2010

Nippe said:
Okay, installed that driver and made sure its right version now.. (Already installed MSE because tried to solve this problem before too and reports includes all crashes it seems) And I have Comodo firewall, do I have to remove that?

You should it is often involved.

I am adding things to the below post

Ken J

Nippe · Nov 20, 2010

Today they came back.. Everything started when COM Surrogate stopped working and then everything else crashed.. BSOD didn't come before I pressed power button, report below.

Nippe · Nov 20, 2010

Seems like this happens daily on first boot?

Nippe · Dec 2, 2010

BSOD every second startup

I'm getting BSOD after 5 mins from computer startup every first startup of day, after reboot everything works perfectly.

Running 64-bit Win 7 Pro.

EDIT: Seems like reinstalling MSE didn't help.. Any other suggestions?

yowanvista · Dec 2, 2010

Dumps blames MSE, Reinstall it
If you are using Windows Defender turn it off

Code:

Unable to load image \SystemRoot\system32\DRIVERS\MpFilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
Probably caused by : MpFilter.sys ( MpFilter+8e5c )

Nippe · Dec 2, 2010

Ok, reinstalled it.. One thing I forgot to mentoin, sometimes when i boot my pc it just blinks that cursor for a while (between motherboard version screen and "starting up windows" screen and then restart? If that happens pc wont bluescreen after next startup.

Nippe · Dec 3, 2010

Seems like reinstalling MSE didn't help (computer crashed after first startup again).. Any other suggestions?

Nippe · Dec 3, 2010

Still blue screening at first boot

I'm getting BSOD after 5 mins from computer startup every first startup of day, after reboot everything works perfectly.

yowanvista · Dec 3, 2010

Dump blames MSE, reintsall it
Turn off Windows Defender if you are using it

Code:

Unable to load image \SystemRoot\system32\DRIVERS\MpFilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
Probably caused by : MpFilter.sys ( MpFilter+8e5c )

Nippe · Dec 3, 2010

I reinstalled it, don't help.

yowanvista · Dec 3, 2010

Nippe said:
I reinstalled it, don't help.

Remove it temporarily

Nippe · Dec 6, 2010

Link to orginal thread:
http://www.sevenforums.com/crashes-debugging/128583-still-bluescreening-first-boot.html#post1110429

I uninstalled MSE as told and problem still excists, uploading new report..

baarod · Dec 6, 2010

yowanvista said:

Dump blames MSE, reintsall it
Turn off Windows Defender if you are using it

Code:

Unable to load image \SystemRoot\system32\DRIVERS\MpFilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
Probably caused by : MpFilter.sys ( MpFilter+8e5c )

That's not a fault report -- it's just saying you don't have the symbols loaded for MpFilter.sys. Now go back and clean up the other threads you started on this exact same problem and we'll be able to see what's really been done to help you.

http://www.sevenforums.com/crashes-debugging/125758-programs-stop-working-bsod.html
http://www.sevenforums.com/crashes-debugging/128335-bsod-every-second-startup.html
http://www.sevenforums.com/crashes-debugging/128583-still-bluescreening-first-boot.html
http://www.sevenforums.com/crashes-debugging/129207-bsod-s-again.html

Ask an operator to help you if you are unable to do this yourself.

Based on the disjoint information I've been able to gather on this you need to uninstall ALL, and I mean every bit, of third-party junk you might have installed to replace firewalls, anti-virus, system tools etc. That means no Comodo, Avast, PCTools, etc. Leave only a current updated version of Microsoft Security Essentials installed for protection. There's nothing wrong with what Microsoft provides and no third-party outfit knows Windows as well as Microsoft. If they claim they hold some special secrets that Microsoft won't tell you they are lying.

This software removal is just to establish a baseline and to eliminate all of the noise that these other software vendors introduce into the debugging stream with all the nasty hacks they use. I'm virtually certain that you will find you have a bad RAM stick or slot so after uninstalling what I've instructed you to, open Start, type "mdsched" and press enter. Reboot when prompted and report back.

Nippe · Dec 6, 2010

Now go back and clean up the other threads you started on this exact same problem and we'll be able to see what's really been done to help you.

By that you mean to remove old posts?

And I have uninstalled other programs already (atleast they don't shot up in add or remove programs)

baarod · Dec 6, 2010

Nippe said:
Now go back and clean up the other threads you started on this exact same problem and we'll be able to see what's really been done to help you.

Click to expand...

By that you mean to remove old posts?

And I have uninstalled other programs already (atleast they don't shot up in add or remove programs)

It would be most beneficial to combine them with the most recent post. They all have to do with your ongoing bugchecks ("BSOD" is an amateur term that just aggravates experts) so having all the information together in one place will keep the folks trying to help you from trying all of the things other have had you try before. I can report this post for possible operator assistance if you'd like...

How'd that memory test work out by the way? Remember that's the most likely root cause here.

BSOD:s again..

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer