BSOD - iTunes or iOlo, no idea (dmp file attch.)


  1. jlawass
    Posts : 3
    Windows 7
       New #1

    BSOD - iTunes or iOlo, no idea (dmp file attch.)


    The problem started at first every time I started using iTunes. But I also started using iOlo for all of my security needs. Just when I thought I had it figured out, it now crashes more frequently and while using other programs. It reads APC_index_mismatch.

    Here is the pop-up and the dmp file is attached.

    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: 1
    BCP1: 83096E82
    BCP2: 00000000
    BCP3: 0000FFFF
    BCP4: 00000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    All of my software is updated. I have run a complete scan for viruses and other malware and nothing wrong was found. I have avoided using file sharing programs and iTunes for the time being. I also recently switched over to Windows 7 from XP. Lenovo gave me a disk for all the driver updates but certain things still don't work like the camera and Veriface. The computer was purchased in 2009. Y530. 2.0 Ghz, 3 GB RAM, 32-bit OS.
      My Computer
    Quote Quote

  3. zigzag3143
    Posts : 28,845
    Win 8 Release candidate 8400
       New #2

    jlawass said:
    The problem started at first every time I started using iTunes. But I also started using iOlo for all of my security needs. Just when I thought I had it figured out, it now crashes more frequently and while using other programs. It reads APC_index_mismatch.

    Here is the pop-up and the dmp file is attached.

    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: 1
    BCP1: 83096E82
    BCP2: 00000000
    BCP3: 0000FFFF
    BCP4: 00000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    All of my software is updated. I have run a complete scan for viruses and other malware and nothing wrong as found. I have avoided using file sharing programs and iTunes for the time being.
    Just curious. where did you get win 7 from? It is a different version than the RTM from microsoft.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\030710-21122-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82e1c000 PsLoadedModuleList = 0x82f64810
Debug session time: Sun Mar  7 10:07:49.895 2010 (GMT-5)
System Uptime: 0 days 1:39:29.877
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {83066e82, 0, ffff, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
      My Computer
    Quote Quote

  4. jlawass
    Posts : 3
    Windows 7
    Thread Starter
       New #3

    This version came from Lenovo. The laptop came with XP last year and they upgraded it with the disc. As I said, the drivers were confusing and some programs still don't work.
      My Computer
    Quote Quote

  6. jlawass
    Posts : 3
    Windows 7
    Thread Starter
       New #4

    So, does this mean I'm screwed?
      My Computer
    Quote Quote

 

  Related Discussions
iTunes .itl file is locked
in Music, Pictures & Video

How do I change the attributes of the iTunes library folder And get rid of the read only attributes as right now I can't access my iTunes for windows music library as it says the .itl file is locked on disk or you do not have permission to access this file. Apparently it has something to do...
Hello All, My laptop (Dell Studio 1550, Windows 7 Home Premium 64 bit) just gave me the black screen upon start-up. The Iolo System Mechanic had defragged the registry, I think, and it seems that the process had damaged my laptop's registry. I've ran sfc /scannow with no issues, but the...
Iolo Sys. Mechanic gadget
in Customization

Ok yet another gadget thread.. So I have Iolo System Mechanic and it comes with this gadget.. I've used it along with others for a while now.. I go to renew and upgrade ISM.. and when I do the gadget stops working.. I contact customer support (just loads of help) and they swear up and down that...
and also i get problems need to be repaired in iolo system mechanics from hard drive repair section every week it appears even thought i i use the check disk in window to repair but new problem i think appears a week later and i get a could not fine this item and so i have to press try again...
Hey So I was just wondering if there would be some way to have your computer go into hibernate mode, have it put the hibernation file onto an external flash drive, then move that flash drive to another computer with the same exact build and have it boot up off of that hibernation file.
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 18:29.
Find Us