Windows 7 Bluescreen Dump Product 768_1


  1. Posts : 9
    windows 7
       #1

    Windows 7 Bluescreen Dump Product 768_1


    I have zero experience at analyzing dump files. I restored by OS back to the initial Windows 7 update and the problem went away. I am sure because Windows 7 compatibility issues with hardware items on my machine or with applications I am running, this bluescreen dump issue has re-emerged this morning. It's terribly frustrating to have an issue like this and not have the experience to resolve it. My expectations are that Windows 7 diagnostics will assist with analyzing or resolving the issue, but I have not been able to find a diagnostic that will tell me anything meaningful. so this morning here I am with the following issue:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.768.3
    Locale ID: 1033
    Additional information about the problem:
    BCCode: 1000008e
    BCP1: C0000046
    BCP2: 82E5E8D8
    BCP3: A19E8568
    BCP4: 00000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1
    Files that help describe the problem:
    C:\Windows\Minidump\110109-21590-01.dmp
    C:\Users\DellXPS\AppData\Local\Temp\WER-154347-0.sysdata.xml
    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?link...8&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

    What is product 768_1... this makes absolutely no sense to me. is this a hardware driver issue? is this an application issue, is this an Windows 7 issue? Is this a registry issue?

    Again, I have NO experience with analyzing this situation and I am unfamiliar with the tools. Could you please provide some guidance (in English) written for someone who knows absolutely nothing about running diagnostics because my previous Vista OS ran perfectly.

    Attached is the zip of the dump file

    Thanks,

      My Computer


  2. Posts : 1,377
    Win7x64
       #2

    The crash is caused by an older driver called iksysflt.sys. Web searching suggests the driver is part of something called "Spyware Doctor". In this instance, the cure is worse than the disease.

    Uninstalling "Spyware Doctor" should remove the buggy driver and hence stop the crashing. Alternatively, if you simply can't live without "Spyware Doctor", try do obtain and install a greatly updated version.

    If you're quite certain that you've never installed something called "Spyware Doctor", then the driver is possibly malware which is masquerading under a known name.
      My Computer


  3. Posts : 9
    windows 7
    Thread Starter
       #3

    that is terribly interesting... I believe I deinstalled spyware doctor almost two years ago. It must be an old registry entry. I went to the Windows Program and Features option and it doesn't show up, so I can't remove it (again). I also searched and didn't find anything referencing spyware doctor.

    How do I remove this?
      My Computer


  4. Posts : 1,377
    Win7x64
       #4

    dwood9764 said:
    that is terribly interesting... I believe I deinstalled spyware doctor almost two years ago. It must be an old registry entry. I went to the Windows Program and Features option and it doesn't show up, so I can't remove it (again). I also searched and didn't find anything referencing spyware doctor.

    How do I remove this?
    Try it this way...

    On an elevated CMD instance (run CMD as admin), type this:

    SC CONFIG IKSYSFLT START= DISABLED

    (Note the lack of space before the 'equals' sign and the space after it.) Then, reboot. That should be enough to knock out the driver.

    Optionally, you can then go and outright delete the driver's entry in the registry, and then the driver file itself. It'll most likely be HKLM\System\CCS\Services\IKSYSFLT.

    If that "optional" bit doesn't make much sense, don't worry about it - as long as the SC command reports "success" you'll have deactivated the driver (after a reboot).
      My Computer


  5. Posts : 9
    windows 7
    Thread Starter
       #5

    I went out to cmd.exe as admin and executed your string (after I deleted Spyware Doctor out of my registry) and it came back as SUCCESS. What a mystery.....

    Thanks!
      My Computer


  6. Posts : 1
    Windows 7
       #6

    Same problem/different results


    I am having the same problem although I do not remember installing that software. When I use the cmd SC CONFIG IKSYSFLT START = DISABLED I do not get successful just a listing of the parameters. See attached. Can you tell me what I am doing wrong?

    Thanks
      My Computer


  7. Posts : 5,705
    Win7 x64 + x86
       #7

    momzo13 - Please start your own topic so that your issue can get the individual attention that it deserves.
      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:30.
Find Us