I should add, that since I ran the "driver verifier" per Reventon's suggestion, It's been progressively harder to start up the system without a BSoD loop. After the most recent BSoD(about twenty minutes ago), the computer blued out and restarted itself three times, then froze at the startup logo animation screen.
Ok, that is definitely a sign there is a driver problem here.
However, as this crash was after you ran the BSOD info collection(?) there is no record of it in any of the files.
You do not need to run the full collection application again, simply go to
C:\Windows\Minidump , sort the files by date and copy any files dated newer than 07/27/10 to a zipped folder.
I haven't had a BSoD in about two hours, though it's only a matter of time. Until then, I can only say that when I'm getting the most recent BSoD's, it seems to hang at the part where it says something to the effect of "collecting" or "retrieving" or "something"...
Whatever it says, it's not creating any new dumps, and I have no records after 7/27.
Well since this is obviously a driver (from the bugcheck, and the fact that it double faults at the same memory address) I have two suggestions. I havent been following this thread so they may have already been offered.
The Usual causes: Memory corruption, Hardware (memory in particular), Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service PackDownload a copy of
First memory is mentioned several time so I would
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Beyond that, please run Verifier with these settings:
[quote]
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Code:
Delete these registry keys (works in XP, Vista, Win7):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users[/quote
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\New folder\040510-21184-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03018000 PsLoadedModuleList = 0xfffff800`03255e50
Debug session time: Mon Apr 5 23:36:15.059 2010 (GMT-4)
System Uptime: 0 days 1:03:50.651
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff80003050e60}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
Followup: MachineOwner
---------
2: 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: fffff80003050e60
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 fffff80003087b69 to fffff80003088600
STACK_TEXT:
fffff880`03369ce8 fffff800`03087b69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`03369cf0 fffff800`03086032 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03369e30 fffff800`03050e60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`03385fd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x60
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`03086032 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: 4b88cfeb
FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Followup: MachineOwner
---------
2: kd> .tss
Code:
ASMMAP64.sys fffff880`04940000 fffff880`04947000 0x00007000 0x45c63998 2/4/2007 15:52:56
sncduvc.SYS fffff880`02de2000 fffff880`02deaa80 0x00008a80 0x495894f2 12/29/2008 05:14:26
AsDsm.sys fffff880`014c0000 fffff880`014cd000 0x0000d000 0x49950fc2 2/13/2009 02:14:26
mcdbus.sys fffff880`0443b000 fffff880`04477880 0x0003c880 0x49a3cd1f 2/24/2009 06:34:07
spldr.sys fffff880`0184a000 fffff880`01852000 0x00008000 0x4a0858bb 5/11/2009 12:56:27
ATK64AMD.sys fffff880`04a4d000 fffff880`04a55000 0x00008000 0x4a0a1cb6 5/12/2009 21:04:54
amdxata.sys fffff880`01455000 fffff880`01460000 0x0000b000 0x4a12f2eb 5/19/2009 13:56:59
snp2uvc.sys fffff880`02c19000 fffff880`02dd0600 0x001b7600 0x4a13bb19 5/20/2009 04:11:05
L1C62x64.sys fffff880`04c46000 fffff880`04c59000 0x00013000 0x4a483ac7 6/28/2009 23:53:43
rimspe64.sys fffff880`04c2d000 fffff880`04c46000 0x00019000 0x4a4bf749 7/1/2009 19:54:49
rixdpe64.sys fffff880`10d76000 fffff880`10dcc000 0x00056000 0x4a4f2e74 7/4/2009 06:27:00