Skip navigation

unknown ModName issue.

813 Views 13 Replies Latest reply: Apr 26, 2012 4:26 PM by LaydenWinters RSS
Quiver Calculating status...
Currently Being Moderated
Apr 9, 2012 12:19 AM

Hi all,


I tried tagging this enquiry onto an old post of the same theme, but I'm not sure if that gets the attention of the 'powers that be', as it were.


Basically, iTunes crashes on startup, on a clean Windows XP Pro SP3 box.  The report is:


AppName: itunes.exe AppVer: ModName: unknown
ModVer: Offset: 970108d7


Ok, what I've tried/observed is (and I've repeated these steps after each change):


  • Changing users - no change (system-wide problem)
  • iTunes Safe Mode (same fault)
  • Quicktime still works (this appears to be different to most others experiencing this fault, from what I've read..)
  • itunes batch file to re-register .dll's
  • Full reinstall in the method shown here: including manual cleanout of Temp, prefs & program files / system32 stuff.
  • Removal using the 'Windows Install Clean-Up' Tool
  • Disabling of Anti-Malware software (and removal, later)
  • Removal of all programs that could potentially interfere:- VLC etc
  • Repair of components of iTunes / Quicktime after reinstallation
  • All Drivers are up-to-date
  • Previous iTunes installations have worked on here before - with the same drivers/software.


Any ideas would be greatly appreciated..  Thanks!!

Custom, Windows XP Pro, P4 3.06GHz Northwood
  • b noir Level 9 Level 9 (71,990 points)
    Currently Being Moderated
    Apr 9, 2012 2:23 PM (in response to Quiver)

    You've actually already covered almost everything (both likely and/or unlikely) that I'd check on with one of those.


    Quickly doublechecking one thing. Are you running your XP out of VirtualBox on a Linux system? (That used to produce the unknown modname (but quicktime player launches) issue back in the iTunes 9.x days, although I'm not state of the art on whether it's still an issue with 10.x versions.)

  • b noir Level 9 Level 9 (71,990 points)
    Currently Being Moderated
    Apr 9, 2012 4:15 PM (in response to Quiver)

    One last throw of the dice. The issue is consistent with a systemwide problem, although I'm more used to it being associated with error-message-free launch failures:


    iTunes for Windows in Windows XP or Windows 2000 doesn't open after upgrading

  • b noir Level 9 Level 9 (71,990 points)
    Currently Being Moderated
    Apr 9, 2012 5:49 PM (in response to Quiver)

    That is interesting ... if you delete the file again, and provoke the iTunes error again, do you get to have another look at that modname?

  • b noir Level 9 Level 9 (71,990 points)
    Currently Being Moderated
    Apr 10, 2012 8:59 PM (in response to Quiver)

    ModName: corefp.dll



    Strange. That's your FairPlay. So we're actually in the same area with that as with the system configuration files (they both form part of the authorisation equipment).


    By way of experiment, try disconnecting the PC from the internet and then attempting to launch iTunes. Does it open if it can't go on line?

  • b noir Level 9 Level 9 (71,990 points)
    Currently Being Moderated
    Apr 10, 2012 9:53 PM (in response to Quiver)

    On XP, you'd be able to get a DrWatson log of the error. (Unfortunately, I'm no good at interpreting them.)


    First Dr Watson needs to be configured on the PC.



    In the Windows start menu, click "Run". Type cmd and hit enter. At the prompt in the command line window that comes up, type in



    drwtsn32 -i



    ... and hit return.



    This will create crash logs in Documents And Settings\All Users\Application Data\Microsoft\Dr Watson\.


    There'll usually be a file in here called "drwtsn32.log"



    Prior to collecting an iTunes crash log, delete any existing crash logs in there. (Otherwise, we'll be just appending the information to any existing log, which will make tracking down the information very difficult to track down. I've seen existing log files in the order of a GB in size or more in the past.)



    You should be able to open the log file in a text editor. (WordPad, for example, if it's relatively small.)

  • LaydenWinters Calculating status...
    Currently Being Moderated
    Apr 26, 2012 4:26 PM (in response to Quiver)

    Excuse this interruption but I find myself having the EXACT same issue.  And I mean EXACT.  My Windows Xp computer is running with Service pack 3 with no security issues.  Clean install. 


    This will be the 6th time to have iTunes downloaded to this computer without any of the prior programs running including this one.  In each case of uninstalling, all Apple related programs (I believe 5 in total) were uninstalled...Bonjour..etc.,.


    There seems to be some sort of relationship between the corefp.dll, gnsdk_dsp.dll and the unknown error issue. 


    I kept receiving the corefp.dll error issue before I actually started up Quicktime.  After starting Quicktime (and yes, it works with no problems), the error message changed and stated that the gnsdk_dsp.dll file was the problem.  After disconnecting my computer from the modem, the error message changed from gnsdk_dsp.dll and was again *Unknown*.  Since my modem is again running my internet connection, the error message is again, *Unknown*.


    I've gone as far as replacing the gnsdk_dsp.dll file with a previous created version and I was then told that itunes was corrupted.   - This happened on Installation of itunes for the 5th time.  The computer was then erased and reinitialized from scratch.


    To make my long story short, the Unknown error issue.....well., makes this my 6th time.


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.