mb: Asrock 4coreDual-SATA2 R2.0
Pr: Intel Dual core E5200
win7 Pro 32 bit Retail
Perfectly stable build in every other way but hangs on shutdown. Probably a process that's stuck or a bad driver..........help!!
You have drivers from as far back as 1996. I am truly surprised it was at all stable.
the DMP point to xchal.sys (also 2 years old) and I cant find what thed files owner was.
How To Find Drivers:- - The most common drivers are listed on this page: Driver Reference- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - Driver manufacturer links are on this page: Drivers and Downloads
Bad drivers needing update
Code:giveio.sys 0x89a2b000 0x89a2b680 0x00000680 0x316334f5 4/3/1996 22:33:25 LNE100V5.sys 0x903ef000 0x903f7d80 0x00008d80 0x3bd7ca48 10/25/2001 04:16:08 nv4_mini.sys 0x900cc000 0x9037e2c0 0x002b22c0 0x4182ec49 10/29/2004 21:20:09 zd1211u.sys 0x9c1ce000 0x9c20d600 0x0003f600 0x41c962f2 12/22/2004 08:05:06 speedfan.sys 0x899e4000 0x899e5480 0x00001480 0x4516880f 9/24/2006 09:28:47 fetnd6.sys 0x903e4000 0x903eec00 0x0000ac00 0x485a46e5 6/19/2008 07:45:41 xcmem.sys 0x909da000 0x90a32000 0x00058000 0x49b63923 3/10/2009 05:55:47 xchal.sys 0x9042d000 0x909da000 0x005ad000 0x49b63944 3/10/2009 05:56:20 xcbda.sys 0x89400000 0x89426900 0x00026900 0x49b639a3 3/10/2009 05:57:55 spldr.sys 0x899dc000 0x899e4000 0x00008000 0x4a084ebb 5/11/2009 12:13:47
DMP
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\Seven Forums\071010-25531-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 (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x82809000 PsLoadedModuleList = 0x82948570 Debug session time: Sun Jul 11 00:45:46.609 2010 (GMT-4) System Uptime: 0 days 0:00:14.703 Loading Kernel Symbols ............................................................... ........................................................ Loading User Symbols Loading unloaded module list .... 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_CALLER (c2) The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc. Arguments: Arg1: 00000007, Attempt to free pool which was already freed Arg2: 00001097, (reserved) Arg3: 08160001, Memory contents of the pool block Arg4: 865c06a8, Address of the block of pool being deallocated Debugging Details: ------------------ GetPointerFromAddress: unable to read from 82968700 Unable to read MiSystemVaType memory at 829480c0 *** WARNING: Unable to verify timestamp for viaide.sys *** ERROR: Module load completed but symbols could not be loaded for viaide.sys *** WARNING: Unable to verify timestamp for PCIIDEX.SYS *** ERROR: Module load completed but symbols could not be loaded for PCIIDEX.SYS *** WARNING: Unable to verify timestamp for amdxata.sys *** ERROR: Module load completed but symbols could not be loaded for amdxata.sys *** WARNING: Unable to verify timestamp for xcbda.sys *** ERROR: Module load completed but symbols could not be loaded for xcbda.sys *** WARNING: Unable to verify timestamp for fetnd6.sys *** ERROR: Module load completed but symbols could not be loaded for fetnd6.sys *** WARNING: Unable to verify timestamp for LNE100V5.sys *** ERROR: Module load completed but symbols could not be loaded for LNE100V5.sys *** WARNING: Unable to verify timestamp for spldr.sys *** ERROR: Module load completed but symbols could not be loaded for spldr.sys *** WARNING: Unable to verify timestamp for nv4_mini.sys *** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys *** WARNING: Unable to verify timestamp for xcmem.sys *** ERROR: Module load completed but symbols could not be loaded for xcmem.sys *** WARNING: Unable to verify timestamp for xcfe.sys *** ERROR: Module load completed but symbols could not be loaded for xcfe.sys *** WARNING: Unable to verify timestamp for drmk.sys *** ERROR: Module load completed but symbols could not be loaded for drmk.sys *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys *** WARNING: Unable to verify timestamp for dxg.sys *** ERROR: Module load completed but symbols could not be loaded for dxg.sys POOL_ADDRESS: GetPointerFromAddress: unable to read from 82968700 Unable to read MiSystemVaType memory at 829480c0 865c06a8 BUGCHECK_STR: 0xc2_7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 91437e91 to 82920c4e STACK_TEXT: 80d8aeb0 91437e91 865c06a8 53584956 865c06a8 nt!ExFreePoolWithTag+0x1b2 WARNING: Stack unwind information not available. Following frames may be wrong. 80d8aec4 91437f9e 85a03000 865c06a8 00000000 xchal+0x2e91 80d8aedc 91446faf 85a03000 865c06a8 00000000 xchal+0x2f9e 80d8aef8 9144c766 85a03000 00000000 865c06a8 xchal+0x11faf 80d8af1c 9144c7b8 85a03000 865c06f9 00000001 xchal+0x17766 80d8af3c 914473e9 85a03002 80d8afa4 8285e815 xchal+0x177b8 80d8af48 8285e815 85a03444 85a03000 00000000 xchal+0x123e9 80d8afa4 8285e678 8292ad20 864d8920 00000000 nt!KiExecuteAllDpcs+0xf9 80d8aff4 8285de3c 8e32f96c 00000000 00000000 nt!KiRetireDpcList+0xd5 80d8aff8 8e32f96c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c 8285de3c 00000000 0000001a 00d6850f bb830000 0x8e32f96c STACK_COMMAND: kb FOLLOWUP_IP: xchal+2e91 91437e91 ?? ??? SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: xchal+2e91 FOLLOWUP_NAME: MachineOwner MODULE_NAME: xchal IMAGE_NAME: xchal.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49b63944 FAILURE_BUCKET_ID: 0xc2_7_xchal+2e91 BUCKET_ID: 0xc2_7_xchal+2e91 Followup: MachineOwner ---------
looks like the most onerous driver (circa 1996) is from my install of speed fan system tool.
The other really old items are for my old lan card and graphics card. Time for an upgrade maybe.
I read on another forum that ASUS tv tuner cards might cause the shutdown problem that I am having. I do have a pair of them running under the hood....can anyone confirm this and comment on what fix is available?
thx
Hi and welcome
nv4_mini.sys (circa 2004) nv4_mini.sys is a process belonging to the NVIDIA Compatible Windows 2000 Miniport Driver, Version 169.02 program . "nv4_mini.sys is a nv4_mini.sys" "belonging to NVIDIA Compatible Windows 2000 Miniport Driver, Version 169.02" "from NVIDIA Corporation"
A six year old miniport driver could do it easily. anythiing dated July 13, 2009 or before (win 7 release date) is considered in need of updating.
TV tuner cards can cause it but the type of BSOD probably would be different.
Good Luck
Ken J
Quote