Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD after installing Windows7 on a new SSD and an old XP-machine

02 Jan 2012   #31
writhziden

Windows 7 Home Premium 64 Bit
 
 

First step:

Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.


My System SpecsSystem Spec
.
02 Jan 2012   #32
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\120102\Windows_NT6_BSOD_jcgriff2_120102\121311-12807-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a0a000 PsLoadedModuleList = 0xfffff800`01c4f670 Debug session time: Mon Dec 12 16:31:05.795 2011 (UTC - 7:00) System Uptime: 0 days 1:25:04.575 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 4E, {7, 95571, 1, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3824b ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * 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: 0000000000000007, A driver has unlocked a page more times than it locked it Arg2: 0000000000095571, page frame number Arg3: 0000000000000001, current share count Arg4: 0000000000000000, 0 Debugging Details: ------------------ BUGCHECK_STR: 0x4E_7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: MsMpEng.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80001af8140 to fffff80001a86c40 STACK_TEXT: fffff880`0ab3c908 fffff800`01af8140 : 00000000`0000004e 00000000`00000007 00000000`00095571 00000000`00000001 : nt!KeBugCheckEx fffff880`0ab3c910 fffff800`01aae6cf : fffffa80`043fae90 fffff880`0ab3ca80 fffffa80`05561ec8 fffffa80`043fae00 : nt! ?? ::FNODOBFM::`string'+0x3824b fffff880`0ab3c9f0 fffff800`01a9502a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x28b fffff880`0ab3cac0 fffff800`01a84d6e : 00000000`00000000 00000000`00290ff8 00000000`00000001 00000000`752e2828 : nt!MmAccessFault+0x146a fffff880`0ab3cc20 000007fe`ff3a117a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`0296e638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff3a117a STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+3824b fffff800`01af8140 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+3824b FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x4E_7_nt!_??_::FNODOBFM::_string_+3824b BUCKET_ID: X64_0x4E_7_nt!_??_::FNODOBFM::_string_+3824b Followup: MachineOwner ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\120102\Windows_NT6_BSOD_jcgriff2_120102\121311-12807-02.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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a09000 PsLoadedModuleList = 0xfffff800`01c4e670 Debug session time: Mon Dec 12 18:04:22.069 2011 (UTC - 7:00) System Uptime: 0 days 1:31:33.725 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80001a8fa8e, fffff8800c6e9100, 0} Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+c4 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80001a8fa8e, Address of the instruction which caused the bugcheck Arg3: fffff8800c6e9100, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. 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!ObfDereferenceObject+6e fffff800`01a8fa8e 6683b8c601000000 cmp word ptr [rax+1C6h],0 CONTEXT: fffff8800c6e9100 -- (.cxr 0xfffff8800c6e9100) rax=0000000100001f80 rbx=0000000000000000 rcx=fffff8a00c92fe30 rdx=fffff8a00c92fe30 rsi=fffff8a00c92fe30 rdi=fffff8a00c92fe00 rip=fffff80001a8fa8e rsp=fffff8800c6e9ae0 rbp=fffffa80059acb30 r8=0000000000000000 r9=0000000000000001 r10=0000000000000214 r11=fffff8800c6e9ab0 r12=fffff8a00c92fe00 r13=fffffa80059acb30 r14=0000000002c4ee00 r15=fffff8a002806920 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 nt!ObfDereferenceObject+0x6e: fffff800`01a8fa8e 6683b8c601000000 cmp word ptr [rax+1C6h],0 ds:002b:00000001`00002146=???? Resetting default scope CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: sidebar.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80001d7cf44 to fffff80001a8fa8e STACK_TEXT: fffff880`0c6e9ae0 fffff800`01d7cf44 : fffffa80`059acb30 00000000`00000000 fffffa80`05abfb60 00000000`00000000 : nt!ObfDereferenceObject+0x6e fffff880`0c6e9b40 fffff800`01d7d4f4 : 00000000`00000214 fffffa80`059acb30 fffff8a0`02806920 00000000`00000214 : nt!ObpCloseHandleTableEntry+0xc4 fffff880`0c6e9bd0 fffff800`01a84ed3 : fffffa80`05abfb60 fffff880`0c6e9ca0 00000000`7efa4000 00000000`00000004 : nt!ObpCloseHandle+0x94 fffff880`0c6e9c20 00000000`77bd140a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`02c4e4f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bd140a FOLLOWUP_IP: nt!ObpCloseHandleTableEntry+c4 fffff800`01d7cf44 33c0 xor eax,eax SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!ObpCloseHandleTableEntry+c4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 STACK_COMMAND: .cxr 0xfffff8800c6e9100 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!ObpCloseHandleTableEntry+c4 BUCKET_ID: X64_0x3B_nt!ObpCloseHandleTableEntry+c4 Followup: MachineOwner ---------
  3. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\120102\Windows_NT6_BSOD_jcgriff2_120102\121511-42666-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a17000 PsLoadedModuleList = 0xfffff800`01c5c670 Debug session time: Wed Dec 14 23:37:27.836 2011 (UTC - 7:00) System Uptime: 0 days 17:53:28.601 Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {80000003, fffff88001139730, fffff8800b1bedc0, 0} Probably caused by : fileinfo.sys ( fileinfo!FltGetStreamContext+6 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 0000000080000003, Exception code that caused the bugcheck Arg2: fffff88001139730, Address of the instruction which caused the bugcheck Arg3: fffff8800b1bedc0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid FAULTING_IP: fileinfo!FltGetStreamContext+6 fffff880`01139730 cc int 3 CONTEXT: fffff8800b1bedc0 -- (.cxr 0xfffff8800b1bedc0) rax=0000000000000000 rbx=fffffa8006302f20 rcx=fffffa80041f5bb0 rdx=fffffa8006302f20 rsi=fffffa8007c7e1e0 rdi=0000000000000000 rip=fffff88001139730 rsp=fffff8800b1bf7a8 rbp=fffff8800b1bf850 r8=fffff8800b1bf838 r9=0000000000000000 r10=fffffffffffffe36 r11=fffff8800b1bf8c8 r12=0000000000000000 r13=fffffa8007c7e1e0 r14=fffff8800b1bf8d8 r15=fffff8800b1bfa40 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000246 fileinfo!FltGetStreamContext+0x6: fffff880`01139730 cc int 3 Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: msiexec.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88001139730 STACK_TEXT: fffff880`0b1bf7a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fileinfo!FltGetStreamContext+0x6 FOLLOWUP_IP: fileinfo!FltGetStreamContext+6 fffff880`01139730 cc int 3 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: fileinfo!FltGetStreamContext+6 FOLLOWUP_NAME: MachineOwner MODULE_NAME: fileinfo IMAGE_NAME: fileinfo.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc481 STACK_COMMAND: .cxr 0xfffff8800b1bedc0 ; kb FAILURE_BUCKET_ID: X64_0x3B_fileinfo!FltGetStreamContext+6 BUCKET_ID: X64_0x3B_fileinfo!FltGetStreamContext+6 Followup: MachineOwner ---------
  4. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\120102\Windows_NT6_BSOD_jcgriff2_120102\121511-13197-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a0b000 PsLoadedModuleList = 0xfffff800`01c50670 Debug session time: Thu Dec 15 12:00:53.237 2011 (UTC - 7:00) System Uptime: 0 days 9:46:06.018 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050031, 6f8, 691fb75c} Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000006f8 Arg4: 00000000691fb75c Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: firefox.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80001a871e9 to fffff80001a87c40 STACK_TEXT: fffff800`03449d28 fffff800`01a871e9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx fffff800`03449d30 fffff800`01a856b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff800`03449e70 00000000`691fb75c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 00000000`0040ca18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x691fb75c STACK_COMMAND: kb FOLLOWUP_IP: nt!KiDoubleFaultAbort+b2 fffff800`01a856b2 90 nop SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiDoubleFaultAbort+b2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 Followup: MachineOwner ---------
  5. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\120102\Windows_NT6_BSOD_jcgriff2_120102\121711-14305-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a0f000 PsLoadedModuleList = 0xfffff800`01c54670 Debug session time: Sat Dec 17 02:15:18.784 2011 (UTC - 7:00) System Uptime: 1 days 12:35:17.565 Loading Kernel Symbols ............................................................... ................................................................ ......................... Loading User Symbols Loading unloaded module list .......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {403, fffff68000010cc0, 1e00000cb546025, fffff68000059400} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+330bc ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000000403, The subtype of the bugcheck. Arg2: fffff68000010cc0 Arg3: 01e00000cb546025 Arg4: fffff68000059400 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_403 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: MCULauncher.ex CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80001a333f6 to fffff80001a8bc40 STACK_TEXT: fffff880`0d848678 fffff800`01a333f6 : 00000000`0000001a 00000000`00000403 fffff680`00010cc0 01e00000`cb546025 : nt!KeBugCheckEx fffff880`0d848680 fffff800`01abdbb7 : 00000000`00000000 fffff680`00010da8 fffffa80`05e2e060 fffff800`01abfca4 : nt! ?? ::FNODOBFM::`string'+0x330bc fffff880`0d848830 fffff800`01abf569 : 00000000`00000000 00000000`021b6fff fffffa80`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f fffff880`0d8489f0 fffff800`01da3221 : fffffa80`0546aa90 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9 fffff880`0d848b10 fffff800`01da3623 : 00000000`00000000 00000000`02180000 fffffa80`00000001 fffffa80`0603fa20 : nt!MiUnmapViewOfSection+0x1b1 fffff880`0d848bd0 fffff800`01a8aed3 : ffffffff`ffffffff 00000000`0008e320 fffffa80`05e2e060 00000000`00008000 : nt!NtUnmapViewOfSection+0x5f fffff880`0d848c20 00000000`774915ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0008e318 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774915ba STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+330bc fffff800`01a333f6 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+330bc FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x1a_403_nt!_??_::FNODOBFM::_string_+330bc BUCKET_ID: X64_0x1a_403_nt!_??_::FNODOBFM::_string_+330bc Followup: MachineOwner ---------
  6. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\120102\Windows_NT6_BSOD_jcgriff2_120102\121711-11809-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a4d000 PsLoadedModuleList = 0xfffff800`01c92670 Debug session time: Sat Dec 17 06:54:53.582 2011 (UTC - 7:00) System Uptime: 0 days 4:38:45.222 Loading Kernel Symbols ............................................................... ................................................................ ......................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffff80001ac1b65, 0, ffffffffffffffff} Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) 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. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff80001ac1b65, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: ffffffffffffffff, Parameter 1 of the exception 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!ExpInterlockedPopEntrySListFault16+0 fffff800`01ac1b65 498b08 mov rcx,qword ptr [r8] EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001cfc100 ffffffffffffffff ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. BUGCHECK_STR: 0x1E_c0000005 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: ZoomBrowser.ex CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80001b15588 to fffff80001ac9c40 STACK_TEXT: fffff880`0a97d098 fffff800`01b15588 : 00000000`0000001e ffffffff`c0000005 fffff800`01ac1b65 00000000`00000000 : nt!KeBugCheckEx fffff880`0a97d0a0 fffff800`01ac92c2 : fffff880`0a97d878 00000000`00000000 fffff880`0a97d920 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4977d fffff880`0a97d740 fffff800`01ac7bca : fffffa80`01081ad0 fffff800`01aeffc0 00000000`00000000 fffff6fb`82200708 : nt!KiExceptionDispatch+0xc2 fffff880`0a97d920 fffff800`01ac1b65 : 00000000`00000000 fffff800`01ad759c 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a fffff880`0a97dab0 fffff800`01ad759c : 00000000`00000000 00000000`00000000 fffff700`01080000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16 fffff880`0a97dac0 fffff800`01ac7d6e : 00000000`00000001 00000000`3836f000 00000000`00000001 00000000`07e1f560 : nt!MmAccessFault+0x9dc fffff880`0a97dc20 00000000`04a1af9d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`07e1f458 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x4a1af9d STACK_COMMAND: kb FOLLOWUP_IP: nt!ExpInterlockedPopEntrySListFault16+0 fffff800`01ac1b65 498b08 mov rcx,qword ptr [r8] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nt!ExpInterlockedPopEntrySListFault16+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!ExpInterlockedPopEntrySListFault16+0 BUCKET_ID: X64_0x1E_c0000005_nt!ExpInterlockedPopEntrySListFault16+0 Followup: MachineOwner ---------
  7. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\120102\Windows_NT6_BSOD_jcgriff2_120102\121811-12698-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a5b000 PsLoadedModuleList = 0xfffff800`01ca0670 Debug session time: Sun Dec 18 07:01:48.798 2011 (UTC - 7:00) System Uptime: 0 days 16:21:49.348 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list .................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41287, ac0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46485 ) Followup: MachineOwner --------- 1: 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: 0000000000000ac0 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41287 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: ZoomBrowser.ex CURRENT_IRQL: 0 TRAP_FRAME: fffff8800c7e8920 -- (.trap 0xfffff8800c7e8920) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000425ca0005 rbx=0000000000000000 rcx=fffffa80039016e0 rdx=0000000000000ac1 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80001acfb65 rsp=fffff8800c7e8ab0 rbp=fffff8800c7e8b40 r8=0000000000000ac0 r9=0000000000000000 r10=fffffa80039016e0 r11=fffff8800c7e8c20 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!ExpInterlockedPopEntrySListFault16: fffff800`01acfb65 498b08 mov rcx,qword ptr [r8] ds:8010:00000000`00000ac0=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80001a6ad7e to fffff80001ad7c40 STACK_TEXT: fffff880`0c7e87b8 fffff800`01a6ad7e : 00000000`0000001a 00000000`00041287 00000000`00000ac0 00000000`00000000 : nt!KeBugCheckEx fffff880`0c7e87c0 fffff800`01ad5d6e : 00000000`00000000 00000000`00000ac0 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x46485 fffff880`0c7e8920 fffff800`01acfb65 : 00000000`00000000 fffff800`01ae559c 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e fffff880`0c7e8ab0 fffff800`01ae559c : 00000000`00000000 00000000`00000000 fffff700`01080000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16 fffff880`0c7e8ac0 fffff800`01ad5d6e : 00000000`00000001 00000000`0a7bb000 00000000`00000001 00000000`07e1f580 : nt!MmAccessFault+0x9dc fffff880`0c7e8c20 00000000`04b4af9d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`07e1f478 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x4b4af9d STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+46485 fffff800`01a6ad7e cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+46485 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46485 BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46485 Followup: MachineOwner ---------
  8. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\120102\Windows_NT6_BSOD_jcgriff2_120102\121911-11871-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a50000 PsLoadedModuleList = 0xfffff800`01c95670 Debug session time: Mon Dec 19 00:00:42.009 2011 (UTC - 7:00) System Uptime: 0 days 0:12:06.790 Loading Kernel Symbols ............................................................... ................................................................ ......................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41287, 80, 0, 0} Probably caused by : win32k.sys ( win32k!memcpy+bd ) 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: 0000000000000080 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41287 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: sidebar.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800c37ca40 -- (.trap 0xfffff8800c37ca40) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffb0b5b2ffa9adac rbx=0000000000000000 rcx=0000000002765020 rdx=fffff900bf9e8764 rsi=0000000000000000 rdi=0000000000000000 rip=fffff960000c4ccd rsp=fffff8800c37cbd8 rbp=fffff8800c37ccb0 r8=00000000000001fc r9=000000000000000a r10=ffbec3c2ffb8bdbb r11=0000000002764f60 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc win32k!memcpy+0xbd: fffff960`000c4ccd 488941e0 mov qword ptr [rcx-20h],rax ds:2418:00000000`02765000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80001a5fd7e to fffff80001accc40 STACK_TEXT: fffff880`0c37c5d8 fffff800`01a5fd7e : 00000000`0000001a 00000000`00041287 00000000`00000080 00000000`00000000 : nt!KeBugCheckEx fffff880`0c37c5e0 fffff800`01acad6e : 00000000`00000000 00000000`00000080 fffffa80`059b7f00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x46485 fffff880`0c37c740 fffff800`01ac4b65 : 00000000`00000000 fffff800`01ada59c 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e fffff880`0c37c8d0 fffff800`01ada59c : 00000000`00000000 00000000`00000000 fffff700`01080000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16 fffff880`0c37c8e0 fffff800`01acad6e : 00000000`00000001 00000000`02765000 00000000`00000000 fffff900`c214d6c4 : nt!MmAccessFault+0x9dc fffff880`0c37ca40 fffff960`000c4ccd : fffff960`0008c6c9 fffff880`015d2128 00000000`00000000 00000000`0000099c : nt!KiPageFault+0x16e fffff880`0c37cbd8 fffff960`0008c6c9 : fffff880`015d2128 00000000`00000000 00000000`0000099c fffff880`015db6e4 : win32k!memcpy+0xbd fffff880`0c37cbe0 fffff960`000867f8 : 00000000`00000001 fffff880`0c37d2f8 00000000`00000000 fffff880`0c37d044 : win32k!vSrcCopyS32D32Identity+0x71 fffff880`0c37cc10 fffff960`001f9683 : fffff900`c1ef0cd8 fffff900`c2143018 fffff880`0c37d040 fffff900`c1ef53d0 : win32k!EngCopyBits+0x908 fffff880`0c37cf20 fffff960`001e9a64 : fffff900`c00bf010 00000000`00000001 00000000`00000001 fffff900`c0088740 : win32k!BLTRECORD::bBitBlt+0x697 fffff880`0c37d110 fffff960`001fc668 : fffffa80`058a7b30 fffffa80`058a7e00 00000000`00000000 fffff960`000c6ffb : win32k!GreStretchBltInternal+0xa14 fffff880`0c37d3b0 fffff800`01acbed3 : ffffffff`b2050c5f 00000000`0185000f fffff900`c3076390 00000000`52050c86 : win32k!NtGdiStretchBlt+0x68 fffff880`0c37d430 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 STACK_COMMAND: kb FOLLOWUP_IP: win32k!memcpy+bd fffff960`000c4ccd 488941e0 mov qword ptr [rcx-20h],rax SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: win32k!memcpy+bd FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ecdcd5a FAILURE_BUCKET_ID: X64_0x1a_41287_win32k!memcpy+bd BUCKET_ID: X64_0x1a_41287_win32k!memcpy+bd Followup: MachineOwner ---------
  9. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\120102\Windows_NT6_BSOD_jcgriff2_120102\122211-11965-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a68000 PsLoadedModuleList = 0xfffff800`01cad670 Debug session time: Wed Dec 21 16:11:47.117 2011 (UTC - 7:00) System Uptime: 1 days 0:04:45.773 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list ........... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {8, 6, a, fffffa8004ca4000} ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: usbport!_DEVICE_EXTENSION *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: usbhub!_DEVICE_EXTENSION_HUB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: usbhub!_DEVICE_EXTENSION_HUB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: usbhub!_DEVICE_EXTENSION_HUB *** *** *** ************************************************************************* Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BUGCODE_USB_DRIVER (fe) USB Driver bugcheck, first parameter is USB bugcheck code. Arguments: Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT Arg3: 000000000000000a, TimeoutCode Arg4: fffffa8004ca4000 Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: usbport!_DEVICE_EXTENSION *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: usbhub!_DEVICE_EXTENSION_HUB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: usbhub!_DEVICE_EXTENSION_HUB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: usbhub!_DEVICE_EXTENSION_HUB *** *** *** ************************************************************************* CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xFE PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff880062e6a60 to fffff80001ae4c40 STACK_TEXT: fffff880`0acc2c18 fffff880`062e6a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`0000000a : nt!KeBugCheckEx fffff880`0acc2c20 fffff800`01ddb9e3 : fffffa80`049f3050 00000000`00000001 ffffffff`dc3a58a0 fffff800`01c852b8 : usbhub!UsbhHubProcessChangeWorker+0xec fffff880`0acc2c80 fffff800`01aef001 : fffff800`01c85200 fffff800`01ddb901 fffffa80`062e1700 00000000`00000000 : nt!IopProcessWorkItem+0x23 fffff880`0acc2cb0 fffff800`01d7ffee : 00000030`485fcd81 fffffa80`062e17b0 00000000`00000080 fffffa80`03a32890 : nt!ExpWorkerThread+0x111 fffff880`0acc2d40 fffff800`01ad65e6 : fffff800`01c5ae80 fffffa80`062e17b0 fffffa80`03a3eb60 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`0acc2d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: usbhub!UsbhHubProcessChangeWorker+ec fffff880`062e6a60 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: usbhub!UsbhHubProcessChangeWorker+ec FOLLOWUP_NAME: MachineOwner MODULE_NAME: usbhub IMAGE_NAME: usbhub.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c15 FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec Followup: MachineOwner ---------
  10. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\120102\Windows_NT6_BSOD_jcgriff2_120102\122211-12729-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a14000 PsLoadedModuleList = 0xfffff800`01c59670 Debug session time: Thu Dec 22 10:07:29.010 2011 (UTC - 7:00) System Uptime: 0 days 17:53:35.790 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41287, 11c0a38c0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46485 ) Followup: MachineOwner --------- 1: 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: 000000011c0a38c0 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41287 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: sidebar.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88009bef1a0 -- (.trap 0xfffff88009bef1a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000047b840004 rbx=0000000000000000 rcx=fffffa80039014e0 rdx=000000011c0a38c1 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80001a88b65 rsp=fffff88009bef330 rbp=fffff88009bef3c0 r8=000000011c0a38c0 r9=0000000000000000 r10=fffffa80039014e0 r11=fffff88009bef4a0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!ExpInterlockedPopEntrySListFault16: fffff800`01a88b65 498b08 mov rcx,qword ptr [r8] ds:dae0:00000001`1c0a38c0=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80001a23d7e to fffff80001a90c40 STACK_TEXT: fffff880`09bef038 fffff800`01a23d7e : 00000000`0000001a 00000000`00041287 00000001`1c0a38c0 00000000`00000000 : nt!KeBugCheckEx fffff880`09bef040 fffff800`01a8ed6e : 00000000`00000000 00000001`1c0a38c0 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x46485 fffff880`09bef1a0 fffff800`01a88b65 : 00000000`00000000 fffff800`01a9e59c 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e fffff880`09bef330 fffff800`01a9e59c : 00000000`00000000 00000000`00000000 fffff700`01080000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16 fffff880`09bef340 fffff800`01a8ed6e : 00000000`00000001 00000000`027be000 00000000`0286c901 00000000`02460000 : nt!MmAccessFault+0x9dc fffff880`09bef4a0 00000000`00ae3802 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`02d3b94c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xae3802 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+46485 fffff800`01a23d7e cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+46485 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46485 BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46485 Followup: MachineOwner ---------
  11. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\120102\Windows_NT6_BSOD_jcgriff2_120102\122411-19515-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a61000 PsLoadedModuleList = 0xfffff800`01ca6670 Debug session time: Sat Dec 24 13:00:44.250 2011 (UTC - 7:00) System Uptime: 0 days 10:52:19.031 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050031, 6f8, fffff88000e4ea26} Probably caused by : partmgr.sys ( partmgr!PmWmiCounterIoComplete+26 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000006f8 Arg4: fffff88000e4ea26 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80001add1e9 to fffff80001addc40 STACK_TEXT: fffff880`009b7c68 fffff800`01add1e9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx fffff880`009b7c70 fffff800`01adb6b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`009b7db0 fffff880`00e4ea26 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 00000000`00000020 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : partmgr!PmWmiCounterIoComplete+0x26 STACK_COMMAND: kb FOLLOWUP_IP: partmgr!PmWmiCounterIoComplete+26 fffff880`00e4ea26 ff157c280000 call qword ptr [partmgr!_imp_KeQueryPerformanceCounter (fffff880`00e512a8)] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: partmgr!PmWmiCounterIoComplete+26 FOLLOWUP_NAME: MachineOwner MODULE_NAME: partmgr IMAGE_NAME: partmgr.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce792c0 FAILURE_BUCKET_ID: X64_0x7f_8_partmgr!PmWmiCounterIoComplete+26 BUCKET_ID: X64_0x7f_8_partmgr!PmWmiCounterIoComplete+26 Followup: MachineOwner ---------
  12. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\120102\Windows_NT6_BSOD_jcgriff2_120102\122711-12792-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a49000 PsLoadedModuleList = 0xfffff800`01c8e670 Debug session time: Mon Dec 26 18:24:28.037 2011 (UTC - 7:00) System Uptime: 0 days 14:57:28.818 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904fb, fffff8800bde7878, fffff8800bde70d0, fffff880012ec038} Probably caused by : Ntfs.sys ( Ntfs!TxfOpenFileProcessing+158 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 00000000001904fb Arg2: fffff8800bde7878 Arg3: fffff8800bde70d0 Arg4: fffff880012ec038 Debugging Details: ------------------ EXCEPTION_RECORD: fffff8800bde7878 -- (.exr 0xfffff8800bde7878) ExceptionAddress: fffff880012ec038 (Ntfs!TxfOpenFileProcessing+0x0000000000000158) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000002a20 Attempt to read from address 0000000000002a20 CONTEXT: fffff8800bde70d0 -- (.cxr 0xfffff8800bde70d0) rax=fffff8a00abbec48 rbx=0000000000002a20 rcx=0000000000000004 rdx=0000000000000000 rsi=fffff8a00abbec70 rdi=0000000000000000 rip=fffff880012ec038 rsp=fffff8800bde7ab0 rbp=0000000000000000 r8=fffff8a00abbec70 r9=fffff8a00abbeed8 r10=fffff8a000267000 r11=0000000000000000 r12=fffff8a00abbeb40 r13=0000000000000000 r14=fffffa8005d486c0 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 Ntfs!TxfOpenFileProcessing+0x158: fffff880`012ec038 803b00 cmp byte ptr [rbx],0 ds:002b:00000000`00002a20=?? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: rundll32.exe CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000002a20 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001cf8100 0000000000002a20 FOLLOWUP_IP: Ntfs!TxfOpenFileProcessing+158 fffff880`012ec038 803b00 cmp byte ptr [rbx],0 FAULTING_IP: Ntfs!TxfOpenFileProcessing+158 fffff880`012ec038 803b00 cmp byte ptr [rbx],0 BUGCHECK_STR: 0x24 LAST_CONTROL_TRANSFER: from fffff880012e8167 to fffff880012ec038 STACK_TEXT: fffff880`0bde7ab0 fffff880`012e8167 : fffff980`19200200 fffff8a0`0abbeb40 fffff980`19200398 fffff8a0`0abbeed8 : Ntfs!TxfOpenFileProcessing+0x158 fffff880`0bde7bd0 fffff880`012d6fe5 : fffffa80`05d486c0 fffffa80`059b4ae0 fffffa80`040cb180 fffff8a0`0abbeed8 : Ntfs!NtfsOpenAttribute+0x127 fffff880`0bde7ce0 fffff880`012d2e3b : fffff880`0bde84a0 fffffa80`05d486c0 fffff8a0`0abbeed8 fffff8a0`0000003a : Ntfs!NtfsOpenExistingAttr+0x145 fffff880`0bde7da0 fffff880`012d609f : fffffa80`05d486c0 fffffa80`059b47d0 fffff8a0`0abbeed8 fffff880`0000003a : Ntfs!NtfsOpenAttributeInExistingFile+0x5ab fffff880`0bde7f30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsOpenExistingPrefixFcb+0x1ef SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: Ntfs!TxfOpenFileProcessing+158 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d79997b STACK_COMMAND: .cxr 0xfffff8800bde70d0 ; kb FAILURE_BUCKET_ID: X64_0x24_Ntfs!TxfOpenFileProcessing+158 BUCKET_ID: X64_0x24_Ntfs!TxfOpenFileProcessing+158 Followup: MachineOwner ---------
  13. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\120102\Windows_NT6_BSOD_jcgriff2_120102\123111-11840-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a07000 PsLoadedModuleList = 0xfffff800`01c4c670 Debug session time: Sat Dec 31 14:54:00.841 2011 (UTC - 7:00) System Uptime: 1 days 9:01:37.621 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffffffffffffff8, 2, 0, fffff80001a8fad1} Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+171 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) 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 a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffffffffffffff8, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80001a8fad1, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001cb6100 fffffffffffffff8 CURRENT_IRQL: 2 FAULTING_IP: nt!KiInsertTimerTable+171 fffff800`01a8fad1 4c3b7df8 cmp r15,qword ptr [rbp-8] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: TOTALCMD.EXE TRAP_FRAME: fffff8800c36af50 -- (.trap 0xfffff8800c36af50) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000009858 rbx=0000000000000000 rcx=00000114d488f57f rdx=fffffa80054519f0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80001a8fad1 rsp=fffff8800c36b0e0 rbp=0000000000000000 r8=ffffffffffffffff r9=00000000000000dc r10=fffff80001bf9e80 r11=fffffa8003ef6c00 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe cy nt!KiInsertTimerTable+0x171: fffff800`01a8fad1 4c3b7df8 cmp r15,qword ptr [rbp-8] ss:0018:ffffffff`fffffff8=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80001a831e9 to fffff80001a83c40 STACK_TEXT: fffff880`0c36ae08 fffff800`01a831e9 : 00000000`0000000a ffffffff`fffffff8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0c36ae10 fffff800`01a81e60 : 00000000`00000000 00000000`00000000 00000000`00001f80 fffffa80`03ef6c20 : nt!KiBugCheckDispatch+0x69 fffff880`0c36af50 fffff800`01a8fad1 : 00000000`00000000 00000000`00000000 00000008`00000001 fffff880`009b1180 : nt!KiPageFault+0x260 fffff880`0c36b0e0 fffff800`01a89092 : fffffa80`03ef6b60 fffffa80`03ef6b60 fffff880`00000000 fffff800`00000000 : nt!KiInsertTimerTable+0x171 fffff880`0c36b140 fffff800`01a8844a : 00000000`00000000 00000000`00000000 00000000`000000dc 00000000`00000000 : nt!KiCommitThreadWait+0x332 fffff880`0c36b1d0 fffff800`01d7a77f : fffff880`00000003 fffff880`0c36b520 00000000`00000001 fffffa80`00000006 : nt!KeWaitForMultipleObjects+0x272 fffff880`0c36b490 fffff800`01da74cd : fffff880`009b1101 fffff800`01a868a4 000111f5`00000001 00000000`00000000 : nt!ObpWaitForMultipleObjects+0x294 fffff880`0c36b960 fffff800`01a82ed3 : fffff880`0c36bca0 fffff800`01a8d85a 00000000`0000002a 00000000`74982450 : nt!NtWaitForMultipleObjects32+0xec fffff880`0c36bbb0 00000000`74982e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0329f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74982e09 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiInsertTimerTable+171 fffff800`01a8fad1 4c3b7df8 cmp r15,qword ptr [rbp-8] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KiInsertTimerTable+171 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+171 BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+171 Followup: MachineOwner ---------
I know you already ran Memtest and found no errors, but Memtest sometimes misses memory problems associated with Windows. Please also run the extended version of the Windows Memory Diagnostics Tool for at least five passes. You may want to run this overnight since it takes a long time to finish.
My System SpecsSystem Spec
03 Jan 2012   #33
YamYam

Windows 7
 
 

OK.
I removed Daemon Tools.
Ran the extended version of the Windows Memory Diagnostics Tool 3 (!) times, this took me more than 6 hours; no failures. Will start tonight for another 3 runs.
I will keep you informed.

YamYam
My System SpecsSystem Spec
.

03 Jan 2012   #34
writhziden

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by YamYam View Post
OK.
I removed Daemon Tools.
Ran the extended version of the Windows Memory Diagnostics Tool 3 (!) times, this took me more than 6 hours; no failures. Will start tonight for another 3 runs.
I will keep you informed.

YamYam
Sounds good. Best wishes!
My System SpecsSystem Spec
08 Jan 2012   #35
YamYam

Windows 7
 
 

The results :
- 7x Windows Memory Diagnostics Tool : no problems
- 2x 5 times Memtest 86+ : no problems
Several days no BSOD's until the 6th. of January.
The minidump is enclosed.
I will try the suggestions until next Friday the 13th ().

Then I will reinstall Windows 7, now the 32 bit version. If the BSOD keep coming, I have to consider to return to Windows XP.


Attached Files
File Type: rar _minidumps.rar (138.9 KB, 2 views)
My System SpecsSystem Spec
08 Jan 2012   #36
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\010612-15256-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a56000 PsLoadedModuleList = 0xfffff800`01c9b670 Debug session time: Fri Jan 6 10:03:29.821 2012 (UTC - 7:00) System Uptime: 0 days 7:22:30.602 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41287, 129af9, 0, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46485 ) 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: 0000000000129af9 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41287 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: firefox.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff880086a6830 -- (.trap 0xfffff880086a6830) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000003208b0004 rbx=0000000000000000 rcx=fffffa8003901790 rdx=0000000000129afa rsi=0000000000000000 rdi=0000000000000000 rip=fffff80001acab65 rsp=fffff880086a69c0 rbp=fffff880086a6a40 r8=0000000000129af9 r9=fffff680000a77e0 r10=fffffa8003901790 r11=fffff880086a6c20 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!ExpInterlockedPopEntrySListFault16: fffff800`01acab65 498b08 mov rcx,qword ptr [r8] ds:77e0:00000000`00129af9=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80001a65d7e to fffff80001ad2c40 STACK_TEXT: fffff880`086a66c8 fffff800`01a65d7e : 00000000`0000001a 00000000`00041287 00000000`00129af9 00000000`00000000 : nt!KeBugCheckEx fffff880`086a66d0 fffff800`01ad0d6e : 00000000`00000000 00000000`00129af9 fffffa80`0422e000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x46485 fffff880`086a6830 fffff800`01acab65 : 00000000`00000002 fffff800`01ae344d 00000000`00000004 00000000`00000000 : nt!KiPageFault+0x16e fffff880`086a69c0 fffff800`01ae344d : 00000000`00000004 00000000`00000000 fffffa80`0580db60 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16 fffff880`086a69d0 fffff800`01ae019e : 00000000`00000001 00000000`14efc000 fffff880`086a6c20 fffff680`000a77e0 : nt!MiResolveDemandZeroFault+0x14d fffff880`086a6ac0 fffff800`01ad0d6e : 00000000`00000001 00000000`14efc000 00000000`00000001 00000000`00000030 : nt!MmAccessFault+0x5de fffff880`086a6c20 00000000`6fe91725 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`002aad98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6fe91725 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+46485 fffff800`01a65d7e cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+46485 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46485 BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46485 Followup: MachineOwner ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\010612-14367-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a4e000 PsLoadedModuleList = 0xfffff800`01c93670 Debug session time: Fri Jan 6 15:47:56.382 2012 (UTC - 7:00) System Uptime: 0 days 0:00:51.163 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80001d9d399, fffff8800a17ba30, 0} Probably caused by : ntkrnlmp.exe ( nt!CmpGetNameControlBlock+12e ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80001d9d399, Address of the instruction which caused the bugcheck Arg3: fffff8800a17ba30, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. 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!CmpGetNameControlBlock+12e fffff800`01d9d399 3b3e cmp edi,dword ptr [rsi] CONTEXT: fffff8800a17ba30 -- (.cxr 0xfffff8800a17ba30) rax=fffff8a000011000 rbx=0000000000000000 rcx=fffff8a0000184a0 rdx=0000000000f9ce9e rsi=006f0043002e006d rdi=00000000b0cb7e02 rip=fffff80001d9d399 rsp=fffff8800a17c410 rbp=fffff8800a17c4a8 r8=0000000000000039 r9=00000000000000ff r10=0000000000000030 r11=fffff8a004825d94 r12=fffff8a000011000 r13=00000000000074a0 r14=0000000001d33040 r15=fffff8a0027ffa01 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 nt!CmpGetNameControlBlock+0x12e: fffff800`01d9d399 3b3e cmp edi,dword ptr [rsi] ds:002b:006f0043`002e006d=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: TrustedInstall CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80001d9d399 STACK_TEXT: fffff880`0a17c410 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpGetNameControlBlock+0x12e FOLLOWUP_IP: nt!CmpGetNameControlBlock+12e fffff800`01d9d399 3b3e cmp edi,dword ptr [rsi] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!CmpGetNameControlBlock+12e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 STACK_COMMAND: .cxr 0xfffff8800a17ba30 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!CmpGetNameControlBlock+12e BUCKET_ID: X64_0x3B_nt!CmpGetNameControlBlock+12e Followup: MachineOwner ---------
  3. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\010612-14352-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a10000 PsLoadedModuleList = 0xfffff800`01c55670 Debug session time: Fri Jan 6 02:39:15.934 2012 (UTC - 7:00) System Uptime: 0 days 0:02:08.715 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff900c20f1000, 1, fffff960000623f4, 0} Could not read faulting driver name Probably caused by : win32k.sys ( win32k!sfac_GetLongGlyphIDs+84 ) Followup: MachineOwner --------- 1: 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: fffff900c20f1000, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff960000623f4, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001cbf100 fffff900c20f1000 FAULTING_IP: win32k!sfac_GetLongGlyphIDs+84 fffff960`000623f4 44891e mov dword ptr [rsi],r11d MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: csrss.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88009fbfc80 -- (.trap 0xfffff88009fbfc80) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000063e2316 rbx=0000000000000000 rcx=000000000000000e rdx=0000000000002316 rsi=0000000000000000 rdi=0000000000000000 rip=fffff960000623f4 rsp=fffff88009fbfe10 rbp=00000000000098f4 r8=0000000000002316 r9=00000000063d7484 r10=00000000000098f4 r11=0000000000002316 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc win32k!sfac_GetLongGlyphIDs+0x84: fffff960`000623f4 44891e mov dword ptr [rsi],r11d ds:00000000`00000000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80001a389fc to fffff80001a8cc40 STACK_TEXT: fffff880`09fbfb18 fffff800`01a389fc : 00000000`00000050 fffff900`c20f1000 00000000`00000001 fffff880`09fbfc80 : nt!KeBugCheckEx fffff880`09fbfb20 fffff800`01a8ad6e : 00000000`00000001 fffff900`c20f1000 ffff0800`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4611f fffff880`09fbfc80 fffff960`000623f4 : 00000000`00000001 fffff900`c20f1000 00000000`0000ffff fffff960`00061d18 : nt!KiPageFault+0x16e fffff880`09fbfe10 fffff960`0006233b : fffff960`00062794 00000000`000098ed 00000000`00005d86 00000000`00000008 : win32k!sfac_GetLongGlyphIDs+0x84 fffff880`09fbfe60 fffff960`0006226a : 00000000`063c5e54 00000000`00000008 00000000`000216d0 00000000`000216d0 : win32k!sfac_GetWinNTGlyphIDs+0xbb fffff880`09fbfed0 fffff960`0006213e : 00000000`00000000 00000000`00000000 fffff880`09fc0060 00000000`000216f0 : win32k!fs_WinNTGetGlyphIDs+0x6a fffff880`09fbff20 fffff960`00061e9a : 00000000`063d545a fffff880`09fc0060 00000000`000098f4 00000000`063c98ed : win32k!cjComputeGLYPHSET_MSFT_UNICODE+0x252 fffff880`09fbffe0 fffff960`000591b3 : fffff900`c00b11a0 00000000`00000003 00000000`00000001 00000000`00000000 : win32k!bLoadGlyphSet+0x13a fffff880`09fc0010 fffff960`00059352 : fffff900`c00b11a0 fffff900`00000001 fffff900`c00b11a0 fffff960`001ca734 : win32k!bReloadGlyphSet+0x24b fffff880`09fc06d0 fffff960`000592aa : 00000000`00000000 fffff900`c00b11a0 fffff900`00000001 fffff900`c074e844 : win32k!ttfdQueryFontTree+0x66 fffff880`09fc0720 fffff960`000a567b : fffff960`00059250 fffff900`c00ae170 00000000`00000003 00000000`00000000 : win32k!ttfdSemQueryFontTree+0x5a fffff880`09fc0760 fffff960`000a5527 : fffff880`09fc0870 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!PDEVOBJ::QueryFontTree+0x63 fffff880`09fc07e0 fffff960`000600ae : fffff900`c008a010 00000000`00000000 00000000`00000002 00000000`00000000 : win32k!PFEOBJ::pfdg+0xa3 fffff880`09fc0840 fffff960`000b9cbc : fffff900`c074e730 fffff880`09fc0ad0 fffff880`09fc09d0 fffff880`09fc0b20 : win32k!RFONTOBJ::bRealizeFont+0x46 fffff880`09fc0960 fffff960`0008b0e1 : 00000000`10018000 fffff900`00000000 000003da`00000000 0035f554`00000002 : win32k!RFONTOBJ::bInit+0x548 fffff880`09fc0a80 fffff960`0008b077 : 00000000`00000000 fffff880`09fc0ca0 00000000`70616d63 029402bc`0035f500 : win32k!ulGetFontData2+0x31 fffff880`09fc0af0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!ulGetFontData+0x7f STACK_COMMAND: kb FOLLOWUP_IP: win32k!sfac_GetLongGlyphIDs+84 fffff960`000623f4 44891e mov dword ptr [rsi],r11d SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: win32k!sfac_GetLongGlyphIDs+84 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ecdcd5a FAILURE_BUCKET_ID: X64_0x50_win32k!sfac_GetLongGlyphIDs+84 BUCKET_ID: X64_0x50_win32k!sfac_GetLongGlyphIDs+84 Followup: MachineOwner ---------
  4. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\010612-14336-02.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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a0f000 PsLoadedModuleList = 0xfffff800`01c54670 Debug session time: Fri Jan 6 15:46:13.846 2012 (UTC - 7:00) System Uptime: 0 days 5:41:01.502 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050031, 6f8, fffff8800126a892} Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000006f8 Arg4: fffff8800126a892 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: uTorrent.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80001a8b1e9 to fffff80001a8bc40 STACK_TEXT: fffff880`009b7c68 fffff800`01a8b1e9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx fffff880`009b7c70 fffff800`01a896b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`009b7db0 fffff880`0126a892 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 00000000`0a391848 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsInitializeTopLevelIrp+0x22 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiDoubleFaultAbort+b2 fffff800`01a896b2 90 nop SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiDoubleFaultAbort+b2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 Followup: MachineOwner ---------
  5. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\YamYam\010612-14336-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01a66000 PsLoadedModuleList = 0xfffff800`01cab670 Debug session time: Fri Jan 6 02:36:17.571 2012 (UTC - 7:00) System Uptime: 0 days 0:31:06.351 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffff80001adab65, 0, ffffffffffffffff} Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) 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. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff80001adab65, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: ffffffffffffffff, Parameter 1 of the exception 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!ExpInterlockedPopEntrySListFault16+0 fffff800`01adab65 498b08 mov rcx,qword ptr [r8] EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001d15100 ffffffffffffffff ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. BUGCHECK_STR: 0x1E_c0000005 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: firefox.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80001b2e588 to fffff80001ae2c40 STACK_TEXT: fffff880`081f7fa8 fffff800`01b2e588 : 00000000`0000001e ffffffff`c0000005 fffff800`01adab65 00000000`00000000 : nt!KeBugCheckEx fffff880`081f7fb0 fffff800`01ae22c2 : fffff880`081f8788 00000000`00000002 fffff880`081f8830 fffffa80`041cf3f8 : nt! ?? ::FNODOBFM::`string'+0x4977d fffff880`081f8650 fffff800`01ae0bca : 00000000`00097e2f fffff880`081f8880 fffffa80`04527000 fffff6fb`82200348 : nt!KiExceptionDispatch+0xc2 fffff880`081f8830 fffff800`01adab65 : 00000000`00000002 fffff800`01af344d 80000001`1c4ed867 fffff880`081f8a40 : nt!KiGeneralProtectionFault+0x10a fffff880`081f89c0 fffff800`01af344d : 80000001`1c4ed867 fffff880`081f8a40 fffff700`01080000 fffffa80`041cf3f8 : nt!ExpInterlockedPopEntrySListFault16 fffff880`081f89d0 fffff800`01af019e : 00000000`00000001 00000000`1a04c000 fffff880`081f8c20 fffff680`000d0260 : nt!MiResolveDemandZeroFault+0x14d fffff880`081f8ac0 fffff800`01ae0d6e : 00000000`00000001 00000000`1a04c000 00000000`0605c601 00000000`15d01000 : nt!MmAccessFault+0x5de fffff880`081f8c20 00000000`724e73d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`0043ca4c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x724e73d0 STACK_COMMAND: kb FOLLOWUP_IP: nt!ExpInterlockedPopEntrySListFault16+0 fffff800`01adab65 498b08 mov rcx,qword ptr [r8] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nt!ExpInterlockedPopEntrySListFault16+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!ExpInterlockedPopEntrySListFault16+0 BUCKET_ID: X64_0x1E_c0000005_nt!ExpInterlockedPopEntrySListFault16+0 Followup: MachineOwner ---------
Run Disk Check with just the Automatically fix file system errors checked

Also, check for viruses.
  1. Download and install the free version (do not start the trial) of Malwarebytes : Free anti-malware, anti-virus and spyware removal download and make sure to select the update box before finishing installation. Let it update. Do not run it yet.
  2. Download VIPRE Rescue - VIPRE Computer Recovery Solution from Sunbelt Software but do not unzip it yet.
  3. Download the Fakerean removal tool
  4. Start in Safe Mode and run in the following order.
    a. Unzip VIPRE Rescue and let it run.
    b. Run a full scan of Malwarebytes
    c. Run the fakerean tool.

Post back your results.
My System SpecsSystem Spec
15 Jan 2012   #37
YamYam

Windows 7
 
 
ASUS BIOS, Intel Chipset E7200 and Windows 7 (!)

Dear all,

I think I got the reason for all my problems, but first an update:
1. Disk Check in Windows 7 : no problems found
2. VIPRE Rescue : no viruses found
3. Full scan of Malwarebytes : : no viruses found
4. Fakerean tool : no problems/viruses
Still there are a lot of BSOD’s.

Then someone suggested me to look AGAIN at the BIOS.
I got the most recent BIOS (version 07.02) but, I found out that this BIOS does NOT support the Core 2Duo, E7200 processor; it supports previous processors but not the 7200 (http://www.asus.nl/Barebone_PC/V_Ser.../V3P5G33/#CPUS)
The system (ASUS V3-P5G33 barebone with Core 2Duo E7200 processor) was sold to me and functioned without problems with Windows XP for more than 3 years.
The ASUS V3-P5G33 barebone is made of a P5K-VM/V motherboard. For both motherboards (VM and V), newer BIOS’s are available which support the Core 2Duo E7200 processor (http://usa.asus.com/Motherboards/Int...ket_775/P5KVM/). Flashing the BIOS from the ASUS V3-P5G33 barebone, however, is not permitted. When I tried to update the BIOS, I get the message that the model of the BIOS image does not match the BIOS ROM currently present.
The ASUS helpdesk comfirms my findings mentioned above. But asking for a solution, or the possibility to flash the BIOS with the newer version, it keeps shamefacedly quiet; ASUS does not answer.

I think the only way to keep the computer running is to reinstall Windows XP.
I tried to install Windows XP on a new SSD, and it is running now for 48 hours without problems.
Does someone have additional ideas to resolve the problem with the Windows 7/ASUS V3-P5G33 barebone/Core 2Duo E7200 processor problem ?

YamYam
My System SpecsSystem Spec
15 Jan 2012   #38
writhziden

Windows 7 Home Premium 64 Bit
 
 

If the problem is hardware related, you may want to start a thread in the Hardware & Devices forum where users with more experience may find an answer for you.

Let us know if you get it resolved.
My System SpecsSystem Spec
15 Jan 2012   #39
YamYam

Windows 7
 
 
File closed for now

Thanks all for your help until now.
I will close this topic and transfer it to the hardware & devices forum.

YamYam
My System SpecsSystem Spec
Reply

 BSOD after installing Windows7 on a new SSD and an old XP-machine




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Installing Windows7 from external HDD
Hello. My burner stopped working for some reason so I am attempting to install Windows7 64 from an old external IDE hard drive 2.5. I still have xp 32 and will install W7 on an empty partition or erase the whole disk. The problem is I don't know how to make the external drive boot the image. The...
Installation & Setup
Now trying to getwife's vista machine to see printer on Windows7 netwo
I looked both on the Vista Forums and on this forum and could not find an answer. The machine is a HP G60 Notebook PC running windows Vista 32-bit OS. She's a member of the workgroup, but we can't get the printer added. We go through the add printer steps, clicking on add a network, wireless or...
Hardware & Devices
Installing windows7- getting errors
Alright so recently my OS gave up on me out of the blue and I could't boot into windows anymore. I put in my W7 CD and ran it from boot, I tried to install Windows over my C: but it gave me an errror. I then tried formating my C: (SSD 120gig) and now when I try to install Windows 7 on it I get...
Installation & Setup
BSOD when dual installing XP with windows7
I bought a new computer with vista home install and I upgraded with windows 7 (my intention was never tu use vista) I create a partition and try to install my XP professional so i could use both os. I booted from my CD like allways start copyng the file and then will not let me install the XP (blu...
BSOD Help and Support
Problem installing Windows7 RC1
Each time I try to install RC-1 from the image disk I receive the following message. "Windows could not prepare the computer to boot into the next phase of installation." Computer currently is running Vista Ultimate. Any help would be greatly appreciated. Thanks and have a great day!
Installation & Setup


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 07:03.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App