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)
Im using Windows 7 Pro x64 (OEM) and have had BSOD:s since I built my PC (about a month ago)
�� Quote: Originally Posted by Nippe 
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)
Im using Windows 7 Pro x64 (OEM) and have had BSOD:s since I built my PC (about a month ago)
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.
Sorry just found that out and reuploaded.
�� Quote: Originally Posted by Nippe 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)
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
Quote:
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).
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).
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 Stop 0x124 - what it means and what to try
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 Ken
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?
�� Quote: Originally Posted by Nippe 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?
I am adding things to the below post
Ken J
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.
Seems like this happens daily on first boot?
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?
Running 64-bit Win 7 Pro.
EDIT: Seems like reinstalling MSE didn't help.. Any other suggestions?
Dumps blames MSE, Reinstall it
If you are using Windows Defender turn it off
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 )
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.
Seems like reinstalling MSE didn't help (computer crashed after first startup again).. Any other suggestions?
I'm getting BSOD after 5 mins from computer startup every first startup of day, after reboot everything works perfectly.
Dump blames MSE, reintsall it
Turn off Windows Defender if you are using 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 )
I reinstalled it, don't help.
�� Quote: Originally Posted by Nippe I reinstalled it, don't help.
Link to orginal thread:
http://www.sevenforums.com/crashes-d...ml#post1110429
I uninstalled MSE as told and problem still excists, uploading new report..
http://www.sevenforums.com/crashes-d...ml#post1110429
I uninstalled MSE as told and problem still excists, uploading new report..
�� Quote: Originally Posted by yowanvista Dump blames MSE, reintsall it
Turn off Windows Defender if you are using 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 )
http://www.sevenforums.com/crashes-d...king-bsod.html
http://www.sevenforums.com/crashes-d...d-startup.html
http://www.sevenforums.com/crashes-d...irst-boot.html
http://www.sevenforums.com/crashes-d...d-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.
Quote:
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.
And I have uninstalled other programs already (atleast they don't shot up in add or remove programs)
�� Quote: Originally Posted by Nippe Quote:
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.
And I have uninstalled other programs already (atleast they don't shot up in add or remove programs)
How'd that memory test work out by the way? Remember that's the most likely root cause here.
Quote:
I can report this post for possible operator assistance if you'd like...
mdsched and memtest both ran perfectly with no errors detected..
baarod, yowan is correct; the dump blames MpFilter.sys. Now as to whether or not that MpFilter.sys is the real cause is another story. The OP has an obsolete driver loaded on his system. I suggest he update the driver or uninstall the hardware.
Quote:
Probably caused by : Probably caused by : MpFilter.sys
Quote:
skfiltv.sys Thu Aug 14 02:48:33 2008 - probably Pilote USB audio (WDM); Creative wireless headset; Hs-1200 Digital Wireless Headset. Creative Worldwide Support
�� Quote: Originally Posted by CarlTR6 baarod, yowan is correct; the dump blames MpFilter.sys. Now as to whether or not that MpFilter.sys is the real cause is another story. The OP has an obsolete driver loaded on his system. I suggest he update the driver or uninstall the hardware.
Quote:
Probably caused by : Probably caused by : MpFilter.sys
Quote:
skfiltv.sys Thu Aug 14 02:48:33 2008 - probably Pilote USB audio (WDM); Creative wireless headset; Hs-1200 Digital Wireless Headset. Creative Worldwide Support
�� Quote: Originally Posted by baarod �� Quote: Originally Posted by CarlTR6 baarod, yowan is correct; the dump blames MpFilter.sys. Now as to whether or not that MpFilter.sys is the real cause is another story. The OP has an obsolete driver loaded on his system. I suggest he update the driver or uninstall the hardware.
Quote:
Probably caused by : Probably caused by : MpFilter.sys
Quote:
skfiltv.sys Thu Aug 14 02:48:33 2008 - probably Pilote USB audio (WDM); Creative wireless headset; Hs-1200 Digital Wireless Headset. Creative Worldwide Support
�� Quote: Originally Posted by yowanvista �� Quote: Originally Posted by baarod �� Quote: Originally Posted by CarlTR6 baarod, yowan is correct; the dump blames MpFilter.sys.Now as to whether or not that MpFilter.sys is the real cause is another story. The OP has an obsolete driver loaded on his system. I suggest he update the driver or uninstall the hardware.
I'm going to suggest that you follow How to disable Windows Defender in Windows 7 � Simple Help to turn off Defender as well just to prove this point. If the issue goes away, hey, I'm wrong. It's happened once or twice before
Just have to make sure that OP followed directions and completely uninstalled MSSE as well. The goal here is to prevent loading of that filesystem filter driver so the debugger doesn't get lost in the filter chain as it traces through it. Since the RAM tests were reported clean I'm suspecting another filesystem filter like a virtual CD or the like. If MpFilter.sys causes crash (should be removed when I uninstall MSE?), why does comouter still bluescreen on first boot..
Thats driver for HS-1200 wireless..? I'm using HS-1000 USB headset, should I remove that then? And how? Creative got some update tool that cannot find any newer version to my drivers.
Quote:
Now as to whether or not that MpFilter.sys is the real cause is another story. The OP has an obsolete driver loaded on his system. I suggest he update the driver or uninstall the hardware. Quote:
skfiltv.sys Thu Aug 14 02:48:33 2008 - probably Pilote USB audio (WDM); Creative wireless headset; Hs-1200 Digital Wireless Headset. Creative Worldwide Support
skfiltv.sys Thu Aug 14 02:48:33 2008 - probably Pilote USB audio (WDM); Creative wireless headset; Hs-1200 Digital Wireless Headset. Creative Worldwide Support
�� Quote: Originally Posted by Nippe If MpFilter.sys causes crash (should be removed when I uninstall MSE?), why does comouter still bluescreen on first boot..
Thats driver for HS-1200 wireless..? I'm using HS-1000 USB headset, should I remove that then? And how? Creative got some update tool that cannot find any newer version to my drivers.
Quote:
Now as to whether or not that MpFilter.sys is the real cause is another story. The OP has an obsolete driver loaded on his system. I suggest he update the driver or uninstall the hardware. Quote:
skfiltv.sys Thu Aug 14 02:48:33 2008 - probably Pilote USB audio (WDM); Creative wireless headset; Hs-1200 Digital Wireless Headset. Creative Worldwide Support
skfiltv.sys Thu Aug 14 02:48:33 2008 - probably Pilote USB audio (WDM); Creative wireless headset; Hs-1200 Digital Wireless Headset. Creative Worldwide Support
Uninstalled all Creative programs but the driver (skfiltv.sys) is still on my PC, how am I supposed to remove it? And do I even have to reinstall driver after removing?
Places where skfiltv.sys is:
C:\Windows\System32\DriverStore\FileRepository\xfiskv.inf_amd64_neutral_1ce8ee75da7e8191\WinVista\am d64
C:\Windows\System32\DriverStore\FileRepository\xfiskv.inf_amd64_neutral_a25d73415b2fe706\WinVista\am d64
C:\Windows\System32\drivers
Places where skfiltv.sys is:
C:\Windows\System32\DriverStore\FileRepository\xfiskv.inf_amd64_neutral_1ce8ee75da7e8191\WinVista\am d64
C:\Windows\System32\DriverStore\FileRepository\xfiskv.inf_amd64_neutral_a25d73415b2fe706\WinVista\am d64
C:\Windows\System32\drivers
�� Quote: Originally Posted by Nippe Uninstalled all Creative programs but the driver (skfiltv.sys) is still on my PC, how am I supposed to remove it? And do I even have to reinstall driver after removing?
Places where skfiltv.sys is:
C:\Windows\System32\DriverStore\FileRepository\xfiskv.inf_amd64_neutral_1ce8ee75da7e8191\WinVista\am d64
C:\Windows\System32\DriverStore\FileRepository\xfiskv.inf_amd64_neutral_a25d73415b2fe706\WinVista\am d64
C:\Windows\System32\drivers
Places where skfiltv.sys is:
C:\Windows\System32\DriverStore\FileRepository\xfiskv.inf_amd64_neutral_1ce8ee75da7e8191\WinVista\am d64
C:\Windows\System32\DriverStore\FileRepository\xfiskv.inf_amd64_neutral_a25d73415b2fe706\WinVista\am d64
C:\Windows\System32\drivers
Should I just leave those drivers in C:\Windows\System32\DriverStore\FileRepository where they are or try to delete them somehow? Because they need permission from system to be deleted.
You can leave the ones in the FileRepository. Just rename the one in System32\Drivers. If there is no updated driver later than 2008, the hardware is obsolete and not designed for Win 7.
In Creative webpage (Creative Worldwide Support > Fatal1ty USB Gaming Headset HS-1000) they say
So I think that driver should support Windows 7.. Should I try removing it and see if computer don't bluescreen tomorrow? And how can "bluescreen every first startup of the day" be caused by headset driver?
Quote:
This download is a driver providing Microsoft� Windows� 7, Windows Vista� and Windows XP support for certain Creative gaming headsets.
While a 2008 driver could be OK with Win 7, it is definitely not a Win 7 driver. Win 7 was not even released in 2008. The "magic" date for third party Win 7 drivers is July 13, 2009, or later. I suggest you rename this driver from .sys to .old and reboot. The driver won't load; but your device will not work. See how your system does without this driver. You can always rename it back to .sys.
�� Quote: Originally Posted by Nippe And how can "bluescreen every first startup of the day" be caused by headset driver?
�� Quote: Originally Posted by baarod �� Quote: Originally Posted by Nippe And how can "bluescreen every first startup of the day" be caused by headset driver?
Quote:
Folks were trying to get you to believe that MpFilter.sys causes your crash
�� Quote: Originally Posted by CarlTR6 �� Quote: Originally Posted by baarod �� Quote: Originally Posted by Nippe And how can "bluescreen every first startup of the day" be caused by headset driver?
�� Quote: Originally Posted by yowanvista Quote:
Folks were trying to get you to believe that MpFilter.sys causes your crash
I think SFC is a good idea; it certainly cannot hurt anything. I always look to see what the dump analysis blames; but I do not rely on that unless it is something, that experience has taught me, causes conflicts. I agree that filters are a good potential cause of crashes. I also agree with uninstalling Defender and MSE and reinstalling MSE. A fresh install of MSE may cure the problem - unless something else was interfering.
Nippe, run SFC /SCANNOW from a command prompt - right click on Command Prompt and select Run as administrator. At the prompt, type "sfc /scannow" (without the quotes).
Nippe, run SFC /SCANNOW from a command prompt - right click on Command Prompt and select Run as administrator. At the prompt, type "sfc /scannow" (without the quotes).
Wow.. Ran SFC /scannow and it found corrupted files but was unable to fix them, uploading report cause it looks pretty bad :/
Oh, and noticed it ain't "first boot of the day".. If I leave computer without power for about 2 or more hours it crashes after next startup.
Oh, and noticed it ain't "first boot of the day".. If I leave computer without power for about 2 or more hours it crashes after next startup.
�� Quote: Originally Posted by Nippe Wow.. Ran SFC /scannow and it found corrupted files but was unable to fix them, uploading report cause it looks pretty bad :/
Oh, and noticed it ain't "first boot of the day".. If I leave computer without power for about 2 or more hours it crashes after next startup.
Oh, and noticed it ain't "first boot of the day".. If I leave computer without power for about 2 or more hours it crashes after next startup.
Hum.. This is a link to very first thread I started after I set up my new PC, it should give most of information you need.
http://www.sevenforums.com/crashes-d...requently.html
http://www.sevenforums.com/crashes-d...requently.html
Nippe, run SFC at least three times. From my experience, if SFC find multiple problems, it only corrects them one at a time. Let us know the results after three or four runs with SFC. If this does not do the trick, I concur with baarod, it is time to do a clean reinstall.
And programs I got running:
Ok.. Ran SFC like 5 times now.. Don't think it managed to fix anything but heres report anyways:
So only solution is to do clean install? 
What about if problems come back?
What about if problems come back? You can try a repair install: Repair Install. If this does not work, it's time for a clean install: Clean Install Windows 7.
OK, today I decided to reinstall Windows. When computer started installing it crashed after 10% and bluescreened (BAD_POOL_HEADER). That was first startup ofc, after that I tried again and it installed just fine. Seems like its hardware issue?
Ran SFC with clean install now and it didn't find any problems. Will see does if bluescreen tomorrow (hope not)
Might have found a cause for bluescreens! Had a chat with some guy in WoW about those lags and he said that uninstalling some ASUS programs removed them from him.. So I did so and my lags were gone. He also said that program called "SmartDoctor" which has to do something with graphic card fan speeds caused bluescreens for him while playing. So I googled about that thing and found this site:
ASUSTeK Computer Inc.-Forum- Blue Screen Crashes, ASUS Drivers and Smart Doctor
That looks excactly whats been happening for me.. Trying to uninstall those programs and see if that does the trick.
ASUSTeK Computer Inc.-Forum- Blue Screen Crashes, ASUS Drivers and Smart Doctor
Quote:
Ok, I really hope someone from ASUS reads this aswell
If not, at least some information regarding windows crashes with ASUS Drivers:
I have experienced *random* blue screens on PC Startup after buying the 8600 nVidia from ASUS - and as I tend to tune everything to the owner settings I installed the whole software suite that comes with it (including Smart Doctor) - and upgraded all to the latest version from the ASUS download site - still blue screens.
Soooo... I went into digging through the stack dumps of windows to check what is actually happening.
Here is what I found:
If you have the Blue Screen Crash just on windows starting - when it starts to load your software uninstall Smart Doctor and it will go away. The problem with Smart Doctor is, that it is trying to acces the driver features to read the Video Card state and data, before the Video Card Driver finishes to initialize / load fully itself. It accesses so, an uninitialized part of the driver and / or card which does lead to a Page Fault in an Unpaged Area (Driver Memory) -> Blue Screen + Reset.
If not, at least some information regarding windows crashes with ASUS Drivers:
I have experienced *random* blue screens on PC Startup after buying the 8600 nVidia from ASUS - and as I tend to tune everything to the owner settings I installed the whole software suite that comes with it (including Smart Doctor) - and upgraded all to the latest version from the ASUS download site - still blue screens.
Soooo... I went into digging through the stack dumps of windows to check what is actually happening.
Here is what I found:
If you have the Blue Screen Crash just on windows starting - when it starts to load your software uninstall Smart Doctor and it will go away. The problem with Smart Doctor is, that it is trying to acces the driver features to read the Video Card state and data, before the Video Card Driver finishes to initialize / load fully itself. It accesses so, an uninitialized part of the driver and / or card which does lead to a Page Fault in an Unpaged Area (Driver Memory) -> Blue Screen + Reset.
Yes, it does seem like a hardware issue. I suggest that you run Memtest86 from a cold boot after your computer has been off for a while. Run it for at least 7 passes. This will take 6-8 hours. Follow the instructions in this tutorial: RAM - Test with Memtest86+
Seems like computer is still crashing even without any programs installed and SFC don't find any problems.. Going to run Memtest86+ tomorrow (hope it can test 8gb of RAM) and post back results when done.
Very good. We will be waiting for the results.
Okay, I left Memtest86+ running for 6 hours and it seems to have found pretty many problems.. I have no clue how to read those error outputs but seems like errors are between 2gb and 4gb. Guess I just have to start going thru memory sticks 1-by-1 like in RAM - Test with Memtest86+ and see if I can identify bad sticks and then go to shop..
�� Quote: Originally Posted by Nippe Okay, I left Memtest86+ running for 6 hours and it seems to have found pretty many problems.. I have no clue how to read those error outputs but seems like errors are between 2gb and 4gb. Guess I just have to start going thru memory sticks 1-by-1 like in RAM - Test with Memtest86+ and see if I can identify bad sticks and then go to shop..
1) bad drivers. Only use signed drivers that have passed Microsoft Windows Hardware Compatibility Labs Logo certification. Not only will you get better quality but the driver software has to implement the latest features for the OS it's written for.
2) bad memory. Nobody ever believes this at first. When removing the offending DIMM also removes the bugcheck they usually come around.
3) third party anti-malware and *ahem* "utilities". Nobody knows Windows better than Microsoft. Be suspect of anyone who tells you otherwise. Sure there are exceptions, like Marc Russinovich who started Winternals before Microsoft bought them.
4) malware. It shouldn't surprise you that software whose only aim is to do evil things might not be written with the greatest attention to quality. Techniques such as rootkit injection, polymorphism and obfuscation might cloak this malware so well as to evade detection by even the best scanners but, when it crashes, it gives itself away.
�� Quote: Originally Posted by Nippe Okay, I left Memtest86+ running for 6 hours and it seems to have found pretty many problems.. I have no clue how to read those error outputs but seems like errors are between 2gb and 4gb. Guess I just have to start going thru memory sticks 1-by-1 like in RAM - Test with Memtest86+ and see if I can identify bad sticks and then go to shop..
Tested each individual RAM stick with every of them passing (1 hour testing, 3 passes) and then started reading motherboard manual..
It says that my motherboard (P7H55-M PRO without integrated GPU) doesn't support more than 2 sticks of RAM type I have (CORSAIR CM3X2048-1333C9DHX ver3.3), 4 sticks are only supported with same model but with integrated GPU.
My motherboard seems to support "CORSAIR CM3X1024-1333C9 ver1.1" with 2x1gb sticks. And that manual also says my motherboard won't support any combinations with 4 sticks (why is there even 4 slots then..)
What should I do in this case?
It says that my motherboard (P7H55-M PRO without integrated GPU) doesn't support more than 2 sticks of RAM type I have (CORSAIR CM3X2048-1333C9DHX ver3.3), 4 sticks are only supported with same model but with integrated GPU.
My motherboard seems to support "CORSAIR CM3X1024-1333C9 ver1.1" with 2x1gb sticks. And that manual also says my motherboard won't support any combinations with 4 sticks (why is there even 4 slots then..)
What should I do in this case?
Oh, and I cannot test each slot because computer only boots when I have 1 stick in A1 or 2 sticks in A1 and B1 or 4 sticks in all slots.
Ran Memtest86+ with 4 sticks again with no errors.. Seems like problems come only after computer has been powered down for more than 2 hours..?
A cold boot puts more stress on the RAM. You need to run at least 7 passes when testing; 3 is not enough. Some experts recommend 12 or more passes.
Well I don't think that my RAM is broken, I think problem is combatibility with my motherboard.
Btw, found a "fix" to this problem: I won't shut down computer anymore, i just sleep it.
Btw, found a "fix" to this problem: I won't shut down computer anymore, i just sleep it.
Thanks for the update. RAM problems can definitely be caused by RAM incompatible with the motherboard. That is certainly one way to fix it! I have used that method myself. Of course the real fix, is to resolve the RAM problem.
I have used that method myself. Of course the real fix, is to resolve the RAM problem. Waking this old thread because got a blue screen after restarting pc to install Windows updates..
I'm still not sure if my RAM causes these problems (I think I scould try to something like linux boot and watch if that causes any problems)
But I'll add new report from blue screen if that shows anything odd.
I'm still not sure if my RAM causes these problems (I think I scould try to something like linux boot and watch if that causes any problems)
But I'll add new report from blue screen if that shows anything odd.
Oh, and Windows error reporting center told that it was caused by a driver (but not what driver), any1 here that can see it from dump?
Không có nhận xét nào:
Đăng nhận xét