Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


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


08 Mar 2010   #1

Windows 7
 
 
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 System SpecsSystem Spec
.

08 Mar 2010   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by jlawass View Post
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 System SpecsSystem Spec
08 Mar 2010   #3

Windows 7
 
 

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 System SpecsSystem Spec
.


09 Mar 2010   #4

Windows 7
 
 

So, does this mean I'm screwed?
My System SpecsSystem Spec
Reply

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




Thread Tools



Similar help and support threads for2: BSOD - iTunes or iOlo, no idea (dmp file attch.)
Thread Forum
An .mpg file won't import into iTunes for Windows Music, Pictures & Video
Black screen of death after IOLO defrag BSOD Help and Support
Iolo Sys. Mechanic gadget Gadgets
error getting file security when installing itunes Software
get problems need to be repaired in iolo system mechanics from HDD Performance & Maintenance
Idea: Moving hibernate file between identical computers General Discussion

Our Sites

Site Links

About Us

Find 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 02:00 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33