1. #1
    sad's Avatar
    Join Date
    Feb 2014
    Location
    Lyon, France
    Posts
    8

    BSOD when mount on virtual drive - Windows 7 x64 SP1

    Hi all,

    To begin, excuse my poor english, I'm a french who doesn't practice for a long time. ^^
    I hope you can help me.
    I ofen mount some ISO or MDS ... on virtual drive without matter, but till 2 weeks, I can't mount anything, when I try i've got the BSOD...
    I try with Daemon tools, power iso, magicdisc and alcohol 52%.
    I update all my drivers, i try Check Disk
    - SFC
    - Fix it
    - Windows Repair.
    I update framework, but doesn't work... .
    When i clic "Mount" i fall in BSOD.

    Here is a report of whocrashed:
    Code:
    Crash dump directory:  C:\Windows\Minidump
    
    Crash dumps are enabled on your  computer.
    
    On  Wed 19/02/2014 18:50:35 GMT your computer crashed
    crash dump file:  C:\Windows\Minidump\021914-28860-01.dmp
    This was probably caused by the  following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF8800A9F6BF0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path:  C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &  System
    Bug check description: This indicates that a kernel-mode program  generated an exception which the error handler did not catch.
    This appears to  be a typical software driver bug and is not likely to be caused by a hardware  problem. 
    The crash took place in the Windows kernel. Possibly this problem  is caused by another driver that cannot be identified at this time.  
    
    
    
    On  Wed 19/02/2014 18:50:35 GMT your computer crashed
    crash dump file:  C:\Windows\memory.dmp
    This was probably caused by the following module: ksecdd.sys (ksecdd+0x26B3) 
    Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF8800A9F6BF0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path:  C:\Windows\system32\drivers\ksecdd.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Kernel Security  Support Provider Interface
    Bug check description: This indicates that a  kernel-mode program generated an exception which the error handler did not  catch.
    This appears to be a typical software driver bug and is not likely to  be caused by a hardware problem. 
    The crash took place in a standard  Microsoft module. Your system configuration may be incorrect. Possibly this  problem is caused by another driver on your system that cannot be identified at  this time. 
    
    
    
    On Wed 19/02/2014 18:22:54 GMT your computer  crashed
    crash dump file: C:\Windows\Minidump\021914-24928-01.dmp
    This  was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF8800A56DBF0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path:  C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &  System
    Bug check description: This indicates that a kernel-mode program  generated an exception which the error handler did not catch.
    This appears to  be a typical software driver bug and is not likely to be caused by a hardware  problem. 
    The crash took place in the Windows kernel. Possibly this problem  is caused by another driver that cannot be identified at this time.  
    
    
    
    On  Wed 19/02/2014 17:58:06 GMT your computer crashed
    crash dump file:  C:\Windows\Minidump\021914-26535-01.dmp
    This was probably caused by the  following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF88004788BF0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path:  C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &  System
    Bug check description: This indicates that a kernel-mode program  generated an exception which the error handler did not catch.
    This appears to  be a typical software driver bug and is not likely to be caused by a hardware  problem. 
    The crash took place in the Windows kernel. Possibly this problem  is caused by another driver that cannot be identified at this time.  
    
    
    
    On  Wed 19/02/2014 17:29:31 GMT your computer crashed
    crash dump file:  C:\Windows\Minidump\021914-25474-01.dmp
    This was probably caused by the  following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF8800ACDEBF0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path:  C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &  System
    Bug check description: This indicates that a kernel-mode program  generated an exception which the error handler did not catch.
    This appears to  be a typical software driver bug and is not likely to be caused by a hardware  problem. 
    The crash took place in the Windows kernel. Possibly this problem  is caused by another driver that cannot be identified at this time.  
    
    
    
    On  Wed 19/02/2014 16:53:55 GMT your computer crashed
    crash dump file:  C:\Windows\Minidump\021914-22978-01.dmp
    This was probably caused by the  following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF8800800BBF0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path:  C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &  System
    Bug check description: This indicates that a kernel-mode program  generated an exception which the error handler did not catch.
    This appears to  be a typical software driver bug and is not likely to be caused by a hardware  problem. 
    The crash took place in the Windows kernel. Possibly this problem  is caused by another driver that cannot be identified at this time.  
    
    
    
    On  Wed 19/02/2014 14:26:29 GMT your computer crashed
    crash dump file:  C:\Windows\Minidump\021914-20139-01.dmp
    This was probably caused by the  following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF8800731ABF0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path:  C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &  System
    Bug check description: This indicates that a kernel-mode program  generated an exception which the error handler did not catch.
    This appears to  be a typical software driver bug and is not likely to be caused by a hardware  problem. 
    The crash took place in the Windows kernel. Possibly this problem  is caused by another driver that cannot be identified at this time.  
    
    
    
    On  Tue 18/02/2014 17:45:52 GMT your computer crashed
    crash dump file:  C:\Windows\Minidump\021814-16458-01.dmp
    This was probably caused by the  following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF88009E4DBF0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path:  C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &  System
    Bug check description: This indicates that a kernel-mode program  generated an exception which the error handler did not catch.
    This appears to  be a typical software driver bug and is not likely to be caused by a hardware  problem. 
    The crash took place in the Windows kernel. Possibly this problem  is caused by another driver that cannot be identified at this time.  
    
    
    
    On  Tue 18/02/2014 17:41:48 GMT your computer crashed
    crash dump file:  C:\Windows\Minidump\021814-15490-01.dmp
    This was probably caused by the  following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF88009E67BF0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path:  C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &  System
    Bug check description: This indicates that a kernel-mode program  generated an exception which the error handler did not catch.
    This appears to  be a typical software driver bug and is not likely to be caused by a hardware  problem. 
    The crash took place in the Windows kernel. Possibly this problem  is caused by another driver that cannot be identified at this time.  
    
    
    
    On  Tue 18/02/2014 17:36:23 GMT your computer crashed
    crash dump file:  C:\Windows\Minidump\021814-16036-01.dmp
    This was probably caused by the  following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF88009D75BF0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path:  C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &  System
    Bug check description: This indicates that a kernel-mode program  generated an exception which the error handler did not catch.
    This appears to  be a typical software driver bug and is not likely to be caused by a hardware  problem. 
    The crash took place in the Windows kernel. Possibly this problem  is caused by another driver that cannot be identified at this time. 
    
    
     
    I hope you can help me...

    Thank you
    Last edited by jcgriff2; 02-22-2014 at 02:52 PM. Reason: code box


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2

    re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    Bonjour, et bienvenue à Sysnative!

    Votre anglais est très bien, ne vous inquiétez pas! J'ai appris un peu de français, alors j'ai pensé que je dirais bonjour de cette façon! :O)

    Please refer to the following and reply back accordingly with the required information - http://www.sysnative.com/forums/bsod...ows-vista.html

    Regards,

    Patrick

  3. #3
    sad's Avatar
    Join Date
    Feb 2014
    Location
    Lyon, France
    Posts
    8

    re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    Quote Originally Posted by Patrick View Post
    Bonjour, et bienvenue à Sysnative!

    Votre anglais est très bien, ne vous inquiétez pas! J'ai appris un peu de français, alors j'ai pensé que je dirais bonjour de cette façon! :O)

    Please refer to the following and reply back accordingly with the required information - http://www.sysnative.com/forums/bsod...ows-vista.html

    Regards,

    Patrick
    Hi Patrick, your french is perfect.
    So I try Sysnative jcgriff2 BSOD File Collection app and it's repeating " Waiting for SystemInfo". It's been 1h30 i'm waiting it's finish ... I let it during the night (because it's 20h here ^^, don't know where you're from ^^)
    Run System Health Report doesn't work too... tell me "Untraceable access path" (it's a reverso translation from the french sentences i've got)
    I do the autorun, but I don't how to save a report ...

    Something new today, my computer freeze in BSOD when I start it. To come to tell you, I'm in "safe mode"... .

    Do you think i must reinstal windows?

  4. #4

    re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    If you're having difficulty with the BSOD tool, you can skip it for now. Let's instead access the crash dumps manually:

    1. Navigate to the %systemroot%\Minidump folder (so, for example - C:\Windows\Minidump)
    2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
    3. Upload the zip containing the DMP files to Skydrive or a hosting site of your choice and paste in your reply.

    As far as your freeze question goes, and booting into safe mode. After this happened, can you boot back into normal Windows? If not, do not fret, you can still boot into safe mode w/ networking and provide the dumps that way.

    Regards,

    Patrick

  5. #5
    sad's Avatar
    Join Date
    Feb 2014
    Location
    Lyon, France
    Posts
    8

    re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    Quote Originally Posted by Patrick View Post
    If you're having difficulty with the BSOD tool, you can skip it for now. Let's instead access the crash dumps manually:

    1. Navigate to the %systemroot%\Minidump folder (so, for example - C:\Windows\Minidump)
    2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
    3. Upload the zip containing the DMP files to Skydrive or a hosting site of your choice and paste in your reply.

    As far as your freeze question goes, and booting into safe mode. After this happened, can you boot back into normal Windows? If not, do not fret, you can still boot into safe mode w/ networking and provide the dumps that way.

    Regards,

    Patrick

    Minidump.zip
    Hi Patrick,

    here is my zip of minidump.
    I restore my system, then i can work on normal mode, but the tool make the same "waiting for systeminfo"...
    But in normal mode, i can't upload anything... with imageshack i've got the BSOD, and in sysnative, my computer freeze... .
    So i'm back on safe mode to upload ^^

  6. #6
    x BlueRobot's Avatar
    Join Date
    May 2013
    Location
    Minkowski Space
    Posts
    1,872

    re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    Code:
    BugCheck 1E, {ffffffffc0000005, fffff8800a9f6bf0, 0, 0}
    
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    Code:
    6: kd> !error ffffffffc0000005
    Error code: (NTSTATUS) 0xc0000005 (3221225477) - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    Access Violations seem to be really common with these kind of bugchecks, and are usually caused by software. In this case, it could access privileges or NULL pointers.

    Code:
    6: kd> .cxr 0xfffff8800a9f7370
    rax=0000000000000000 rbx=fffff8800a9f7f70 rcx=00000000002e0a70
    rdx=fffff8800a9f7de8 rsi=fffff8800a9f7f90 rdi=fffff8800a9f7f40
    rip=fffff88001dd86b3 rsp=fffff8800a9f7d50 rbp=0000000000000000
     r8=fffff8800a9f7e58  r9=00000000002e0a70 r10=fffffa8006d57d60
    r11=fffff8a0046c4000 r12=fffff8800a9f7f90 r13=fffff88001de6790
    r14=0000000080090301 r15=0000000000000000
    iopl=0         nv up ei ng nz ac pe cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010293
    ksecdd!KsecProcessSecurityContext+0x293:
    fffff880`01dd86b3 ff5010          call    qword ptr [rax+10h] ds:002b:00000000`00000010=????????????????
    The referenced address is a combination of the rax register which is simply a General Purpose Register (x64) and a offset of 10, to give the complete non-paged pool address. It seems like a NULL pointer.

    I couldn't find much information in the raw stack, apart from a data structure called NDR64_UNMRSHL_POINTER_QUEUE_ELEMENT which belongs to the msrpc module. It seems it may be used for unmarshalling a pointer. It makes sense because msrpc belongs to Remote Produrce Calls.

    Anyhow, I would suggest attempting to upload the MSINFO32 file manually, by following these instructions:

    1. Start, and then type: MSINFO32 or msinfo32
    2. File and Save
    3. Place the saved file (.NFO) in a zipped folder
    4. Upload the zipped folder in your next post
    Machines Can Think

    We don't make mistakes; we just have happy accidents.

  7. #7

    re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    Thanks!

    All of the attached DMP files are of the KMODE_EXCEPTION_NOT_HANDLED (1e) bug check.

    This indicates that a kernel-mode program generated an exception which the error handler did not catch.

    BugCheck 1E, {ffffffffc0000005, fffff8800a9f6bf0, 0, 0}

    ^^ The 1st parameter is 0xc0000005 which indicates an access violation occurred, let's see what caused it:

    Code:
    6: kd> .exr 0xfffff8800a9f7b18
    ExceptionAddress: fffff88001dd86b3 (ksecdd!KsecProcessSecurityContext+0x0000000000000293)
       ExceptionCode: c0000005 (Access violation)
    If we take a look at the call stack:

    Code:
    6: kd> kv
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff880`0a9f6b38 fffff800`0391f1bb : 00000000`0000001e ffffffff`c0000005 fffff880`0a9f6bf0 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0a9f6b40 fffff800`038e0d18 : ffbca55a`ffbba359 ffbfa85d`ffbda75c ffc3ac61`ffc1aa5f ffc9b065`ffc7ae64 : nt!KipFatalFilter+0x1b
    fffff880`0a9f6b80 fffff800`038b8cdc : ffdac478`ffd9c376 ffdeca7c`ffddc97a ffe1cd7d`ffdfcc7d ffe3d181`ffe2cf7f : nt! ?? ::FNODOBFM::`string'+0x83d
    fffff880`0a9f6bc0 fffff800`038b875d : fffff800`039d9d74 fffff880`0a9f8460 00000000`00000000 fffff800`03818000 : nt!_C_specific_handler+0x8c
    fffff880`0a9f6c30 fffff800`038b7535 : fffff800`039d9d74 fffff880`0a9f6ca8 fffff880`0a9f7b18 fffff800`03818000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`0a9f6c60 fffff800`038c84c1 : fffff880`0a9f7b18 fffff880`0a9f7370 fffff880`00000000 fffff880`0a9f7f40 : nt!RtlDispatchException+0x415
    fffff880`0a9f7340 fffff800`0388d242 : fffff880`0a9f7b18 fffff880`0a9f7f70 fffff880`0a9f7bc0 fffff880`0a9f7f90 : nt!KiDispatchException+0x135
    fffff880`0a9f79e0 fffff800`0388bdba : 00000000`00000000 00000000`00000010 00000000`00000000 fffff880`0a9f7f70 : nt!KiExceptionDispatch+0xc2
    fffff880`0a9f7bc0 fffff880`01dd86b3 : fffff880`00000000 fffff880`0a9f7dc8 00000000`00000000 fffff880`0a9f7f40 : nt!KiPageFault+0x23a (TrapFrame @ fffff880`0a9f7bc0)
    fffff880`0a9f7d50 fffff880`01de86a6 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000001 : ksecdd!KsecProcessSecurityContext+0x293
    fffff880`0a9f7e50 fffff880`02053c84 : 00000000`00000000 fffffa80`06c8ca0c fffffa80`073e0a00 00000000`00000000 : ksecdd!InitializeSecurityContextW+0x66
    fffff880`0a9f7eb0 fffff880`02054b0e : 00000000`0003a7f7 00000000`0003a7f7 00000000`00000100 01cf2dac`8e2a5464 : tcpip!WfpAlepCreateTokenFromLogonId+0x1c4
    fffff880`0a9f7fd0 fffff880`02053a02 : fffffa80`06f186c0 fffffa80`073e0ac0 fffffa80`06f186c0 fffffa80`0ae138b0 : tcpip!WfpAleCreateTokenFromLogonId+0x2e
    fffff880`0a9f8050 fffff880`02054075 : 00000000`00000000 fffffa80`073e0ac0 00000000`00000000 fffffa80`06f186c0 : tcpip!WfpAlepSetSecurity+0x282
    fffff880`0a9f8120 fffff880`0208ce5a : 0000a310`e54752bc fffff880`0a9f83c8 fffff880`0a9f8320 fffff880`0206d8d6 : tcpip!WfpAleProcessSecureSocketControl+0xa5
    fffff880`0a9f82b0 fffff880`02077cb9 : 00000000`00004800 fffff880`01e892a0 00000000`00000000 fffffa80`0bd10cf0 : tcpip!InetInspectSecureSocketControl+0x2a
    fffff880`0a9f8300 fffff880`02077137 : 00000000`00004800 fffff880`07a61160 fffffa80`0bd10d38 fffff880`0a9f8570 : tcpip!TcpSetSockOptEndpoint+0x4a9
    fffff880`0a9f8400 fffff800`03899878 : 80000800`00000000 80000800`00000001 00000000`00000000 00000000`00000000 : tcpip!TcpTlEndpointIoControlEndpointCalloutRoutine+0x107
    fffff880`0a9f8460 fffff880`020771c0 : fffff880`02077030 00000000`00000000 fffff880`01fa5500 00000000`00000001 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`0a9f8540 fffff880`07a61066 : fffffa80`073d7701 fffffa80`07237ee0 fffffa80`073d7710 00000000`00000000 : tcpip!TcpTlEndpointIoControlEndpoint+0x70
    fffff880`0a9f85b0 fffff880`07a606f0 : 00000000`980000c8 00000000`00000000 fffffa80`07237ee0 fffffa80`072461d0 : afd!WskProTLControlRequest+0x136
    fffff880`0a9f8640 fffff880`07a60b0b : fffffa80`0c795c10 fffffa80`07237ee0 fffffa80`072461d0 fffff800`03a33a28 : afd!WskProControlSocketCore+0x110
    fffff880`0a9f86c0 fffff880`09c836c0 : fffffa80`00000468 fffffa80`0c795c10 00000000`00000000 00000000`000007ff : afd!WskProAPIControlSocket+0x9b
    fffff880`0a9f8730 fffff880`09c82de6 : 00000000`00000001 fffff880`07a72400 00000000`00000000 00000000`00000700 : mrxsmb!SmbWskSetSocketOptions+0x1f0
    fffff880`0a9f87f0 fffff880`09c7b082 : fffffa80`0b203160 fffffa80`0c396201 00000000`00000080 fffffa80`0b203160 : mrxsmb!SmbWskInitiateAsynchronousConnect+0x1a6
    fffff880`0a9f8940 fffff880`09c813a9 : 00000000`00000000 00000000`00000004 fffffa80`0c3962f0 00000000`00000000 : mrxsmb!RxCeInitiateConnectRequest+0x52
    fffff880`0a9f8970 fffff880`09c81ba5 : fffff880`09c95f00 fffffa80`0c3962f0 fffff880`07b83110 00000000`aaaaaaaa : mrxsmb!RxCeBuildConnectionOverMultipleTransports+0x659
    fffff880`0a9f8b00 fffff880`07b691b1 : fffff880`07b844a8 00000000`00000080 fffff880`07b83110 fffffa80`0c396390 : mrxsmb!RxCeInitiateConnection+0x151
    fffff880`0a9f8b40 fffff800`03b2a2ea : fffff880`07b844a8 fffff880`07b848f8 fffff880`0a9f8c00 fffffa80`0ca8e600 : rdbss!RxpWorkerThreadDispatcher+0x1a1
    fffff880`0a9f8c00 fffff800`0387e8e6 : fffff800`03a08e80 fffffa80`0ca8e690 fffff800`03a16cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`0a9f8c40 00000000`00000000 : fffff880`0a9f9000 fffff880`0a9f3000 fffff880`0a9f6c50 00000000`00000000 : nt!KiStartSystemThread+0x16
    ^^ Various network routines... i.e - mrxsmb, afd, tcpip, kscedd, etc.

    Code:
    6: kd> .trap fffff880`0a9f7bc0
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=00000000002e0a70
    rdx=fffff8800a9f7de8 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88001dd86b3 rsp=fffff8800a9f7d50 rbp=0000000000000000
     r8=fffff8800a9f7e58  r9=00000000002e0a70 r10=fffffa8006d57d60
    r11=fffff8a0046c4000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac pe cy
    ksecdd!KsecProcessSecurityContext+0x293:
    Code:
    6: kd> u @rip
    ksecdd!KsecProcessSecurityContext+0x293:
    fffff880`01dd86b3 ff5010          call    qword ptr [rax+10h]
    fffff880`01dd86b6 448bf0          mov     r14d,eax
    fffff880`01dd86b9 85c0            test    eax,eax
    fffff880`01dd86bb 780d            js      ksecdd!KsecProcessSecurityContext+0x2aa (fffff880`01dd86ca)
    fffff880`01dd86bd 488b8c2408010000 mov     rcx,qword ptr [rsp+108h]
    fffff880`01dd86c5 49894c2408      mov     qword ptr [r12+8],rcx
    fffff880`01dd86ca 4585f6          test    r14d,r14d
    fffff880`01dd86cd 0f89e0feffff    jns     ksecdd!KsecProcessSecurityContext+0x193 (fffff880`01dd85b3)
    ^^ More mention of ksecdd!KsecProcessSecurityContext after some disassembly.

    This is very likely a driver (likely security related) causing network conflicts.

    -----------------

    1. Remove and replace BitDefender with Microsoft Security Essentials for temporary troubleshooting purposes:

    BitDefender removal - How to uninstall Bitdefender

    MSE - Microsoft Security Essentials - Microsoft Windows

    2. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

    3. If you're still crashing after both of the above, enable Driver Verifier:

    Driver Verifier:

    What is Driver Verifier?

    Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

    Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

    Before enabling Driver Verifier, it is recommended to create a System Restore Point:

    Vista - START | type rstrui - create a restore point
    Windows 7 - START | type create | select "Create a Restore Point"
    Windows 8 - Restore Point - Create in Windows 8

    How to enable Driver Verifier:

    Start > type "verifier" without the quotes > Select the following options -

    1. Select - "Create custom settings (for code developers)"
    2. Select - "Select individual settings from a full list"
    3. Check the following boxes -
    - Special Pool
    - Pool Tracking
    - Force IRQL Checking
    - Deadlock Detection
    - Security Checks (Windows 7 & 8)
    - DDI compliance checking (Windows 8)
    - Miscellaneous Checks
    4. Select - "Select driver names from a list"
    5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
    6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
    7. Click on Finish.
    8. Restart.

    Important information regarding Driver Verifier:

    - If Driver Verifier finds a violation, the system will BSOD.

    - After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

    If this happens, do not panic, do the following:

    - Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

    - Once in Safe Mode - Start > Search > type "cmd" without the quotes.

    - To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
    ・ Restart and boot into normal Windows.

    If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

    - Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

    - Once in Safe Mode - Start > type "system restore" without the quotes.

    - Choose the restore point you created earlier.

    How long should I keep Driver Verifier enabled for?

    It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

    My system BSOD'd, where can I find the crash dumps?

    They will be located in %systemroot%\Minidump

    Any other questions can most likely be answered by this article:
    Using Driver Verifier to identify issues with Windows drivers for advanced users

    Regards,

    Patrick

  8. #8
    sad's Avatar
    Join Date
    Feb 2014
    Location
    Lyon, France
    Posts
    8

    re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    Quote Originally Posted by Patrick View Post
    Thanks!

    All of the attached DMP files are of the KMODE_EXCEPTION_NOT_HANDLED (1e) bug check.

    This indicates that a kernel-mode program generated an exception which the error handler did not catch.

    BugCheck 1E, {ffffffffc0000005, fffff8800a9f6bf0, 0, 0}

    ^^ The 1st parameter is 0xc0000005 which indicates an access violation occurred, let's see what caused it:

    Code:
    6: kd> .exr 0xfffff8800a9f7b18
    ExceptionAddress: fffff88001dd86b3 (ksecdd!KsecProcessSecurityContext+0x0000000000000293)
       ExceptionCode: c0000005 (Access violation)
    If we take a look at the call stack:

    Code:
    6: kd> kv
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff880`0a9f6b38 fffff800`0391f1bb : 00000000`0000001e ffffffff`c0000005 fffff880`0a9f6bf0 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0a9f6b40 fffff800`038e0d18 : ffbca55a`ffbba359 ffbfa85d`ffbda75c ffc3ac61`ffc1aa5f ffc9b065`ffc7ae64 : nt!KipFatalFilter+0x1b
    fffff880`0a9f6b80 fffff800`038b8cdc : ffdac478`ffd9c376 ffdeca7c`ffddc97a ffe1cd7d`ffdfcc7d ffe3d181`ffe2cf7f : nt! ?? ::FNODOBFM::`string'+0x83d
    fffff880`0a9f6bc0 fffff800`038b875d : fffff800`039d9d74 fffff880`0a9f8460 00000000`00000000 fffff800`03818000 : nt!_C_specific_handler+0x8c
    fffff880`0a9f6c30 fffff800`038b7535 : fffff800`039d9d74 fffff880`0a9f6ca8 fffff880`0a9f7b18 fffff800`03818000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`0a9f6c60 fffff800`038c84c1 : fffff880`0a9f7b18 fffff880`0a9f7370 fffff880`00000000 fffff880`0a9f7f40 : nt!RtlDispatchException+0x415
    fffff880`0a9f7340 fffff800`0388d242 : fffff880`0a9f7b18 fffff880`0a9f7f70 fffff880`0a9f7bc0 fffff880`0a9f7f90 : nt!KiDispatchException+0x135
    fffff880`0a9f79e0 fffff800`0388bdba : 00000000`00000000 00000000`00000010 00000000`00000000 fffff880`0a9f7f70 : nt!KiExceptionDispatch+0xc2
    fffff880`0a9f7bc0 fffff880`01dd86b3 : fffff880`00000000 fffff880`0a9f7dc8 00000000`00000000 fffff880`0a9f7f40 : nt!KiPageFault+0x23a (TrapFrame @ fffff880`0a9f7bc0)
    fffff880`0a9f7d50 fffff880`01de86a6 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000001 : ksecdd!KsecProcessSecurityContext+0x293
    fffff880`0a9f7e50 fffff880`02053c84 : 00000000`00000000 fffffa80`06c8ca0c fffffa80`073e0a00 00000000`00000000 : ksecdd!InitializeSecurityContextW+0x66
    fffff880`0a9f7eb0 fffff880`02054b0e : 00000000`0003a7f7 00000000`0003a7f7 00000000`00000100 01cf2dac`8e2a5464 : tcpip!WfpAlepCreateTokenFromLogonId+0x1c4
    fffff880`0a9f7fd0 fffff880`02053a02 : fffffa80`06f186c0 fffffa80`073e0ac0 fffffa80`06f186c0 fffffa80`0ae138b0 : tcpip!WfpAleCreateTokenFromLogonId+0x2e
    fffff880`0a9f8050 fffff880`02054075 : 00000000`00000000 fffffa80`073e0ac0 00000000`00000000 fffffa80`06f186c0 : tcpip!WfpAlepSetSecurity+0x282
    fffff880`0a9f8120 fffff880`0208ce5a : 0000a310`e54752bc fffff880`0a9f83c8 fffff880`0a9f8320 fffff880`0206d8d6 : tcpip!WfpAleProcessSecureSocketControl+0xa5
    fffff880`0a9f82b0 fffff880`02077cb9 : 00000000`00004800 fffff880`01e892a0 00000000`00000000 fffffa80`0bd10cf0 : tcpip!InetInspectSecureSocketControl+0x2a
    fffff880`0a9f8300 fffff880`02077137 : 00000000`00004800 fffff880`07a61160 fffffa80`0bd10d38 fffff880`0a9f8570 : tcpip!TcpSetSockOptEndpoint+0x4a9
    fffff880`0a9f8400 fffff800`03899878 : 80000800`00000000 80000800`00000001 00000000`00000000 00000000`00000000 : tcpip!TcpTlEndpointIoControlEndpointCalloutRoutine+0x107
    fffff880`0a9f8460 fffff880`020771c0 : fffff880`02077030 00000000`00000000 fffff880`01fa5500 00000000`00000001 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`0a9f8540 fffff880`07a61066 : fffffa80`073d7701 fffffa80`07237ee0 fffffa80`073d7710 00000000`00000000 : tcpip!TcpTlEndpointIoControlEndpoint+0x70
    fffff880`0a9f85b0 fffff880`07a606f0 : 00000000`980000c8 00000000`00000000 fffffa80`07237ee0 fffffa80`072461d0 : afd!WskProTLControlRequest+0x136
    fffff880`0a9f8640 fffff880`07a60b0b : fffffa80`0c795c10 fffffa80`07237ee0 fffffa80`072461d0 fffff800`03a33a28 : afd!WskProControlSocketCore+0x110
    fffff880`0a9f86c0 fffff880`09c836c0 : fffffa80`00000468 fffffa80`0c795c10 00000000`00000000 00000000`000007ff : afd!WskProAPIControlSocket+0x9b
    fffff880`0a9f8730 fffff880`09c82de6 : 00000000`00000001 fffff880`07a72400 00000000`00000000 00000000`00000700 : mrxsmb!SmbWskSetSocketOptions+0x1f0
    fffff880`0a9f87f0 fffff880`09c7b082 : fffffa80`0b203160 fffffa80`0c396201 00000000`00000080 fffffa80`0b203160 : mrxsmb!SmbWskInitiateAsynchronousConnect+0x1a6
    fffff880`0a9f8940 fffff880`09c813a9 : 00000000`00000000 00000000`00000004 fffffa80`0c3962f0 00000000`00000000 : mrxsmb!RxCeInitiateConnectRequest+0x52
    fffff880`0a9f8970 fffff880`09c81ba5 : fffff880`09c95f00 fffffa80`0c3962f0 fffff880`07b83110 00000000`aaaaaaaa : mrxsmb!RxCeBuildConnectionOverMultipleTransports+0x659
    fffff880`0a9f8b00 fffff880`07b691b1 : fffff880`07b844a8 00000000`00000080 fffff880`07b83110 fffffa80`0c396390 : mrxsmb!RxCeInitiateConnection+0x151
    fffff880`0a9f8b40 fffff800`03b2a2ea : fffff880`07b844a8 fffff880`07b848f8 fffff880`0a9f8c00 fffffa80`0ca8e600 : rdbss!RxpWorkerThreadDispatcher+0x1a1
    fffff880`0a9f8c00 fffff800`0387e8e6 : fffff800`03a08e80 fffffa80`0ca8e690 fffff800`03a16cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`0a9f8c40 00000000`00000000 : fffff880`0a9f9000 fffff880`0a9f3000 fffff880`0a9f6c50 00000000`00000000 : nt!KiStartSystemThread+0x16
    ^^ Various network routines... i.e - mrxsmb, afd, tcpip, kscedd, etc.

    Code:
    6: kd> .trap fffff880`0a9f7bc0
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=00000000002e0a70
    rdx=fffff8800a9f7de8 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88001dd86b3 rsp=fffff8800a9f7d50 rbp=0000000000000000
     r8=fffff8800a9f7e58  r9=00000000002e0a70 r10=fffffa8006d57d60
    r11=fffff8a0046c4000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac pe cy
    ksecdd!KsecProcessSecurityContext+0x293:
    Code:
    6: kd> u @rip
    ksecdd!KsecProcessSecurityContext+0x293:
    fffff880`01dd86b3 ff5010          call    qword ptr [rax+10h]
    fffff880`01dd86b6 448bf0          mov     r14d,eax
    fffff880`01dd86b9 85c0            test    eax,eax
    fffff880`01dd86bb 780d            js      ksecdd!KsecProcessSecurityContext+0x2aa (fffff880`01dd86ca)
    fffff880`01dd86bd 488b8c2408010000 mov     rcx,qword ptr [rsp+108h]
    fffff880`01dd86c5 49894c2408      mov     qword ptr [r12+8],rcx
    fffff880`01dd86ca 4585f6          test    r14d,r14d
    fffff880`01dd86cd 0f89e0feffff    jns     ksecdd!KsecProcessSecurityContext+0x193 (fffff880`01dd85b3)
    ^^ More mention of ksecdd!KsecProcessSecurityContext after some disassembly.

    This is very likely a driver (likely security related) causing network conflicts.

    -----------------

    1. Remove and replace BitDefender with Microsoft Security Essentials for temporary troubleshooting purposes:

    BitDefender removal - How to uninstall Bitdefender

    MSE - Microsoft Security Essentials - Microsoft Windows

    2. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

    3. If you're still crashing after both of the above, enable Driver Verifier:

    Driver Verifier:

    What is Driver Verifier?

    Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

    Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

    Before enabling Driver Verifier, it is recommended to create a System Restore Point:

    Vista - START | type rstrui - create a restore point
    Windows 7 - START | type create | select "Create a Restore Point"
    Windows 8 - Restore Point - Create in Windows 8

    How to enable Driver Verifier:

    Start > type "verifier" without the quotes > Select the following options -

    1. Select - "Create custom settings (for code developers)"
    2. Select - "Select individual settings from a full list"
    3. Check the following boxes -
    - Special Pool
    - Pool Tracking
    - Force IRQL Checking
    - Deadlock Detection
    - Security Checks (Windows 7 & 8)
    - DDI compliance checking (Windows 8)
    - Miscellaneous Checks
    4. Select - "Select driver names from a list"
    5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
    6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
    7. Click on Finish.
    8. Restart.

    Important information regarding Driver Verifier:

    - If Driver Verifier finds a violation, the system will BSOD.

    - After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

    If this happens, do not panic, do the following:

    - Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

    - Once in Safe Mode - Start > Search > type "cmd" without the quotes.

    - To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
    ・ Restart and boot into normal Windows.

    If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

    - Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

    - Once in Safe Mode - Start > type "system restore" without the quotes.

    - Choose the restore point you created earlier.

    How long should I keep Driver Verifier enabled for?

    It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

    My system BSOD'd, where can I find the crash dumps?

    They will be located in %systemroot%\Minidump

    Any other questions can most likely be answered by this article:
    Using Driver Verifier to identify issues with Windows drivers for advanced users

    Regards,

    Patrick

    System.zip
    Hi BlueRobot, thanks for helping me.
    You'll find the ZIP attached.

    Patrick, i desinstal daemon and bit defender, i clean my register with Ccleaner, but BSOD still here, i need to come to safe mode to upload the report attached.
    I start driver verifier.

  9. #9
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    16,153
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    Did the system BSOD after Driver Verifier was enabled?

    If so, please copy the most recent dump file from c:\windows\minidump to Documents; zip up the dump file and attach to your next post.

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015
    Windows Insider MVP 2018 - Present

  10. #10
    sad's Avatar
    Join Date
    Feb 2014
    Location
    Lyon, France
    Posts
    8

    re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    Quote Originally Posted by jcgriff2 View Post
    Did the system BSOD after Driver Verifier was enabled?

    If so, please copy the most recent dump file from c:\windows\minidump to Documents; zip up the dump file and attach to your next post.
    Minidump.rar
    Hi jcgriff2,

    so my computer does not go to BSOD, but it freeze when I mount an ISO, or if I try to upload my zip here... . The problem changes, is it a good think?
    You'll find the minidump attached.
    If I reinstal from factory, do you think it will resolve the problem?
    Can i stop driver verifier?

  11. #11
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    16,153
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    Hi -

    Turn Driver Verifier off. Bring up an Admin CMD prompt and type/paste -
    Code:
    verifier /reset
    Reboot.

    Boot into Safemode w/ Networking - tap F8 key repeatedly during boot-up.

    Upload the same zip file from your last post while in Safemode to your reply post.

    Is there any freezing?

    A reinstall of Windows may help us determine if the problem lies with software or hardware, but I'd like to hear about the safemode test first, please.

    Did Windows 7 come with the system or did you purchase a full retail copy?

    Regards. . .

    jcgriff2





    BSOD SUMMARY
    Code:
    
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\022114-24944-01.dmp]
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Fri Feb 21 12:53:16.374 2014 (UTC - 5:00)
    System Uptime: 0 days 0:12:02.202
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff880`09ccbbf0 00000000`00000000 00000000`00000000
    BiosVersion = P01-A3
    BiosReleaseDate = 04/19/2011
    SystemManufacturer = Acer
    SystemProductName = Predator G3610
    MaxSpeed:     3400
    CurrentSpeed: 3392
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021914-28860-01.dmp]
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Wed Feb 19 13:50:35.979 2014 (UTC - 5:00)
    System Uptime: 0 days 0:12:05.807
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff880`0a9f6bf0 00000000`00000000 00000000`00000000
    BiosVersion = P01-A3
    BiosReleaseDate = 04/19/2011
    SystemManufacturer = Acer
    SystemProductName = Predator G3610
    MaxSpeed:     3400
    CurrentSpeed: 3392
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021914-22978-01.dmp]
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Wed Feb 19 11:53:55.226 2014 (UTC - 5:00)
    System Uptime: 0 days 0:08:49.053
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff880`0800bbf0 00000000`00000000 00000000`00000000
    BiosVersion = P01-A3
    BiosReleaseDate = 04/19/2011
    SystemManufacturer = Acer
    SystemProductName = Predator G3610
    MaxSpeed:     3400
    CurrentSpeed: 3392
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021914-20139-01.dmp]
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Wed Feb 19 09:26:29.710 2014 (UTC - 5:00)
    System Uptime: 0 days 9:37:34.538
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff880`0731abf0 00000000`00000000 00000000`00000000
    BiosVersion = P01-A3
    BiosReleaseDate = 04/19/2011
    SystemManufacturer = Acer
    SystemProductName = Predator G3610
    MaxSpeed:     3400
    CurrentSpeed: 3392
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021814-16458-01.dmp]
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Tue Feb 18 12:45:52.477 2014 (UTC - 5:00)
    System Uptime: 0 days 0:03:17.305
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff880`09e4dbf0 00000000`00000000 00000000`00000000
    BiosVersion = P01-A3
    BiosReleaseDate = 04/19/2011
    SystemManufacturer = Acer
    SystemProductName = Predator G3610
    MaxSpeed:     3400
    CurrentSpeed: 3392
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021814-15490-01.dmp]
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Tue Feb 18 12:41:48.973 2014 (UTC - 5:00)
    System Uptime: 0 days 0:04:34.689
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff880`09e67bf0 00000000`00000000 00000000`00000000
    BiosVersion = P01-A3
    BiosReleaseDate = 04/19/2011
    SystemManufacturer = Acer
    SystemProductName = Predator G3610
    MaxSpeed:     3400
    CurrentSpeed: 3392
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021814-16036-01.dmp]
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Tue Feb 18 12:36:23.481 2014 (UTC - 5:00)
    System Uptime: 0 days 22:51:45.309
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff880`09d75bf0 00000000`00000000 00000000`00000000
    BiosVersion = P01-A3
    BiosReleaseDate = 04/19/2011
    SystemManufacturer = Acer
    SystemProductName = Predator G3610
    MaxSpeed:     3400
    CurrentSpeed: 3392
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021714-45006-01.dmp]
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Mon Feb 17 13:43:43.518 2014 (UTC - 5:00)
    System Uptime: 0 days 0:19:53.346
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff880`07b94bf0 00000000`00000000 00000000`00000000
    BiosVersion = P01-A3
    BiosReleaseDate = 04/19/2011
    SystemManufacturer = Acer
    SystemProductName = Predator G3610
    MaxSpeed:     3400
    CurrentSpeed: 3392
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021714-15896-01.dmp]
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Mon Feb 17 13:10:45.788 2014 (UTC - 5:00)
    System Uptime: 0 days 0:04:52.616
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff880`07943bf0 00000000`00000000 00000000`00000000
    BiosVersion = P01-A3
    BiosReleaseDate = 04/19/2011
    SystemManufacturer = Acer
    SystemProductName = Predator G3610
    MaxSpeed:     3400
    CurrentSpeed: 3392
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021714-15927-01.dmp]
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Mon Feb 17 12:40:31.220 2014 (UTC - 5:00)
    System Uptime: 0 days 0:06:12.048
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff880`079f0bf0 00000000`00000000 00000000`00000000
    BiosVersion = P01-A3
    BiosReleaseDate = 04/19/2011
    SystemManufacturer = Acer
    SystemProductName = Predator G3610
    MaxSpeed:     3400
    CurrentSpeed: 19222
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021714-51464-01.dmp]
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Mon Feb 17 12:33:36.277 2014 (UTC - 5:00)
    System Uptime: 0 days 0:02:43.104
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff880`07537bf0 00000000`00000000 00000000`00000000
    BiosVersion = P01-A3
    BiosReleaseDate = 04/19/2011
    SystemManufacturer = Acer
    SystemProductName = Predator G3610
    MaxSpeed:     3400
    CurrentSpeed: 3392
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021714-22713-01.dmp]
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Mon Feb 17 12:07:24.846 2014 (UTC - 5:00)
    System Uptime: 0 days 0:30:50.674
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff880`03f9dbf0 00000000`00000000 00000000`00000000
    BiosVersion = P01-A3
    BiosReleaseDate = 04/19/2011
    SystemManufacturer = Acer
    SystemProductName = Predator G3610
    MaxSpeed:     3400
    CurrentSpeed: 3392
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021714-20498-01.dmp]
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Mon Feb 17 11:35:42.036 2014 (UTC - 5:00)
    System Uptime: 1 days 3:40:40.864
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff880`078d6bf0 00000000`00000000 00000000`00000000
    BiosVersion = P01-A3
    BiosReleaseDate = 04/19/2011
    SystemManufacturer = Acer
    SystemProductName = Predator G3610
    MaxSpeed:     3400
    CurrentSpeed: 3392
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020714-24804-01.dmp]
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Fri Feb  7 14:37:05.196 2014 (UTC - 5:00)
    System Uptime: 0 days 0:08:35.024
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff880`099c3bf0 00000000`00000000 00000000`00000000
    BiosVersion = P01-A3
    BiosReleaseDate = 04/19/2011
    SystemManufacturer = Acer
    SystemProductName = Predator G3610
    MaxSpeed:     3400
    CurrentSpeed: 3392
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020714-22464-01.dmp]
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Fri Feb  7 14:27:39.231 2014 (UTC - 5:00)
    System Uptime: 0 days 0:11:02.059
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff880`09cfebf0 00000000`00000000 00000000`00000000
    BiosVersion = P01-A3
    BiosReleaseDate = 04/19/2011
    SystemManufacturer = Acer
    SystemProductName = Predator G3610
    MaxSpeed:     3400
    CurrentSpeed: 3392
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020714-31839-01.dmp]
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Fri Feb  7 14:15:42.076 2014 (UTC - 5:00)
    System Uptime: 1 days 12:33:31.793
    Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff880`09e04bf0 00000000`00000000 00000000`00000000
    BiosVersion = P01-A3
    BiosReleaseDate = 04/19/2011
    SystemManufacturer = Acer
    SystemProductName = Predator G3610
    MaxSpeed:     3400
    CurrentSpeed: 3392
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
      
    
    	    
                 
           J. C. Griffith, Microsoft MVP (jcgriff2)   
                 
               http://mvp.microsoft.com/en-us/mvp/John%20C.%20Griffith-4025562   
    
               www.sysnative.com
                 
               www.jcgriff2.com 
    
    
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    
    
      

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015
    Windows Insider MVP 2018 - Present

  12. #12
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    16,153
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    Quote Originally Posted by sad View Post
    ...So I try Sysnative jcgriff2 BSOD File Collection app and it's repeating " Waiting for SystemInfo". It's been 1h30 i'm waiting it's finish ... I let it during the night (because it's 20h here ^^, don't know where you're from ^^).
    0.2
    For info, the jcgriff2 app was waiting for msinfo32 to finish.

    Please go to your Documents folder & zip up the entire Windows7_Vista_jcgriff2 folder & attach to your next post.

    Regards. . .

    jcgriff2

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015
    Windows Insider MVP 2018 - Present

  13. #13
    sad's Avatar
    Join Date
    Feb 2014
    Location
    Lyon, France
    Posts
    8

    re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    Quote Originally Posted by jcgriff2
    For info, the jcgriff2 app was waiting for msinfo32 to finish.

    Please go to your Documents folder & zip up the entire Windows7_Vista_jcgriff2 folder & attach to your next post.

    Regards. . .

    jcgriff2
    Attachment 7138

    Hi jcgriff2,

    I'm sorry, i didn't know where I can find the report ... you'll find the zip attached.
    Yesterday when I upload the last zip, i was in safe mode and no freeze in safe mode. Today the same, the freeze appears only in normal mode.
    Windows 7 was already installed on the computer when I bought it. It's an official version with no modification.

    Regards
    Last edited by jcgriff2; 02-22-2014 at 06:44 PM. Reason: fix BB tags

  14. #14
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    16,153
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    Quote Originally Posted by sad View Post
    ......the freeze appears only in normal mode.
    If that's the case, it seems that software may be the culprit.

    Run Driver Verifier again -- let it run for 24 hours minimum.

    You can use the system, but it may be very slow.


    Regards. . .

    jcgriff2

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015
    Windows Insider MVP 2018 - Present

  15. #15
    sad's Avatar
    Join Date
    Feb 2014
    Location
    Lyon, France
    Posts
    8

    re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    Quote Originally Posted by jcgriff2 View Post
    Quote Originally Posted by sad View Post
    ......the freeze appears only in normal mode.
    If that's the case, it seems that software may be the culprit.

    Run Driver Verifier again -- let it run for 24 hours minimum.

    You can use the system, but it may be very slow.

    Regards. . .

    jcgriff2
    Hi jcgriff2,

    so Drivers verifier is on til your last message.
    I see one thing, my computer freeze only when you open a window to select a file. Example: iso that I want to mount, Image that I want to upload or a file file that I want to attached in a mail....

  16. #16
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    16,153
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    Let Driver Verifier run 24 hours minimum & see if it BSODs your system.

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015
    Windows Insider MVP 2018 - Present

  17. #17
    sad's Avatar
    Join Date
    Feb 2014
    Location
    Lyon, France
    Posts
    8

    Re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    Hi all,
    so I reinstal Windows from factory, and my problem disappear.
    Thank you all for your help and your patient.

  18. #18

    Re: BSOD when mount on virtual drive - Windows 7 x64 SP1

    That's definitely one way to do it! Glad to hear your issues stopped.

    Regards,

    Patrick

Similar Threads

  1. Cannot restore system on new hard drive using USB recovery drive
    By usasma in forum Windows 8 | Windows RT
    Replies: 3
    Last Post: 02-23-2014, 08:10 AM
  2. Check Virtual Memory Usage with WMI (Windows 7/ Vista)
    By jcgriff2 in forum BSOD Kernel Dump Analysis Debugging Information
    Replies: 0
    Last Post: 10-26-2012, 03:33 AM
  3. Check Virtual Memory Usage with WMI (Windows 7/ Vista)
    By jcgriff2 in forum Windows 7 | Windows Vista Tutorials
    Replies: 0
    Last Post: 10-26-2012, 03:33 AM
  4. Replies: 0
    Last Post: 06-25-2012, 08:48 PM
  5. Windows 8 UX fundamentals–free virtual training
    By JMH in forum Microsoft News
    Replies: 0
    Last Post: 06-13-2012, 12:54 AM

Log in

Log in