 | |
| |
| 10 Jun 2011 | #1 |
| | Bsod Seems like I am getting a few random BSOD's that have been happening lately. Thank you for any help given. Attached are 4 minidumps. |
My System Specs | |
| 11 Jun 2011 | #2 |
| | 
Quote: Originally Posted by nkyredsfan  Seems like I am getting a few random BSOD's that have been happening lately. Thank you for any help given. Attached are 4 minidumps. Ur more recent minidump points to ntoskrnl.exe. So please try the follow steps, NTOSKRNL.EXE is missing or corrupt. Error message: "Windows could not start because of a computer disk hardware configuration problem" ----------------------- Those are oldest errors,athrx.sys,nwifi.sys, and usbhub.sys,but if you still want to <<fix them>> for good or bad do that.... athrx.sys is caused by Atheros Wireless LAN device driver,so unistall the software/driver,clean with ccleaner http://www.piriform.com/CCLEANER any remainings fragments,install the most updated software driver. nwifi.sys cause by NativeWiFi Miniport Driver,possible solution(the same with above) usbhub.sys caused by USB driver,possible solution,uninstall all ur usb drivers,restart let windows to install them automatically. |
| My System Specs |
| 11 Jun 2011 | #3 |
| | A Zone Alarm software probably Zone Alarm Firewall is the cause, please remove it from your system Use the Removal Tool Code: vsdatant.sys fffff880`02d07000 fffff880`02d98000 0x00091000 0x4b09cb48 23/11/2009 03:37:44 Code: *******************************************************************************
* *
* 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: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffff800032d2690
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
TRAP_FRAME: 000000000000ff70 -- (.trap 0xff70)
Unable to read trap frame at 00000000`0000ff70
LAST_CONTROL_TRANSFER: from fffff800032d3c69 to fffff800032d4700
STACK_TEXT:
fffff800`00ba4d28 fffff800`032d3c69 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`032d2132 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff800`032d2690 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`0000ff70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x10
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`032d2132 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: 4d9fdd34
FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
BUCKET_ID: X64_0x7f_8_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: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffff800032d2690
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
TRAP_FRAME: 000000000000ff70 -- (.trap 0xff70)
Unable to read trap frame at 00000000`0000ff70
LAST_CONTROL_TRANSFER: from fffff800032d3c69 to fffff800032d4700
STACK_TEXT:
fffff800`00ba4d28 fffff800`032d3c69 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`032d2132 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff800`032d2690 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`0000ff70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x10
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`032d2132 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: 4d9fdd34
FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Followup: MachineOwner
--------- |
| My System Specs |
| . |
| |
| 12 Jun 2011 | #4 |
| | Thanks to both of you. I uninstalled ZA and when I get more time I will work with the drivers. |
| My System Specs |
 |
Bsod problems?
« A patch is preventing your system from starting
|
after extracting zip file explorer keeps crashing »
| Thread Tools | |
All times are GMT -5. The time now is 02:17 PM.
