New
#11
Got 3 new bluescreens since my last entry, i am pretty sure this has to do with a wrong driver
Bad pool header BSOD
-
-
New #12
These crashes were caused by memory corruption (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.
If you are overclocking anything reset to default before running these tests.
In other words STOP!!!
1-Memtest.
RAM - Test with Memtest86+*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool
*Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
Any errors are indicative of a memory problem.
If a known good stick fails in a motherboard slot it is probably the slot.
2-Driver verifier
Driver Verifier - Enable and DisableUsing Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users
Next > Read this carefully re Asacpi.sys
The pre 2009 version of this driver is a known bsod cause.
Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM
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 12th 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 (notbefore).
-
New #13
Hello, thanks for your help.
My ram is ok, tested it several times and several days, on 32 bit my problems started after the 3gb switch so i switched back and i think the problem had to do with viruses.
Reinstalled windows hoped it would have solved every bluescreen.
But it seems it was indeed a driver problem, downloaded by Windows update, so i fixed that, thanks to your information and after several hours no bluescreens were encountered.
Well not the known bluescreens atleast.
So when i restarted my pc, i got another one, but this one is simple to fix hope.
Last bluescreen problem i will encounter i hope.
Here is the dump file.
After this, i will learn how to detect the cause of bluescreens my self, i know this has to do with my pagefile, so i've changed the settings to no pagefile and after restart i will reset to the default settings.
Edit :
I found the problem, ntoskrnl.exe is the cause of the crash this time.
I think i can fix this problem with the checkdisk command right ?
-
New #14
Caused by AMD Catalyst Control Center/AMD Vison Engine Control Center. Please uninstall the software through Control Panel -> Uninstall a program.Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [H:\BSODDmpFiles\themaniacboy\012612-25381-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02a03000 PsLoadedModuleList = 0xfffff800`02c48670 Debug session time: Wed Jan 25 17:27:00.638 2012 (UTC - 7:00) System Uptime: 0 days 0:02:22.809 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff683b9fa2388, 0, fffff80002a6a27b, 5} Could not read faulting driver name Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffff683b9fa2388, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff80002a6a27b, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000005, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb2100 fffff683b9fa2388 FAULTING_IP: nt!MiAgeWorkingSet+1d1 fffff800`02a6a27b 488b19 mov rbx,qword ptr [rcx] MM_INTERNAL_CODE: 5 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: CCC.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff880033167c0 -- (.trap 0xfffff880033167c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff683b9fa2388 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002a6a27b rsp=fffff88003316950 rbp=00000003b9fa2388 r8=0000000000000001 r9=fffffa80062a8868 r10=0000000000000005 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po cy nt!MiAgeWorkingSet+0x1d1: fffff800`02a6a27b 488b19 mov rbx,qword ptr [rcx] ds:fffff683`b9fa2388=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a2a3bf to fffff80002a7fc40 STACK_TEXT: fffff880`03316658 fffff800`02a2a3bf : 00000000`00000050 fffff683`b9fa2388 00000000`00000000 fffff880`033167c0 : nt!KeBugCheckEx fffff880`03316660 fffff800`02a7dd6e : 00000000`00000000 fffff683`b9fa2388 00000000`00000000 00000980`00000000 : nt! ?? ::FNODOBFM::`string'+0x44791 fffff880`033167c0 fffff800`02a6a27b : 00000003`00000000 87300001`2210d867 00000000`00000000 00000000`00000073 : nt!KiPageFault+0x16e fffff880`03316950 fffff800`02afbac5 : fffffa80`062a8868 fffff800`00000001 00000000`00000001 fffff880`03316bb0 : nt!MiAgeWorkingSet+0x1d1 fffff880`03316b00 fffff800`02a6a826 : 00000000`0000008f 00000000`00000000 fffffa80`00000000 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x4d786 fffff880`03316b80 fffff800`02a6acd3 : 00000000`00000008 fffff880`03316c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e fffff880`03316bd0 fffff800`02d1afee : fffffa80`03abe680 00000000`00000080 fffffa80`039749e0 00000000`00000001 : nt!KeBalanceSetManager+0x1c3 fffff880`03316d40 fffff800`02a715e6 : fffff880`02f64180 fffffa80`03abe680 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`03316d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiAgeWorkingSet+1d1 fffff800`02a6a27b 488b19 mov rbx,qword ptr [rcx] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiAgeWorkingSet+1d1 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+1d1 BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+1d1 Followup: MachineOwner ---------
-
New #15
I uninstalled it, removed the remaining files through driver sweeper and i am now reinstalling it, if another blue screen occurs caused by CCC than i will uninstall it again without reinstalling
BTW,
What is watchdog.sys ?
I googled it, seems to have something to do with flash player, but i can't uninstall that because it is build in Google chrome.
Also, i have updated DirectX, i hope this solves the rest of the problems.
Thanks for the help, really appreciate it.
-
New #16
watchdog.sys is a system file used by many applications. See how things go with CCC taken care of, or if you have to, uninstall CCC and just install your video card drivers without the CCC software.Last edited by writhziden; 25 Jan 2012 at 23:07. Reason: Did not intend for it to seem I was suggesting uninstalling watchdog.sys; do not uninstall watchdog.sys
-
New #17
-
New #18
-
New #19
-
New #20
Hello, can a bsod caused by ntoskrnl.exe be the problem of a underclocked memory ?
My standard memory clock 1600 mhz, but in the bios it is clocked to 1333mhz.
I think my memory is the problem, but i am not sure, so i'll run memtest86+ again.
Wish me good luck
Quote
Related Discussions