Jump to content

Littlemutt

Members
  • Content Count

    10
  • Joined

  • Last visited

About Littlemutt

  • Rank
    Member
  • Birthday 01/01/1970
  1. Littlemutt

    v5 question

    I posted to another thread this: Guess its not related to version I"m using...
  2. Littlemutt

    dealing with lack of x86 driver

    Shame this seems to have been kicking around for several months now, and still not fixed. Once again, I gave up and un-installed SAS. Uninstalled it before when they could not find/fix the issue with Nividia cards causing spikes in the CPU. Now have a new machine, Vista64 HP SP2 with ATI card, so came back to try out SAS only to find yet another long-standing bug.
  3. Littlemutt

    Windows Vista Compatibility

    If its during initial setup and you check the box 'do not protect my homepage' or whatever it says, then its been around off and on for awhile.
  4. Littlemutt

    Any timeline for full vista compatability?

    Sadly, with the new 'pre-build', the spiking is still present.
  5. Littlemutt

    High CPU Usage

    Well, sad to report, using the latest 'pre-build', that at least on my system, while the CPU spikes are lower than before, they are Still present at a 1 sec rate spiking to 17%. Vista HP SP1 Nvidia video card 7300GT 512meg latest drivers AMD 1.4ghz Thunderbird CPU 1gig RAM
  6. Littlemutt

    Any timeline for full vista compatability?

    ooh, where is the download for this, I'm willing to test the Nvidia issue
  7. Littlemutt

    High CPU Usage

    Just tried the latest beta or pre-release 4.21.1004, and the issue with Nvidia is still present.
  8. Littlemutt

    Superantispyware causes computer to reboot

    Grrr, OK, thanks... back to the drawing board. Funny thing is only seems to crash with SAS running. I have rolled back to an older build 4.0.1154, will see what happens.
  9. Littlemutt

    Superantispyware causes computer to reboot

    Add me to the list of those getting BSOD's with SAS active. I started getting them about a month ago out of the blue after not having any in over a year of running Vista HP , now with SP1. I thought at first it was my video driver, so it was updated and was running without 'extra' programs for awhile till I thought the system was stable. I started up SAS yesterday morning, updated and started a manual quick-scan and went to get a haircut. Came home to find BSOD. Left if off for a few hours, then ran manual scans of registry and memory, all clean no crashes. I disabled the scheduled scan so it wouldn't run. Then, 4 hrs later while doing nothing on the PC it crashed to BSOD. I'm still struggling with Vista, and looking through the event manager I'm not having any luck finding the dumps from the BSOD. Any help would be great. I'm running the latest version, and have a Lifetime subscription. EDIT to add minidump: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: 8013c000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: SUPERANTISPYWAR CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 00000000 to 90d4d90a STACK_TEXT: 81772ce8 00000000 fecaa1f8 0000000e 00000000 win32k!EngBitBlt+0x21e1 STACK_COMMAND: kb FOLLOWUP_IP: win32k!EngBitBlt+21e1 90d4d90a 53 push ebx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: win32k!EngBitBlt+21e1 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 47c78851 FAILURE_BUCKET_ID: 0x7f_8_win32k!EngBitBlt+21e1 BUCKET_ID: 0x7f_8_win32k!EngBitBlt+21e1 Followup: MachineOwner ---------
×