i keep getting blue screens on win 7 i have win 7 on 500GB western digital hard drive runing on sata channel 1 i have both .dmp files and the listings from debug.exe i will include both could you determine my issue i have had this problem for a while and have tried alot of problem solving methods via microsoft.com thanks for any info i have a p4p800mx mobo 2.5 GB ram nvidia 8400gs graphics card sound blaster live 24 bit sound card and ati wonder pci tuner card 800 watt atx psu pentium 4 ht processor 2.8GHz OClocked to 3.0GHz through the bios. i also have tried both oem and microsoft drivers for graphics and i still get an occasional your graphics card has unexpectantly stopped working and has recovered i cant send the actual dmp files it wont let me any info on this matter would be appreciated.
Opened log file 'c:debuglog.txt'
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112709-19343-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers Windows 7 Kernel Version 7100 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7100.0.x86fre.winmain_win7rc.090421-1700 Machine Name: Kernel base = 0x82800000 PsLoadedModuleList = 0x8293f570 Debug session time: Fri Nov 27 14:39:43.708 2009 (GMT-5) System Uptime: 0 days 2:07:57.115 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ......... 0: kd> !analyze -v;r;kv;lmtn;.logclose;q ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************
PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 00000099, A PTE or PFN is corrupt Arg2: 0004e977, page frame number Arg3: 00000002, current page state Arg4: 0004e974, 0
Unloaded modules: 9e523000 9e52e000 hiber_atapor Timestamp: unavailable (00000000) Checksum: 00000000 9e52e000 9e537000 hiber_atapi. Timestamp: unavailable (00000000) Checksum: 00000000 9e537000 9e548000 hiber_dumpfv Timestamp: unavailable (00000000) Checksum: 00000000 9e4ac000 9e516000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 932d9000 932f1000 parport.sys Timestamp: unavailable (00000000) Checksum: 00000000 8aa9d000 8aaaa000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 8aaaa000 8aab5000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 8aab5000 8aabe000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 8aabe000 8aacf000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 Closing open log file c:debuglog.txt My System SpecsSystem Spec Edit/Delete Message Reply With Quote Multi-Quote This Message System Manufacturer/Model Number homemade OS windows 7 CPU pent 4 ht Motherboard asus p4p800mx Memory 2.5 GB Graphics Card Nvidia GeForce 8400 gs Sound Card sound blaster live 24 bit Monitor(s) Displays dual stone age monitors e772p and e773p
Update your System Spec PSU diablotek da series 400w Case factory modded Dell 2350 Cooling air Hard Drives WD 500 GB sata, WD 56 GB IDE Primary, WD 34 GB IDE Slave jcm2302 View Public Profile Find More Posts by jcm2302 Add jcm2302 to Your Contacts Old 1 Minute Ago #2 (permalink) jcm2302 New Member
jcm2302 is on a distinguished road
Join Date: Nov 2009 windows 7 3 posts
jcm2302 is online now Add to jcm2302's Reputation Report Post
Default also i get this
Opened log file 'c:debuglog.txt'
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112709-19593-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers Windows 7 Kernel Version 7100 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7100.0.x86fre.winmain_win7rc.090421-1700 Machine Name: Kernel base = 0x82807000 PsLoadedModuleList = 0x82946570 Debug session time: Fri Nov 27 18:22:52.563 2009 (GMT-5) System Uptime: 0 days 3:42:22.985 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ...... 1: kd> !analyze -v;r;kv;lmtn;.logclose;q ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************
MACHINE_CHECK_EXCEPTION (9c) A fatal Machine Check Exception has occurred. KeBugCheckEx parameters; x86 Processors If the processor has ONLY MCE feature available (For example Intel Pentium), the parameters are: 1 - Low 32 bits of P5_MC_TYPE MSR 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of P5_MC_ADDR MSR 4 - Low 32 bits of P5_MC_ADDR MSR If the processor also has MCA feature available (For example Intel Pentium Pro), the parameters are: 1 - Bank number 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error IA64 Processors 1 - Bugcheck Type 1 - MCA_ASSERT 2 - MCA_GET_STATEINFO SAL returned an error for SAL_GET_STATEINFO while processing MCA. 3 - MCA_CLEAR_STATEINFO SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA. 4 - MCA_FATAL FW reported a fatal MCA. 5 - MCA_NONFATAL SAL reported a recoverable MCA and we don't support currently support recovery or SAL generated an MCA and then couldn't produce an error record. 0xB - INIT_ASSERT 0xC - INIT_GET_STATEINFO SAL returned an error for SAL_GET_STATEINFO while processing INIT event. 0xD - INIT_CLEAR_STATEINFO SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event. 0xE - INIT_FATAL Not used. 2 - Address of log 3 - Size of log 4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO AMD64 Processors 1 - Bank number 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error Arguments: Arg1: 00000000 Arg2: 80dc794c Arg3: 00000000 Arg4: 00000000
Debugging Details: ------------------
NOTE: This is a hardware error. This error was reported by the CPU via Interrupt 18. This analysis will provide more information about the specific error. Please contact the manufacturer for additional information about this error and troubleshooting assistance.
This error is documented in the following publication:
This error code can be reported back to the manufacturer. They may be able to provide additional information based upon this error. All questions regarding STOP 0x9C should be directed to the hardware manufacturer.
Unloaded modules: 9e8df000 9e949000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 926ac000 926c4000 parport.sys Timestamp: unavailable (00000000) Checksum: 00000000 8aaa6000 8aab3000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 8aab3000 8aabe000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 8aabe000 8aac7000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 8aac7000 8aad8000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 Closing open log file c:debuglog.txt My System SpecsSystem Spec Edit/Delete Message Reply With Quote Multi-Quote This Message System Manufacturer/Model Number homemade OS windows 7 CPU pent 4 ht Motherboard asus p4p800mx Memory 2.5 GB Graphics Card Nvidia GeForce 8400 gs Sound Card sound blaster live 24 bit Monitor(s) Displays dual stone age monitors e772p and e773p
Update your System Spec PSU diablotek da series 400w Case factory modded Dell 2350 Cooling air Hard Drives WD 500 GB sata, WD 56 GB IDE Primary, WD 34 GB IDE Slave jcm2302 View Public Profile Find More Posts by jcm2302 Add jcm2302 to Your Contacts Unread 1 Minute Ago #3 (permalink) jcm2302 New Member
jcm2302 is on a distinguished road
Join Date: Nov 2009 windows 7 3 posts
jcm2302 is online now Add to jcm2302's Reputation Report Post
Default and this
Opened log file 'c:debuglog.txt'
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112709-18812-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers Windows 7 Kernel Version 7100 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7100.0.x86fre.winmain_win7rc.090421-1700 Machine Name: Kernel base = 0x82808000 PsLoadedModuleList = 0x82947570 Debug session time: Fri Nov 27 00:37:26.002 2009 (GMT-5) System Uptime: 0 days 0:48:09.393 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************
Use !analyze -v to get detailed debugging information.
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: c000001d, The exception code that was not handled Arg2: 82876c42, The address that the exception occurred at Arg3: 9d9ada78, Trap Frame Arg4: 00000000
Debugging Details: ------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP: nt!ExfAcquirePushLockShared+7 82876c42 f083ec44 lock sub esp,44h
TRAP_FRAME: 9d9ada78 -- (.trap 0xffffffff9d9ada78) .trap 0xffffffff9d9ada78 ErrCode = 00000000 eax=87040030 ebx=8a3bd364 ecx=8a3bd364 edx=00000000 esi=9d9adb50 edi=00000000 eip=82876c42 esp=9d9adaec ebp=9d9adaec iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!ExfAcquirePushLockShared+0x7: 82876c42 f083ec44 lock sub esp,44h .trap Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: sidebar.exe
CURRENT_IRQL: 0
MISALIGNED_IP: nt!ExfAcquirePushLockShared+7 82876c42 f083ec44 lock sub esp,44h
LAST_CONTROL_TRANSFER: from 8a3ba02e to 82876c42
FAILED_INSTRUCTION_ADDRESS: nt!ExfAcquirePushLockShared+7 82876c42 f083ec44 lock sub esp,44h
Unloaded modules: 9e4f4000 9e55e000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 93f36000 93f4e000 parport.sys Timestamp: unavailable (00000000) Checksum: 00000000 8aaab000 8aab8000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 8aab8000 8aac3000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 8aac3000 8aacc000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 8aacc000 8aadd000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 Closing open log file c:debuglog.txt My System SpecsSystem Spec Edit/Delete Message Reply With Quote Multi-Quote This Message System Manufacturer/Model Number homemade OS windows 7 CPU pent 4 ht Motherboard asus p4p800mx Memory 2.5 GB Graphics Card Nvidia GeForce 8400 gs Sound Card sound blaster live 24 bit Monitor(s) Displays dual stone age monitors e772p and e773p
Update your System Spec PSU diablotek da series 400w Case factory modded Dell 2350 Cooling air Hard Drives WD 500 GB sata, WD 56 GB IDE Primary, WD 34 GB IDE Slave jcm2302 View Public Profile Find More Posts by jcm2302 Add jcm2302 to Your Contacts Unread 1 Minute Ago #4 (permalink) jcm2302 New Member
jcm2302 is on a distinguished road
Join Date: Nov 2009 windows 7 4 posts
jcm2302 is online now Add to jcm2302's Reputation Report Post
Default even this sometimes
Opened log file 'c:debuglog.txt'
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112709-21312-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers Windows 7 Kernel Version 7100 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7100.0.x86fre.winmain_win7rc.090421-1700 Machine Name: Kernel base = 0x8283d000 PsLoadedModuleList = 0x8297c570 Debug session time: Fri Nov 27 09:19:52.006 2009 (GMT-5) System Uptime: 0 days 1:28:39.428 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ......... 0: kd> !analyze -v;r;kv;lmtn;.logclose;q ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************
PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 00000099, A PTE or PFN is corrupt Arg2: 00089140, page frame number Arg3: 00000003, current page state Arg4: 0008c60f, 0
Debugging Details: ------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: sidebar.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 82914500 to 828f8e94
STACK_TEXT: a07267e0 82914500 0000004e 00000099 00089140 nt!KeBugCheckEx+0x1e a07267f8 828dad84 c000b790 00000fff 86b58a68 nt!MiBadShareCount+0x24 a0726838 828daa70 86e65b60 00000200 86f6d090 nt!MiDeletePteList+0x2ba a0726c84 828c2f60 c000b78c 86e65b60 e6c8320c nt!MiDecommitPages+0x38b a0726d1c 8287e35a ffffffff 01f78f00 01f78f14 nt!NtFreeVirtualMemory+0x882 a0726d1c 77078244 ffffffff 01f78f00 01f78f14 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 01f78ed4 00000000 00000000 00000000 00000000 0x77078244
STACK_COMMAND: kb
FOLLOWUP_IP: nt!MiBadShareCount+24 82914500 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiBadShareCount+24
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49ee8b48
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x4E_99_nt!MiBadShareCount+24
BUCKET_ID: 0x4E_99_nt!MiBadShareCount+24
Followup: MachineOwner ---------
eax=8296b934 ebx=848d9e02 ecx=00000018 edx=00000000 esi=8295ed20 edi=00000000 eip=828f8e94 esp=a07267c8 ebp=a07267e0 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000202 nt!KeBugCheckEx+0x1e: 828f8e94 cc int 3 ChildEBP RetAddr Args to Child a07267e0 82914500 0000004e 00000099 00089140 nt!KeBugCheckEx+0x1e a07267f8 828dad84 c000b790 00000fff 86b58a68 nt!MiBadShareCount+0x24 (FPO: [0,0,0]) a0726838 828daa70 86e65b60 00000200 86f6d090 nt!MiDeletePteList+0x2ba a0726c84 828c2f60 c000b78c 86e65b60 e6c8320c nt!MiDecommitPages+0x38b a0726d1c 8287e35a ffffffff 01f78f00 01f78f14 nt!NtFreeVirtualMemory+0x882 a0726d1c 77078244 ffffffff 01f78f00 01f78f14 nt!KiFastCallEntry+0x12a (FPO: [0,3] TrapFrame @ a0726d34) WARNING: Frame IP not in any known module. Following frames may be wrong. 01f78ed4 00000000 00000000 00000000 00000000 0x77078244
Unloaded modules: 9d4a2000 9d4c3000 WUDFRd.sys Timestamp: unavailable (00000000) Checksum: 00000000 93d35000 93d4c000 USBSTOR.SYS Timestamp: unavailable (00000000) Checksum: 00000000 93d2f000 93d35000 RimUsb.sys Timestamp: unavailable (00000000) Checksum: 00000000 9d4c3000 9d52d000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 93f34000 93f4c000 parport.sys Timestamp: unavailable (00000000) Checksum: 00000000 8aa73000 8aa80000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 8aa80000 8aa8b000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 8aa8b000 8aa94000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 8aa94000 8aaa5000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 Closing open log file c:debuglog.txt My System SpecsSystem Spec Edit/Delete Message Reply With Quote Multi-Quote This Message System Manufacturer/Model Number homemade OS windows 7 CPU pent 4 ht Motherboard asus p4p800mx Memory 2.5 GB Graphics Card Nvidia GeForce 8400 gs Sound Card sound blaster live 24 bit Monitor(s) Displays dual stone age monitors e772p and e773p
Update your System Spec PSU diablotek da series 400w Case factory modded Dell 2350 Cooling air Hard Drives WD 500 GB sata, WD 56 GB IDE Primary, WD 34 GB IDE Slave jcm2302 View Public Profile Find More Posts by jcm2302 Add jcm2302 to Your Contacts Unread 1 Minute Ago #5 (permalink) jcm2302 New Member
jcm2302 is on a distinguished road
Join Date: Nov 2009 windows 7 5 posts
jcm2302 is online now Add to jcm2302's Reputation Report Post
Default and this so far
Opened log file 'c:debuglog.txt'
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112609-26937-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers Windows 7 Kernel Version 7100 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7100.0.x86fre.winmain_win7rc.090421-1700 Machine Name: Kernel base = 0x82810000 PsLoadedModuleList = 0x8294f570 Debug session time: Thu Nov 26 23:48:06.587 2009 (GMT-5) System Uptime: 0 days 1:14:21.994 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ............... ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {0, 0, 0, 0}
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+5021c9 )
UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO Arg2: 00000000 Arg3: 00000000 Arg4: 00000000
Debugging Details: ------------------
BUGCHECK_STR: 0x7f_0
TRAP_FRAME: 80d8a7e0 -- (.trap 0xffffffff80d8a7e0) .trap 0xffffffff80d8a7e0 ErrCode = 00000000 eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=86d2f8e0 edi=84fce530 eip=af5161c9 esp=80d8a854 ebp=80d8a85c iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nvlddmkm+0x5021c9: af5161c9 f7f1 div eax,ecx .trap Resetting default scope