BSOD/Restart at random - Kernel-Power (41)


  1. Posts : 6
    Windows 7 (64-bit)
       #1

    BSOD/Restart at random - Kernel-Power (41)


    Hi everyone, I've been having this problem for a while and can't seem to find the cause of it.
    I'm using an ACER 2920z laptop which came with Vista 32 and I've upgraded to Windows 7 64. This was a fresh install in January, and I saved an image of it - I have tried re-imaging but to no avail.

    I have a process (I think its a process) called sentinel 64 which gives errors but I can't work out how to stop it running.

    The restarts seem to happen more often when the computer is idle but has also happened while browsing the web. Files requested attached.

    Thank you for reading
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    LoadedScissor said:
    Hi everyone, I've been having this problem for a while and can't seem to find the cause of it.
    I'm using an ACER 2920z laptop which came with Vista 32 and I've upgraded to Windows 7 64. This was a fresh install in January, and I saved an image of it - I have tried re-imaging but to no avail.

    I have a process (I think its a process) called sentinel 64 which gives errors but I can't work out how to stop it running.

    The restarts seem to happen more often when the computer is idle but has also happened while browsing the web. Files requested attached.

    Thank you for reading
    No dump files are attached, did you run any system cleaner(such as Clceaner) after the crash?
    If so wait for the computer to BSOD and re-upload the file

    Here is some info for removing the Sentinel64 driver
    http://www.safenet-inc.com/support-d...tinel-drivers/
      My Computer


  3. Posts : 6
    Windows 7 (64-bit)
    Thread Starter
       #3

    Hi Yowanvista,

    Thank you for the quick reply.

    Sorry I thought that crash dumps were included automatically by running the "Windows_NT6_BSOD_v3.03_jcgriff2_" program (the output of which is included in the first post).

    Please find attached a collection of mini-dump files. These mini dumps seem to be related to another blue screen issue when I was checking drivers using "verifier" and were located in C:\Windows\Minidump. I can't find the mini dumps relating to the kernel minidumps based on time stamp. Is there another location I should check ?
      My Computer


  4. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #4

    These BSODs were all caused by Zone Alarm software Firewall/Security Suite, use the Removal Tool to completely remove such Software
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
        the operating system. The only supported way to extend a kernel
        mode stack is by using KeExpandKernelStackAndCallout.
    Arg2: 0000000000000002
    Arg3: fffff80002c53c40
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc4_91
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002b3195d to fffff80002acb740
    
    STACK_TEXT:  
    fffff800`00b9be58 fffff800`02b3195d : 00000000`000000c4 00000000`00000091 00000000`00000002 fffff800`02c53c40 : nt!KeBugCheckEx
    fffff800`00b9be60 fffff880`01877882 : fffff880`01877d80 fffff800`00b9bf70 fffffa80`02f0b302 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1e30d
    fffff800`00b9bf40 fffff880`0172e0eb : fffffa80`05744540 00000000`00000000 fffffa80`02ed41a0 fffffa80`02ed41a0 : tcpip!FlReceiveNetBufferListChain+0xb2
    fffff800`00b9bfb0 fffff880`016f7fc6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!NdisIMInitializeDeviceInstance+0xb5b
    fffff800`00b9c020 fffff880`0167aa24 : fffffa80`02ed41a0 00000000`00000002 00000000`00000001 fffff800`02c45e80 : ndis!NdisIMNotifyPnPEvent+0x1926
    fffff800`00b9c4a0 fffff880`0167a9e9 : fffffa80`05758010 00000000`00000001 00000000`00000001 fffff880`020f43f2 : ndis!NdisFIndicateReceiveNetBufferLists+0xf4
    fffff800`00b9c4e0 fffff880`0167a980 : fffff880`0210b5c0 00000000`00000000 ffff0080`036ca1d9 00000000`00000000 : ndis!NdisFIndicateReceiveNetBufferLists+0xb9
    fffff800`00b9c520 fffff880`03d0bba5 : fffffa80`05742010 00000000`00000000 00000000`00000001 fffffa80`01a5cab0 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
    fffff800`00b9c560 fffffa80`05742010 : 00000000`00000000 00000000`00000001 fffffa80`01a5cab0 00000000`00000000 : vsdatant+0x19ba5
    fffff800`00b9c568 00000000`00000000 : 00000000`00000001 fffffa80`01a5cab0 00000000`00000000 fffffa80`03f0504c : 0xfffffa80`05742010
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    vsdatant+19ba5
    fffff880`03d0bba5 ??              ???
    
    SYMBOL_STACK_INDEX:  8
    
    SYMBOL_NAME:  vsdatant+19ba5
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: vsdatant
    
    IMAGE_NAME:  vsdatant.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4be6e2ca
    
    FAILURE_BUCKET_ID:  X64_0xc4_91_vsdatant+19ba5
    
    BUCKET_ID:  X64_0xc4_91_vsdatant+19ba5
    
    Followup: MachineOwner
    ---------
       Information

    Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
    You can use MagicDisc as an alternative.


    Code:
    sptd.sys        fffff880`01041000    fffff880`01167000    0x00126000    0x4ad24632    12/10/2009 00:55:14
      My Computer


  5. Posts : 6
    Windows 7 (64-bit)
    Thread Starter
       #5

    Thanks for the quick reply again Yowanvista.

    I've uninstalled Zonealarm and installed Comodo, and also used the link to remove Sentinel64. I've had problems with Magic Disc in the past are there any other alternatives to deamon tools you could recomend ?

    I still seem to get the kernel power 41 (63) error especially if the computer is left idle for 20-30 minutes, though no mini dump is generated. I followed a guide which suggested changing to a small memory dump from kernel memory dump and not too restart automatically yet that still won't give a minidump and the PC still restarts, sometimes you don't even see a blue screen though it is recorded in the event viewer.

    Your help is much appreciated. Thank you.
      My Computer


  6. Posts : 6
    Windows 7 (64-bit)
    Thread Starter
       #6

    [SOLUTION]
    Just as an update for anyone who finds this problem. My Kernel power 41 (63) error was fixed by updating the driver for my wireless card (Intel 4965 AGN) using intels website (the most up to date driver on windows update still caused the problem to occur)

    [SOLUTION]
      My Computer


 

  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:13.
Find Us