Blue screen
-
Monday, January 28, 2013 1:43 AM
Hi, i had few minutes ago a bluescreen, can anyone help me out?
http://www.sendspace.com/file/51z80g
thanks
All Replies
-
Monday, January 28, 2013 7:40 AM
Hi anixus,
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ae4280, The address that the exception occurred at
Arg3: fffff880033c3dc8, Exception Record Address
Arg4: fffff880033c3620, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!IofCallDriver+50
fffff800`02ae4280 49ff64c070 jmp qword ptr [r8+rax*8+70h]
EXCEPTION_RECORD: fffff880033c3dc8 -- (.exr 0xfffff880033c3dc8)
ExceptionAddress: fffff80002ae4280 (nt!IofCallDriver+0x0000000000000050)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000000e0
Attempt to read from address 00000000000000e0
CONTEXT: fffff880033c3620 -- (.cxr 0xfffff880033c3620)
rax=000000000000000e rbx=fffff880018313b0 rcx=fffffa80105ef3c0
rdx=fffffa8011680ab0 rsi=fffffa8011680ab0 rdi=fffffa800d1ce600
rip=fffff80002ae4280 rsp=fffff880033c4008 rbp=0000000000000001
r8=0000000000000000 r9=000000000000000e r10=fffff80002c62588
r11=fffffa800cd7b170 r12=fffffa800d1ce4b0 r13=fffffa800cf5d4f0
r14=0000000000000002 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!IofCallDriver+0x50:
fffff800`02ae4280 49ff64c070 jmp qword ptr [r8+rax*8+70h] ds:002b:00000000`000000e0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 00000000000000e0
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0a100
GetUlongFromAddress: unable to read from fffff80002d0a1c0
00000000000000e0 Nonpaged pool
FOLLOWUP_IP:
fvevol!FveFilterDeviceControl+1d0
fffff880`01802808 8bd8 mov ebx,eax
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffff88001802808 to fffff80002ae4280
STACK_TEXT:
fffff880`033c4008 fffff880`01802808 : 00000000`00000500 fffff800`02aebf21 fffff8a0`00000000 00000000`00000000 : nt!IofCallDriver+0x50
fffff880`033c4010 fffff880`01b58082 : fffffa80`11680ab0 00000000`00000000 fffffa80`11680fb8 fffffa80`11c24190 : fvevol!FveFilterDeviceControl+0x1d0
fffff880`033c4080 fffff800`02d91e0a : fffffa80`11c24040 fffffa80`11c24040 00000000`00000000 fffff880`033c49f0 : volsnap!VolSnapDeviceControl+0x72
fffff880`033c40f0 fffff880`01b4e2c5 : fffff8a0`00246380 fffff880`01b4dcf0 00000000`00000006 fffffa80`11c24190 : nt!IoVolumeDeviceToDosName+0x92
fffff880`033c49c0 fffff880`01b4dd1c : 00000000`00000001 fffff880`01b4dcf0 fffffa80`0eea5b38 fffffa80`0cd7b170 : volsnap!VspLogErrorWorker+0x85
fffff880`033c4b40 fffff800`02ae4641 : fffff880`01b4dcf0 fffff800`02c782d8 fffffa80`0cd7b170 00000000`00000000 : volsnap!VspMediumPriorityWorkItem+0x2c
fffff880`033c4b70 fffff800`02d71e5a : 00000000`00000000 fffffa80`0cd7b170 00000000`00000080 fffffa80`0cd65040 : nt!ExpWorkerThread+0x111
fffff880`033c4c00 fffff800`02acbd26 : fffff880`03165180 fffffa80`0cd7b170 fffff880`0316ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033c4c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: fvevol!FveFilterDeviceControl+1d0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: fvevol
IMAGE_NAME: fvevol.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce793b6
STACK_COMMAND: .cxr 0xfffff880033c3620 ; kb
FAILURE_BUCKET_ID: X64_0x7E_fvevol!FveFilterDeviceControl+1d0
BUCKET_ID: X64_0x7E_fvevol!FveFilterDeviceControl+1d0
Followup: MachineOwner
---------------------------------------------------------------------------------------------------------------------------------------------Bug Check 0x7E : http://msdn.microsoft.com/en-us/library/windows/hardware/ff559239(v=vs.85).aspx
** The Blue Screen Caused By ( fvevol.sys ) , Fvevol.sys file information
The process known as BitLocker Drive Encryption Driver belongs to software Bitlocker Drive Encryption Filter Driver or BitLocker Drive Encryption Filter Driver by Microsoft (www.microsoft.com).
I suggest you to check your system file by, Run a system file check to verify and repair you system files. You do this by typing cmd in search, then right click and run as admin.
SFC /SCANNOW
After that you should check you HDD by this Command.
CHKDSK /R /F
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
If these steps doesn’t solve your Blue screen try to Disable Bitlocker Services from :
Run.. -à Services.msc à Double Click on (BitLocker Drive Encryption Service) à Startup type à Disabled à ok à Restart your computer.
Regards,
MCT / MCITP / MCTS / MCSA / MCSE / C|EH / CCNA
- Marked As Answer by Vincent Wang-MCSCMicrosoft Contingent Staff, Moderator Tuesday, February 05, 2013 7:24 AM
-
Tuesday, January 29, 2013 8:26 AMModerator
Hi,
Also check volsnap.sys, you can refer to the following thread:
BSOD volsnap.sys
Hope this helps.
Vincent Wang
TechNet Community Support
- Marked As Answer by Vincent Wang-MCSCMicrosoft Contingent Staff, Moderator Tuesday, February 05, 2013 7:24 AM
-
Thursday, January 31, 2013 9:19 PM
Blue Screen in Window has two main reasons. First, it could be a virus infection. In that case you have to reboot your computer and start it in safe mode by pressing F8. Scan your Hard drive (C) with an updated and valid anti-virus. That may take a good time. After applying those steps your problem should be resolve. The other cause is a missing of system files. In that case you have to find a Windows 7 DVD (Operating System).Then, Boot your computer on the drive (D), that mean the DVD drive. Restart your computer and let the DVD to repair your system first. If that is not work, reformat your computer completely. However, don’t forget to back-up your important files before starting the formatting. Scan your files on a safe computer before you put them back on your computer. Now, your computer should works as well as when it was brand new.
- Proposed As Answer by Therlande Louis-Jean Thursday, January 31, 2013 9:19 PM
-
Friday, February 01, 2013 10:12 PMModerator
TLJ
Just an FYI. Generally one doesnt propose their own post as an answer (someone else might).
MS-MVP 2010, 2011, 2012 Team ZigZag
.png)
