01-19-2011 04:46 PM
27 12
tools
  1. Sheepdog Elite's Avatar
    So I've just recently started the whole rooting process (2 days ago). I've managed to root my phone and install su and cwm. As I started shopping roms and kernels (more like trying to learn wtf it all amounted to) my computer started crashing every 10 minutes BSOD style. The error is IRQL_NOT_LESS_OR_EQUAL, and it pops up the moment I plug my phone in via USB. If I try to boot with phone connected 80%-100% chance of hanging at bios screen. If anyone can help I'd be super grateful. Relevant info is as follows.

    WinXP
    Samsung Fascinate DL09, kernel 2.6.29
    Odin, CWM, and SU all from how to root post on forum
    Drivers from forum, could not uninstall old drivers properly (seem to uninstall but still show in program list) installed drivers from forum over old (I think it worked)
    01-15-2011 11:19 PM
  2. Cyber Warrior's Avatar
    01-15-2011 11:25 PM
  3. Sheepdog Elite's Avatar
    Not sure if you're aware but the page you linked to linked to bad software upon a little review, however it was the inspiration in needed to get this all squared up. I ended up with Little Registry Cleaner | Download Little Registry Cleaner software for free at SourceForge.net and i'll let you know how it turns out once I finish this level of advance war on my GBA-emu. Thanks for the response!
    01-16-2011 12:25 AM
  4. Sheepdog Elite's Avatar
    No such luck sadly enough. Plugged it again and down I went. Odd though, i've installed bloat freezer, and frozen a bunch of the verizon crapware on my phone. Could one of these apps possibly be my culprit? I don't think I've frozen anything that wants to connect to my computer, but I know I haven't seen media sync (loaded with the new update) since my computer started crashing. Haven't frozen that though. Hmm, i'll try freezing it and see what happens. Will keep you posted.
    01-16-2011 12:41 AM
  5. Sheepdog Elite's Avatar
    Bah. No luck with freezing media sync. Should I try removing CWM and unrooting and see if that fixes it? If so is there a thread I can try? I'm sure I've seen one but I'm not sure if it was here or another forum.
    01-16-2011 01:51 AM
  6. Sheepdog Elite's Avatar
    Freezing the media sync did nothing for me. Booted into my Ubuntu partition that I don't really use alot, and it isn't crashing the way my windows does. Any further help would be greatly appreciated, I'm kind of at a loss since I use windows for just about everything, and don't want to lose netflix while i'm workin on my phone.
    01-16-2011 09:44 AM
  7. joe007's Avatar
    To be clear, the PC only BSODs when you plug the phone in?

    Dried a different cable?
    Have you tried a different USB Port?
    32 vs. 64 bit drivers?
    Reinstall the 32 or 64 drivers?

    chkdsk and or memtest?

    This only happened after DL09 was applied (OTA or CWM)?

    Is USB debug on?
    01-16-2011 12:34 PM
  8. Sheepdog Elite's Avatar
    I got DL09 OTA, and then rooted, and installed CWM (first time for both), I'm on windows XP 32bit. USB debug, and different USB port, different cable, don't make any difference. Tried uninstalling and reinstalling the drivers to no avail. Using 32 bit drivers. Stripped all of my peripherals, cards, and RAM, and rebuilt from the ground up on piece at a time with no culprits to be found. Should I try and load a different CWM and SU?

    According to Rom manager my CWM is 2.5.1.0, and i'm suffering the broken haptic feedback so i'll need to find different CWM to fix that from what i understand.

    My SU says it's 2.3.6.1 w/ binary 2.3.1

    I guess i'll go look for a new CWM and odin that baby in there and see what happens, when I get a chance. Have to do it from linux though I guess.
    01-16-2011 07:57 PM
  9. Sheepdog Elite's Avatar
    Bah. So it's definitively a bad driver issue I guess. Reflashed CWM, stupid fast kernel, still crashing. Can't get the driver to uninstall, so I guess i'm gonna go via safe mode and try to remove it once more before I call samsung in the morning.
    01-17-2011 12:51 AM
  10. DroidXcon's Avatar
    Bah. So it's definitively a bad driver issue I guess. Reflashed CWM, stupid fast kernel, still crashing. Can't get the driver to uninstall, so I guess i'm gonna go via safe mode and try to remove it once more before I call samsung in the morning.
    why dont you trying flashing it back to stock via odin and see what happens
    01-17-2011 12:53 AM
  11. Sheepdog Elite's Avatar
    Found the post about how to go back to stock. I have my sneaking suspicions that when I plug the phone back in it it'll crash again and I won't get chance to use odin. I'll try it tomorrow when I get a chance.
    01-17-2011 01:44 AM
  12. Johnly's Avatar
    It is not the phone! bottom line....
    01-17-2011 01:45 AM
  13. Johnly's Avatar
    Get your computer BIOS current and hardware drivers (99%) of cause....wow....no one has recommended that yet....should be a point of R, then move....
    01-17-2011 01:47 AM
  14. DroidXcon's Avatar
    Found the post about how to go back to stock. I have my sneaking suspicions that when I plug the phone back in it it'll crash again and I won't get chance to use odin. I'll try it tomorrow when I get a chance.
    Well when you pull the battery and put it in download mode it uses generic drivers so it may not happen.
    I suggest this just to eliminate any suspicion of it being software related on the phones side
    follow these directions
    http://forum.androidcentral.com/fasc...-via-odin.html

    It is not the phone! bottom line....
    Johnly is most likely correct. besides uninstalling and reinstalling drivers i dont know what else could cause this.

    Johnly do you have any suggestions on how to remedy this. i dont know enough to help out on the computer driver sides of things.
    Sheepdog Elite likes this.
    01-17-2011 01:54 AM
  15. Sheepdog Elite's Avatar
    Just a bonus question, anyone know how to manually remove a driver that won't uninstall?
    01-17-2011 09:26 AM
  16. fire n ice's Avatar
    Try revo uninstaller. It'll scan your registry and hd for any files leftover after running a standard uninstall

    Sent from my SCH-I500 using Tapatalk
    01-17-2011 09:46 AM
  17. ezas's Avatar
    it wasn't clear to me did you try unfreezing some of your Apps?
    Do you have any other usb devices you can try plugging in?
    You could also try booting into safe mode on your PC.
    I hate to see you rebuilding your phone. My instinct tells me it's your PC.

    And you definitely should run memtest.
    01-17-2011 01:52 PM
  18. Sheepdog Elite's Avatar
    So ya, I unfroze everything, tried a fresh kernel, new rom, no help. chkdsk and memtest yeilded no improvement or fresh info. Gonna try the revo uninstaller and see if I can nuke this bad driver with it. fun
    01-17-2011 10:34 PM
  19. DroidXcon's Avatar
    So ya, I unfroze everything, tried a fresh kernel, new rom, no help. chkdsk and memtest yeilded no improvement or fresh info. Gonna try the revo uninstaller and see if I can nuke this bad driver with it. fun
    did you end up trying odin?
    01-17-2011 10:36 PM
  20. Sheepdog Elite's Avatar
    Gonna have to boot over to linux to pull that off. Ended up with a program called easy uninstaller which nuked my bad driver no problem. Sadly enough I plugged my phone in again and it crashed. AGAIN!
    01-17-2011 10:52 PM
  21. Sheepdog Elite's Avatar
    So a question that sucks to look for the answer to. Is there a way to get back to stock without wiping my stock ROM? I don't wanna start over, and i'm short on ideas of how to keep all my apps and not end up losing all my data.
    01-17-2011 11:19 PM
  22. DroidXcon's Avatar
    Only a nandroid or titanium backup can help with that
    So a question that sucks to look for the answer to. Is there a way to get back to stock without wiping my stock ROM? I don't wanna start over, and i'm short on ideas of how to keep all my apps and not end up losing all my data.


    Sent from my SCH-I500 using Tapatalk
    01-17-2011 11:41 PM
  23. Sheepdog Elite's Avatar
    So for the latest installment in general hospital for droid afflicted PCs. I plugged in via ODIN method and escaped the BSOD and am able to work. Flashed Adryn modded CWM and DL09 kernel in place of old CWM which was replaced with stupidfast (hope that makes sense) with new CWM with DL09 kernel crashed. Factory reset phone, still crashed. At this point all I can think of is the recovery is causing some sort of conflict? I've been through 4 kernels, 3 separate stock roms (original used rom, super clean, and factory reset stock rom). I've uninstalled drivers by force after stock uninstall failed, then reinstalled. Chkdsk and Memtest both came back with negative improvement. So I'm pulling my hair out, don't know what to do, and am just crossing my fingers that there is something in the SD mount fix that will fix me too. No clue what else to think of. What a train wreck. I may have my logistics crossed up here but I think I've replaced absolutely everything I can, except getting rid of CWM. Can I do that? Will it trash my current rom? I know I can capitalize on a backup later but finding a fix that blanks my phone isn't happy.

    To be clear about my error, I know it's driver or memory related, but my drivers are clean, i've manually pulled 1/2 my memory, booted to same issue, swapped memory, same issue. In windows I plug the phone in and something like an even 15-20 seconds my whole system crashes flat out and reboots.

    For the record Nandroid backup and CWM are two of the best things ever. I'm really glad I did all of this even for the fight to figure out this severe conflict.
    01-18-2011 01:32 AM
  24. Sheepdog Elite's Avatar
    So I loaded adryn's new test kernel #5 nonvoodoo standard voltage, and all is well again. I think what was going on was the other kernels were trying to load the newer (DL09 media sync) drivers and that was causing my crash. Since he went back to the old drivers (guessing about that) it loaded a bunch of new hardware info to the machine, and like magic no crash. WOOT!
    01-19-2011 01:24 AM
  25. DroidXcon's Avatar
    So it was the phone and the computer. Thank you so much for posting your results,im sure this info will be useful to others in the future. Congrats on getting it running again.
    So I loaded adryn's new test kernel #5 nonvoodoo standard voltage, and all is well again. I think what was going on was the other kernels were trying to load the newer (DL09 media sync) drivers and that was causing my crash. Since he went back to the old drivers (guessing about that) it loaded a bunch of new hardware info to the machine, and like magic no crash. WOOT!


    Sent from my SCH-I500 using Tapatalk
    01-19-2011 01:32 AM
27 12
LINK TO POST COPIED TO CLIPBOARD