Freezing followed by BSOD when writing to a file

Page 2 of 4 FirstFirst 1234 LastLast

  1. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #11

    Pauly said:
    Should the system reserved partition be assigned a drive letter ??
    Normally i would say no but have no knowledge/experience of paragon part manager so dont know if this is something that it has changed especially with it being over 200MB, dual boot ?
    Sharp noticed, my friend :)
    Really, 227 is an odd figure, it should be either 100 MB or 300 MB and another 100+ MB for UEFI ....

    I am also guessing he has done something there with the bootloader.
      My Computer


  2. Posts : 22
    Windows 7 Professional x64
    Thread Starter
       #12

    Arc said:
    Thank you lots for all the help, Steve

    daviga 404, Your BSOD is APC_INDEX_MISMATCH, BugCheck 1. In most of the cases I have seen it, it is caused by any antivirus/firewall software. Let us see what it shows in your crash dump.

    A deeper search reveals that it is caused by COMODO Firewall Pro Sandbox Driver.
    Code:
    fffff880`09a5e468  fffff880`01221e24Unable to load image \SystemRoot\System32\DRIVERS\cmdguard.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for cmdguard.sys
    *** ERROR: Module load completed but symbols could not be loaded for cmdguard.sys
     cmdguard+0x6e24
    Description here: Driver Reference Table - cmdguard.sys

    If you want to get rid of the BSODs, I'd suggest you to uninstall Comodo. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
    Download, install and update those, and then run full system scans with both of them, one by one.

    Also make it sure that your ADATA S511 SSD is having the latest firmware.

    Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus.
    5. Apply > OK
    6. Accept then restart.

    Let us know the results.
    ________________________________________________________________________________
    BSOD ANALYSIS:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1, {76d5040a, 0, ffff, fffff88009a5eca0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
    
    Followup: MachineOwner
    ---------
    
    0: 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->CombinedApcDisable field. This consists of two separate 16-bit
    fields, the SpecialApcDisable and the KernelApcDisable. A negative value
    of either indicates that a driver has disabled special or normal APCs
    (respectively) without re-enabling them; a positive value indicates that
    a driver has enabled special or normal APCs (respectively) too many times.
    Arguments:
    Arg1: 0000000076d5040a, Address of system call function or worker routine
    Arg2: 0000000000000000, Thread->ApcStateIndex
    Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
    Arg4: fffff88009a5eca0, Call type (0 - system call, 1 - worker routine)
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    +0
    00000000`76d5040a ??              ???
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002ad4469 to fffff80002ad4f00
    
    STACK_TEXT:  
    fffff880`09a5ea68 fffff800`02ad4469 : 00000000`00000001 00000000`76d5040a 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
    fffff880`09a5ea70 fffff800`02ad43a0 : ffffffff`ffffffff 00000000`00000001 00000000`009d9b20 fffff800`0000007a : nt!KiBugCheckDispatch+0x69
    fffff880`09a5ebb0 00000000`76d5040a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
    00000000`016fd1c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d5040a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiSystemServiceExit+245
    fffff800`02ad43a0 4883ec50        sub     rsp,50h
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiSystemServiceExit+245
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    
    FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_52_nt!KiSystemServiceExit+245
    
    BUCKET_ID:  X64_0x1_SysCallNum_52_nt!KiSystemServiceExit+245
    
    Followup: MachineOwner
    ---------
    Actually, I used to have Commodo but uninstalled it a while ago, which seems confusing to me as the driver shouldn't still be there, right? I have Avast! Antivirus and just the bog-standard Windows Firewall installed, at the minute.

    I do have the latest firmware on my SSD as essenbe recommended me to get, and I also cleaned the startup in MsConfig not too long ago.
      My Computer


  3. Posts : 22
    Windows 7 Professional x64
    Thread Starter
       #13

    Arc said:
    Pauly said:
    Should the system reserved partition be assigned a drive letter ??
    Normally i would say no but have no knowledge/experience of paragon part manager so dont know if this is something that it has changed especially with it being over 200MB, dual boot ?
    Sharp noticed, my friend :)
    Really, 227 is an odd figure, it should be either 100 MB or 300 MB and another 100+ MB for UEFI ....

    I am also guessing he has done something there with the bootloader.
    I left the drive as is - the same thing happened on my previous install of Windows when I used Paragon, and it did have a drive letter assigned too. Is it safe to just delete the partition?
      My Computer


  4. Posts : 26,863
    Windows 11 Pro
       #14

    Pauly, according to the OP, it is a file created by Partition Manager and was supposed to be deleted by Partition Manager after it had finished, but was not. He decided to leave it, as it caused him no problem. Regardless of it's name, it is not active, so should cause no problem, I guess. Perhaps it was left there to confuse me.
      My Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #15

    daviga404 said:

    I left the drive as is - the same thing happened on my previous install of Windows when I used Paragon, and it did have a drive letter assigned too. Is it safe to just delete the partition?
    No! Leave it as it is. Let us know how the computer is running after taking the suggested changes.
      My Computer


  6. Posts : 22
    Windows 7 Professional x64
    Thread Starter
       #16

    Well - problem is still persistent. Exactly the same scenario and blue screen. Turns out installing firmware didn't fix it :|
      My Computer


  7. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #17
      My Computer


  8. Posts : 22
    Windows 7 Professional x64
    Thread Starter
       #18

    Arc said:
    Attached
      My Computer


  9. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #19

    No new BSOD is there.

    Attachment 274661
      My Computer


  10. Posts : 22
    Windows 7 Professional x64
    Thread Starter
       #20

    Arc said:
    No new BSOD is there.

    Attachment 274661
    That seems odd - there definitely was a crash, and I'm fairly sure there was another blue screen. Anyway, that is all the Diagnostic Tool gave me.

    The crash appears in Event Log:
      My Computer


 
Page 2 of 4 FirstFirst 1234 LastLast

  Related Discussions
Our Sites
Site Links
About 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 07:10.
Find Us