WinXP Update has rendered my DVD Shrink Useless

Discussion in 'DVD Shrink forum' started by mozzer34, Aug 7, 2006.

  1. mozzer34

    mozzer34 Guest

    I am about to pull out my friggin hair. I have ran DVD Shrink for years now and never had an issue with the program. Now, recently I updated Windows XP SP2 with update KB916595. I foolish updated this and wasn't having any problems before. But now I get the error message they are talking about when I try to run DVD Shrink. I get a blue screen error message that says DRIVER_IRQL_NOT_LESS_OR_EQUAL. I uninstalled the updates and a couple of security updates that seemed to be tied to the update and I restarted. Then I went as far as to uninstall DVD Shrink and restart again and then install DVD Shrink all over. Just to be safe I wanted everything as clean as it could be. But now I am still getting the blue screen error message and I have to reboot and when I reboot I have to restore my active desktop. What the hell. I cannot figure this out. Please anyone that has a clue on this one please let me know.

    Thank you so much.
     
  2. guyrus

    guyrus Guest

    either try going back to a restore point with XP and if that fails, time to do a clean install of your whole system.


    MAKE SURE YOU BACK UP EVERYTHING THAT IS NECCESSARY TO YOU BEFORE YOU REFORMAT..................
     
  3. Tatern

    Tatern Member

    Joined:
    Dec 23, 2005
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    11
    Microsoft blows!!! What a POS operating system!
     
  4. PeaInAPod

    PeaInAPod Active member

    Joined:
    Nov 28, 2005
    Messages:
    3,065
    Likes Received:
    0
    Trophy Points:
    66
    The text on your blue screen is usually the result of a improperly installed driver. Usually involving new hardware. So if you have installed new hardware like a webcam,or soundcard, etc. Disconnect that hardware, uninstall the driver. If that fixes it look for new drivers for your device. If that doesnt solve it, see if the blue screen lists the driver in question. The driver should be named near the bottom of the screen. Post back with some more info and ill see what I can make of it. And running two certain antiviruses at the same time have also been known to cause this problem.
     
  5. mozzer34

    mozzer34 Guest

    Thanks but unfortunately I don't have a good restore point. I could do a clean wipe of the drive it just takes so damn long to get my pc back to the way i want it. I know people wipe their drives regularly but god there has to be a way around this. But maybe not. I haven't installed any drivers recently it has to be this Windows Update and the only time it crashes is when I am trying to encode in DVD Shrink. I can't seem to make it crash any other way. Let me know if you need more info but maybe I am screwed here.
     
  6. rav009

    rav009 Active member

    Joined:
    Nov 14, 2005
    Messages:
    2,206
    Likes Received:
    0
    Trophy Points:
    66
    What's BSOD code?

    What's happening could be caused by a few things, hardware conflicts, software confilcts, bad drivers, the list goes on.
    When it next happends,on a reboot you should see the message "Your system has recovered from a serious error", send it to microsoft, click more info and note down the error code, if you send the report you will instantly be taken to the solution page (if your lucky that is).

    We need the BSOD code to identify what it is thats happening :)
     
  7. PeaInAPod

    PeaInAPod Active member

    Joined:
    Nov 28, 2005
    Messages:
    3,065
    Likes Received:
    0
    Trophy Points:
    66
    Like rav009 said your bsod (blue screen of death, if ya didnt know) can be caused by many things. I simply named a few of the most common. But if you can post what the bsod says we should be able to find the problem.
     
  8. mozzer34

    mozzer34 Guest

    The BSOD says:

    DRIVER_IRQL_NOT_LESS_OR_EQUAL

    STOP 0X000000D1 (0X0000000C,0X00000002, 0X00000000, 0XF814E424)

    smwdm.sys Address F814E424 base at F8136000 Datestamp 3f5f6eba

     
  9. mozzer34

    mozzer34 Guest

    Thanks for asking me to look more closely at the BSOD error message. In doing so I isolated the problem file. The file was my smwdm.sys as I stated in my last post. I looked up that filename on GOOGLE and it pointed to my sound card driver. I then reinstalled the driver on my sound card and presto DVD Shrink is encoding again. Thanks a million.
     
  10. sammychan

    sammychan Member

    Joined:
    Apr 7, 2006
    Messages:
    39
    Likes Received:
    0
    Trophy Points:
    16
    I know this isn't what you want to hear but if you haven't done anything drastic like format your HD yet, you may want to try the trial versions of AnyDVD + CloneDVD2 and if they works fine, then purchase the licenses. I'd rather pay a bit of cash then get frustrated and spent a lot of time trying to get DVD Shrink working again with new windows updates.
     
  11. PeaInAPod

    PeaInAPod Active member

    Joined:
    Nov 28, 2005
    Messages:
    3,065
    Likes Received:
    0
    Trophy Points:
    66
    @mozzer34
    Very glad to hear you got it working. And you also learned a bit about "decoding" BSOD messages.

    @sammychan
    Getting anyDVD and CloneDVD2 wouldnt have changed this problem. The problem was a driver that was corrupted from a window update. like mozzer34 said he re-installed the driver and everything worked again. And since anyDVD is a driver this could just as easily happen to it.
     
  12. rav009

    rav009 Active member

    Joined:
    Nov 14, 2005
    Messages:
    2,206
    Likes Received:
    0
    Trophy Points:
    66
    I'm glad the advice was usefull and your welcome mozzer34 :-D
     
    Last edited: Aug 11, 2006
  13. PacMan777

    PacMan777 Regular member

    Joined:
    Jun 11, 2013
    Messages:
    3,836
    Likes Received:
    0
    Trophy Points:
    46
    I've had Shrink for years and never saw it do something like that. I'm glad AD has some people smart enough to figure it out. If that happened to me, I'd hate to have to reload my OS every time I ran into a driver problem. That's only necessary when the OS is so corrupted it takes longer to fix than reload it.
     

Share This Page