Problems? See this thread at archive.org.
Hi all, this is my first thread about my new F80Q.It has BSOD problem during cold boot or if I open bios at cold boot it hangs.Then I have to do manual restart.I have been used Xp and Vista both (now running Vista Home Premium).
I have included dump files.Please someone tell me what to do.
-
Attached Files:
-
-
What service pack of Vista (need to know which symbols to use for the debugger)? Are any accessories connected to the computer?
If you are crashing inside the BIOS setup that is a low level problem that probably doesn't have anything to do with windows.
I hope you have tried resetting the BIOS to defaults. Also see if there is a more recent version of your BIOS available. -
I am using service pack 1 and updated BIOS.Version is 219 and sometimes I use pen drive and headset.
-
Here's your debug...
Try running memtest86+ though a few passes to see if it detects memory errors. Seems like you may have a back stick of RAM.Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Bob\Desktop\Mini062009-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 Executable search path is: Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 6000.16386.x86fre.vista_rtm.061101-2205 Machine Name: Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11db0 Debug session time: Fri Jun 19 23:33:14.705 2009 (GMT-4) System Uptime: 0 days 0:00:47.453 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 81d3a2e5, a4ab9c30, 0} Probably caused by : memory_corruption Followup: memory_corruption --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 81d3a2e5, The address that the exception occurred at Arg3: a4ab9c30, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!NtSetValueKey+250 81d3a2e5 8b4704 mov eax,dword ptr [edi+4] TRAP_FRAME: a4ab9c30 -- (.trap 0xffffffffa4ab9c30) ErrCode = 00000000 eax=a4d44318 ebx=00000000 ecx=00000004 edx=00000000 esi=00000dba edi=00000000 eip=81d3a2e5 esp=a4ab9ca4 ebp=a4ab9d44 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 nt!NtSetValueKey+0x250: 81d3a2e5 8b4704 mov eax,dword ptr [edi+4] ds:0023:00000004=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x8E PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 81c8c96a to 81d3a2e5 STACK_TEXT: a4ab9d44 81c8c96a 00000864 0516f004 00000000 nt!NtSetValueKey+0x250 a4ab9d44 77d90f34 00000864 0516f004 00000000 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 0516efd8 00000000 00000000 00000000 00000000 0x77d90f34 STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt 2 errors : !nt (81d3a011-81d3a111) 81d3a010 56 *05 44 24 1c 50 ff 74 24 1c ff 35 88 30 f0 81 V.D$.P.t$..5.0.. ... 81d3a110 5d *cc 89 5d d8 8b f8 89 7d d4 3d 22 00 00 c0 75 ]..]....}.="...u MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: STRIDE FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE BUCKET_ID: MEMORY_CORRUPTION_STRIDE Followup: memory_corruption --------- -
Here is the second one. It's another memory error, this time instead of in the kernel it's in a networking driver. I'm not going to do any more until you try memtest, let me know what happens. I'm pretty sure it'll turn up some memory errors, and I think you most likely have a faulty stick of RAM as I've already said.
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Bob\Desktop\Mini062009-02.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 Executable search path is: Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 6000.16386.x86fre.vista_rtm.061101-2205 Machine Name: Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11db0 Debug session time: Sat Jun 20 04:49:35.666 2009 (GMT-4) System Uptime: 0 days 0:00:32.385 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list .. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {b, 2, 0, 80613608} Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+2f ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000b, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 80613608, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac Unable to read MiSystemVaType memory at 81d11780 0000000b CURRENT_IRQL: 2 FAULTING_IP: NETIO!RtlGetNextExpiredTimerWheelEntry+2f 80613608 8b5808 mov ebx,dword ptr [eax+8] CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: svchost.exe TRAP_FRAME: 87651ebc -- (.trap 0xffffffff87651ebc) ErrCode = 00000000 eax=00000003 ebx=00000000 ecx=864ae008 edx=864ae1d0 esi=0000003f edi=00000cb5 eip=80613608 esp=87651f30 ebp=87651f40 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 NETIO!RtlGetNextExpiredTimerWheelEntry+0x2f: 80613608 8b5808 mov ebx,dword ptr [eax+8] ds:0023:0000000b=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 80613608 to 81c8fc44 STACK_TEXT: 87651ebc 80613608 badb0d00 864ae1d0 89e37034 nt!KiTrap0E+0x2ac 87651f40 8b91e97c 00000000 863c8364 00000001 NETIO!RtlGetNextExpiredTimerWheelEntry+0x2f 87651f54 8b91e469 863c8364 87665120 87666a80 tcpip!TcpProcessExpiredTcbTimers+0x1c 87651f88 81ca93ae 863ad678 00000001 09a6b672 tcpip!TcpPeriodicTimeoutHandler+0x16b 87651ff4 81c90d8d a4d23d10 00000000 00000000 nt!KiRetireDpcList+0x147 87651ff8 a4d23d10 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x3d WARNING: Frame IP not in any known module. Following frames may be wrong. 81c90d8d 00000000 0000001a 00c1850f bb830000 0xa4d23d10 STACK_COMMAND: kb FOLLOWUP_IP: NETIO!RtlGetNextExpiredTimerWheelEntry+2f 80613608 8b5808 mov ebx,dword ptr [eax+8] SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: NETIO!RtlGetNextExpiredTimerWheelEntry+2f FOLLOWUP_NAME: MachineOwner MODULE_NAME: NETIO IMAGE_NAME: NETIO.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4549b319 FAILURE_BUCKET_ID: 0xD1_NETIO!RtlGetNextExpiredTimerWheelEntry+2f BUCKET_ID: 0xD1_NETIO!RtlGetNextExpiredTimerWheelEntry+2f Followup: MachineOwner ---------
ASUS F80Q Blue Screen Problem
Discussion in 'Asus' started by tareq, Jun 23, 2009.
