![]() |
|
23 Jan 2010 | #1 |
|
need help... BSOD...
hi all.. i keep getting bsod but have no reason why i have attached a dmp file and would be grateful if anyone could take a look and shed some light on the matter... thanks..............
|
My System Specs![]() |
. |
|
23 Jan 2010 | #2 |
|
Hi and welcome there isnt much info on the cause of this type of BSOD. Checked build kernel error. I suspect that this can be caused by something else, as I've seen 2 of these over the past several months - and none appeared to be a checked build Since it appears to be related to the win 7 kernal I would run a system file check to verify and repair your system files type cmd in search>right click and run as admin>sfc /scannow let us know the result as you may have to run it several times Ken 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\012310-33328-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x8283a000 PsLoadedModuleList = 0x82979570 Debug session time: Fri Jan 22 19:12:25.981 2010 (GMT-5) System Uptime: 0 days 0:11:31.606 Loading Kernel Symbols ............................................................... ................................................................ .................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1, {82a84c1f, 0, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt!NtCreateFile+0 ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* APC_INDEX_MISMATCH (1) This is a kernel internal error. The most common reason to see this bugcheck is when a filesystem or a driver has a mismatched number of calls to disable and re-enable APCs. The key data item is the Thread->KernelApcDisable field. A negative value indicates that a driver has disabled APC calls without re-enabling them. A positive value indicates that the reverse is true. This check is made on exit from a system call. Arguments: Arg1: 82a84c1f, address of system function (system call) Arg2: 00000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex Arg3: 0000ffff, Thread->KernelApcDisable Arg4: 00000000, Previous KernelApcDisable Debugging Details: ------------------ FAULTING_IP: nt!NtCreateFile+0 82a84c1f 8bff mov edi,edi CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1 PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 77ce64f4 to 8286fb23 STACK_TEXT: 95bf4d34 77ce64f4 badb0d00 04edef40 00000000 nt!KiServiceExit2+0x17a WARNING: Frame IP not in any known module. Following frames may be wrong. 04edefdc 00000000 00000000 00000000 00000000 0x77ce64f4 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nt!NtCreateFile+0 82a84c1f 8bff mov edi,edi SYMBOL_NAME: nt!NtCreateFile+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbffc FAILURE_BUCKET_ID: 0x1_nt!NtCreateFile+0 BUCKET_ID: 0x1_nt!NtCreateFile+0 Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* APC_INDEX_MISMATCH (1) This is a kernel internal error. The most common reason to see this bugcheck is when a filesystem or a driver has a mismatched number of calls to disable and re-enable APCs. The key data item is the Thread->KernelApcDisable field. A negative value indicates that a driver has disabled APC calls without re-enabling them. A positive value indicates that the reverse is true. This check is made on exit from a system call. Arguments: Arg1: 82a84c1f, address of system function (system call) Arg2: 00000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex Arg3: 0000ffff, Thread->KernelApcDisable Arg4: 00000000, Previous KernelApcDisable Debugging Details: ------------------ FAULTING_IP: nt!NtCreateFile+0 82a84c1f 8bff mov edi,edi CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1 PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 77ce64f4 to 8286fb23 STACK_TEXT: 95bf4d34 77ce64f4 badb0d00 04edef40 00000000 nt!KiServiceExit2+0x17a WARNING: Frame IP not in any known module. Following frames may be wrong. 04edefdc 00000000 00000000 00000000 00000000 0x77ce64f4 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nt!NtCreateFile+0 82a84c1f 8bff mov edi,edi SYMBOL_NAME: nt!NtCreateFile+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbffc FAILURE_BUCKET_ID: 0x1_nt!NtCreateFile+0 BUCKET_ID: 0x1_nt!NtCreateFile+0 Followup: MachineOwner --------- |
My System Specs![]() |
23 Jan 2010 | #3 |
|
have run scan. says that.... windows resource protection did not find any integrity voilations
|
My System Specs![]() |
. |
|
![]() |
Thread Tools | |
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 13:55. |
![]() ![]() ![]() ![]() ![]() |