BSOD's and random blackout reboots

[kemo]

I don't know if this is the same as my previous BSOD, but I'm still having troubles using 7. Enjoy, it drives me nuts trying to read these, I know some of you fellas love reading these . I try to but am a miserable fail!

Oh and if it is Nvidia again, I JUST downloaded the latest driver, which just so happens to be dated 11/26/09 too

 

[zigzag3143]

I don't know if this is the same as my previous BSOD, but I'm still having troubles using 7. Enjoy, it drives me nuts trying to read these, I know some of you fellas love reading these . I try to but am a miserable fail!

Oh and if it is Nvidia again, I JUST downloaded the latest driver, which just so happens to be dated 11/26/09 too

Hi and welcome

Well this crash wasnt caused by the vid driver, but you do have some really old ones on the system (listed below)

This crash was caused by Memory Management. Might also have a heat component which would reflect in video problems.

I would
Download memtestx86 and run it overnight. That time is needed for both the ram test and to see if there is a heat issue

Run A system file check to verify and repair your system files
type cmd in search>right click and run as admin>SFC /SCANNOW

The usual also apply

If you are overclocking stop
if you have a raid update its driver

Kenn J+




secdrv.SYS fffff880`07931000 202067c9`0793c000 0x20206f490000b000 0x4508052e 9/13/2006 8:18:38 AM
ASACPI.sys fffff880`03fe8000 fffff880`03ff0000 0x00008000 0x4546b048 10/30/2006 9:09:12 PM
AsIO.sys fffff880`037b2000 fffff880`037b9000 0x00007000 0x47663d55 12/17/2007 4:11:49 AM

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


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

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
[B]Built by: 7600.16385.amd64fre.win7_rtm.090713-1255[/B]
Machine Name:
Kernel base = 0xfffff800`02810000 PsLoadedModuleList = 0xfffff800`02a4de50
Debug session time: Thu Nov 26 20:50:11.828 2009 (GMT-5)
System Uptime: 0 days 2:39:35.467
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, c818, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42c75 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 000000000000c818
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88008080900 -- (.trap 0xfffff88008080900)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000007fef87ec rbx=0000000000000000 rcx=000000000000c800
rdx=fffffa80053b1060 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000289e995 rsp=fffff88008080a90 rbp=fffff88008080b40
 r8=fffff88008080ba0  r9=fffff6fb41ffbe18 r10=fffff683ff7c3f60
r11=fffff6fb41ffbe18 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiCheckVirtualAddress+0x155:
fffff800`0289e995 483b4118        cmp     rax,qword ptr [rcx+18h] ds:0003:00000000`0000c818=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000282cb6e to fffff80002881f00

STACK_TEXT:  
fffff880`08080798 fffff800`0282cb6e : 00000000`0000001a 00000000`00041287 00000000`0000c818 00000000`00000000 : nt!KeBugCheckEx
fffff880`080807a0 fffff800`0287ffee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42c75
fffff880`08080900 fffff800`0289e995 : 00000000`03b9f9a0 fffff880`03ed2333 00000000`00000000 fffff880`08080b88 : nt!KiPageFault+0x16e
fffff880`08080a90 fffff800`0289be13 : 00000000`00000000 00000000`00000000 fffff880`08080ca0 fffff880`03efd906 : nt!MiCheckVirtualAddress+0x155
fffff880`08080ac0 fffff800`0287ffee : 00000000`00000008 00000000`03d42e10 000007fe`f884d601 fffffa80`00000000 : nt!MmAccessFault+0x233
fffff880`08080c20 000007fe`f87ec7b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`03b9f520 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f87ec7b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+42c75
fffff800`0282cb6e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42c75

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42c75

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42c75

Followup: MachineOwner

---------

 

[kemo]

funny , cuz I use the same computer and am on Ubuntu all the time, no crashes. Memtest is an option on bootup (thankyou ubuntu). I'll give it a shot and see what the deal is.

 

[kemo]

Needless to say, it passed the ram testing No overclocking... but why is it that 7 can't take the overclocking but my other OS's can???

It's a serious question even though I'm tryin to have a little fun with this, the more I learn, the better! I'm at the point where I'm extremely confused, but it's ok for now... I don't use 7 unless there is something Ubuntu can't do.

 

[Geo64]

Because of the memory management error, you can completely uninstall antivirus to test along with updating those drivers.

Errors in dwm tend to be from "found" hacked/cracked versions of Windows.

 

[usasma]

Update your Asus utility programs to versions that are Win7 compatible.
The ASACPI.SYS can be updated with the ATK0110 ACPI utility, the AISuite utility, or the PCProbe utility (there may be more).
I suspect that the AsIO.sys can be updated with either the AISuite or the PCProbe utilities.

 

[kemo]

Because of the memory management error, you can completely uninstall antivirus to test along with updating those drivers.

Errors in dwm tend to be from "found" hacked/cracked versions of Windows.

If I had a hacked version of any windows, I wouldn't be on here.

Updated "ATK0110", whatever that is... as far as the rest of the ASUS stuff...
There are no drivers for 7 that I can update... well, no drivers period. Will report on future crashes.