New
#11
Ok... Ive looked at the .dmp files but they were inconclusive, so if you're up to it, were going to have to run some more tests in order to pin it down some more...
The dmp(s) point to ntkrpamp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause.
We need to enable driver verifier in order to get more conclusive .dmp files... follow these instructions..
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"
- 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).
We are also getting a Memory Management error, which may indicate bad RAM...
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.
This should run overnight for the best results..
I also found SPTD.sys in your loaded driver list...This is notorious for causing crashes... Try removing any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 00041289, The subtype of the bugcheck. Arg2: 06664001 Arg3: 00001b76 Arg4: 0440d209 Debugging Details: ------------------ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {0, 2, 1, 82b029c7} Probably caused by : ntkrpamp.exe ( nt!KeWaitForGate+13d ) Followup: MachineOwner --------- .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {0, 2, 1, 82b029c7} Probably caused by : ntkrpamp.exe ( nt!KeWaitForGate+13d ) Followup: MachineOwner --------- ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {c0000005, 82b5681a, 8db8fb48, 8db8f720} Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+814 ) Followup: MachineOwner ---------
Quote
