TechSpot

Blue screen randomly occurs sometimes not at all

By KingSaber
Feb 17, 2012
Post New Reply
  1. Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 1e
    BCP1: 0000000000000000
    BCP2: 0000000000000000
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    How to find and post your Minidump Files:

    My Computer > C Drive > Windows Folder > Minidump Folder > Minidump Files.

    It is these files that we need (not the folder). Attach to your next post the five most recent dumps. Notice the Manage Attachments button at the bottom when you go to post the next time. You can Zip up to five files per Zip; if you only have one or two you don’t need to zip them, just attach as is. Please do us a favor and don’t Zip each one individually.
     
  3. KingSaber

    KingSaber TS Rookie Topic Starter

    The dmp files

    Sorry for the wait
     

    Attached Files:

  4. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

  5. KingSaber

    KingSaber TS Rookie Topic Starter

    How would you suggest check my PSU

    how should I check to see if my powersupply is giving enough amps?
    Nevermind now that I thought about it its probably not my PSU. Even when under full load its fine
     
  6. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    So what happened with the memory and hard drive checks? Are you over-clocking?
     
  7. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    All four minidump files cite the same error code 0x1E: KMODE_EXCEPTION_NOT_HANDLED

    The Windows kernel detected an illegal or unknown processor instruction. A Stop 0x1E condition can be caused by invalid memory and access violations similar to those that generate Stop 0xA errors.

    0xA errors can be caused by either hardware or drivers attempting to access a higher IRQ address than what they are designed for resulting in system crashes.

    In all four the driver danew.sys was cited as the cause. This belongs to your Razer DeathAdder USB Optical Mouse. Update your mouse drivers.
     
  8. KingSaber

    KingSaber TS Rookie Topic Starter

    Mx518 and deathadder both plugged in at the same time

    I have my deathadder drivers updated but I also have my old mx518 drivers. Do you think the drivers are conflicting for rights. I notice that this normally happens when im running an application like osu or adobe flash player
     
  9. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Uninstall the old drivers and tell us if the BSODs occur.
     
  10. KingSaber

    KingSaber TS Rookie Topic Starter

    Seems like this problem is bigger http://www.gamerswithjobs.com/node/39079
    If somebody could help me figure out how to get my mouse driver working that would be appreciated. A mouse driver causing a BSOD.... thats just silly, Now I really wish I did have on the fly dpi adjustments >.<
     
  11. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Razor has had many issues with several models and their drivers these past 5 years. I suggest uninstalling your mouseware and reinstall and then update.
     
  12. KingSaber

    KingSaber TS Rookie Topic Starter

    Figured the problem out. Reconnecting the deathadder caused the problems or thats what it seems like.
     
  13. KingSaber

    KingSaber TS Rookie Topic Starter

    yeap this thread can be closed. Problem fixed. Guys dont plug in your deathadder while your computer is on.
     

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...