I've been getting the BSOD recently when resuming my computer from sleep. I was going to reformat but id like to be able to correct the problem without taking that measure if possible. This problem is recent to the last few weeks.
Besides the BSOD on resume of sleep the system runs awesome
Attached is my BSOD dump & system file collection. The System health report is in the same folder.
Comp Specs
Windows 7 Pro Sp1
x64
full retail version
system is less then 1 year old haven't had problems with it
would like to avoid reinstalling if possible os been on system from the beginning
The most recent one Related to
Protexis_Licensing from Protexis Inc.
Note: Located in \%Program Files%\Common Files\Protexis\License Service\
There is also an error with disk hardware. I would run chkdsk
IF possible I would remove it. I have zero experience with it.
A- CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.
Do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.
Then reboot and let the test run.
It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.
See "CHKDSK LogFile" below in order to check the results of the test.
B- Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
C-CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.
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\Windows_NT6_BSOD_jcgriff2\060211-18517-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e49000 PsLoadedModuleList = 0xfffff800`0308e650
Debug session time: Thu Jun 2 08:00:32.909 2011 (GMT-4)
System Uptime: 0 days 6:22:12.142
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fb80008000, ffffffffc000000e, 107213880, fffff70001000000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+37bba )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
[U][I][B][COLOR=Red]The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error[/COLOR].[/B][/I][/U] Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fb80008000, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000107213880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff70001000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000000e
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
[COLOR=Red][U][I][B]
PROCESS_NAME: PsiService_2.e[/B][/I][/U][/COLOR]
CURRENT_IRQL: 0
TRAP_FRAME: fffff880033a5f80 -- (.trap 0xfffff880033a5f80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff70001080068 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031da83a rsp=fffff880033a6110 rbp=0000000000000001
r8=fffff70001000000 r9=0000000000000078 r10=0020000000000000
r11=fffff880033a6170 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!MiInsertVadCharges+0x10a:
fffff800`031da83a 490fa308 bt qword ptr [r8],rcx ds:b060:fffff700`01000000=fffffa8005e149f0
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002f38842 to fffff80002ec8d00
STACK_TEXT:
fffff880`033a5c68 fffff800`02f38842 : 00000000`0000007a fffff6fb`80008000 ffffffff`c000000e 00000001`07213880 : nt!KeBugCheckEx
fffff880`033a5c70 fffff800`02ef072f : fffffa80`073bbdd0 fffff880`033a5de0 fffffa80`0620b3f8 fffffa80`073bbdd0 : nt! ?? ::FNODOBFM::`string'+0x37bba
fffff880`033a5d50 fffff800`02ed707a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff800`02ed5fe8 : nt!MiIssueHardFault+0x28b
fffff880`033a5e20 fffff800`02ec6e2e : 00000000`00000000 fffff700`01000000 fffff880`033a6000 00000000`0038f000 : nt!MmAccessFault+0x146a
fffff880`033a5f80 fffff800`031da83a : 00000000`00010000 000007ff`fffdffff 00000000`fffffffe fffff800`031da698 : nt!KiPageFault+0x16e
fffff880`033a6110 fffff800`031c0546 : ffffffff`ffffffff ffffffff`ffffffff fffff880`033a6430 00000000`00002000 : nt!MiInsertVadCharges+0x10a
fffff880`033a61a0 fffff800`02ec7f93 : ffffffff`ffffffff fffff880`033a6ad8 00000000`00000040 fffff880`033a6648 : nt!NtAllocateVirtualMemory+0x726
fffff880`033a6340 fffff800`02ec4530 : fffff800`031b6bd3 00000000`00000000 fffff800`02e98e0f 00000000`00000022 : nt!KiSystemServiceCopyEnd+0x13
fffff880`033a6548 fffff800`031b6bd3 : 00000000`00000000 fffff800`02e98e0f 00000000`00000022 fffff680`003f7ef8 : nt!KiServiceLinkage
fffff880`033a6550 fffff800`02ec7f93 : fffff880`033a6930 fffff800`02ec6f3d 00000000`00000000 00000000`7efdf318 : nt!NtSetInformationProcess+0x4c6
fffff880`033a68a0 fffff800`02ec4530 : fffff800`031b6396 00000000`00000000 fffffa80`07966930 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`033a6a38 fffff800`031b6396 : 00000000`00000000 fffffa80`07966930 00000000`00000000 fffff800`031c20c4 : nt!KiServiceLinkage
fffff880`033a6a40 fffff800`031b4ce0 : 00000000`00004000 00000000`00040000 00000000`00000000 00000000`00001000 : nt!RtlCreateUserStack+0x122
fffff880`033a6b30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspAllocateThread+0x5bb
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+37bba
fffff800`02f38842 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+37bba
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b
FAILURE_BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+37bba
BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+37bba
Followup: MachineOwner
---------
