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: APC_Index_Mismatch

06 Nov 2010   #1
IoNGeNeRaL

Windows 10 Pro x64 (UPGRADED - 10/20/2016)
 
 
APC_Index_Mismatch

I have another few BSODs. Probably from the ASUS Utility or my BlackBerry. When I plug the device in my USB 2.0 slot to charge it, I get BSODs.


My System SpecsSystem Spec
.
06 Nov 2010   #2
usasma
Microsoft MVP

 
 

Please keep your posts in one topic. It's difficult to see what has been done and what result our work has had. Here's a list of your other topics:
Started 4 days ago - https://www.sevenforums.com/crashes-d...ue-screen.html
Started 2 days ago - https://www.sevenforums.com/crashes-d...y-windows.html
Started yesterday - https://www.sevenforums.com/crashes-d...sod-again.html

The MSINFO32 report shows this device as having a problem:
Quote:
Ethernet Controller PCI\VEN_11AB&DEV_4381&SUBSYS_84391043&REV_11\5B582AFFFF30CF2000 The drivers for this device are not installed.
Please install the drivers for this device or remove the device from your system (if it's built in, disable it in the BIOS).

In this case the most likely culprit is ewusbnet.sys - a driver for your USB NDIS Miniport Driver - likely for Huawei Mobil Connect package. Seen with T-Mobile webConnect.

- Please download a fresh copy of the software/drivers
- Then uninstall the current software/drivers from your system
- Then install the freshly downloaded software/drivers
- Then monitor for further BSOD's

BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Nov  6 09:50:00.923 2010 (UTC - 4:00)
System Uptime: 0 days 0:05:47.000
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+ae67 )
BUGCHECK_STR:  0x1a_5100
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001A
Arguments 00000000`00005100 fffff6fc`40038000 00000000`00000005 00000000`00000963
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Nov  6 09:24:14.779 2010 (UTC - 4:00)
System Uptime: 0 days 0:25:51.825
*** WARNING: Unable to verify timestamp for ewusbnet.sys
*** ERROR: Module load completed but symbols could not be loaded for ewusbnet.sys
Probably caused by : ewusbnet.sys ( ewusbnet+27b6 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`05d5e7b6 fffff880`07b1e8b8 fffff880`07b1e110
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Nov  6 08:52:53.413 2010 (UTC - 4:00)
System Uptime: 1 days 10:59:21.910
*** WARNING: Unable to verify timestamp for ewusbnet.sys
*** ERROR: Module load completed but symbols could not be loaded for ewusbnet.sys
Probably caused by : ewusbnet.sys ( ewusbnet+31180 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
Bugcheck code 00000050
Arguments fffff880`09fe913e 00000000`00000000 fffff880`06df2180 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov  6 11:24:28.851 2010 (UTC - 4:00)
System Uptime: 0 days 0:16:02.225
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1
PROCESS_NAME:  firefox.exe
Bugcheck code 00000001
Arguments 00000000`76f005aa 00000000`00000000 00000000`ffff0000 fffff880`0959aca0
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov  6 11:07:28.128 2010 (UTC - 4:00)
System Uptime: 0 days 0:31:23.141
Probably caused by : fileinfo.sys ( fileinfo!FIPfInterfaceClose+48 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  crashreporter.
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff880`01016177 00000000`00000000 ffffffff`ffffffff
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Nov  4 07:11:02.460 2010 (UTC - 4:00)
System Uptime: 0 days 1:12:13.896
*** WARNING: Unable to verify timestamp for ewusbnet.sys
*** ERROR: Module load completed but symbols could not be loaded for ewusbnet.sys
Probably caused by : ewusbnet.sys ( ewusbnet+27b6 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`0606d7b6 fffff880`03d838b8 fffff880`03d83110
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov  1 14:12:49.713 2010 (UTC - 4:00)
System Uptime: 0 days 0:23:33.759
*** WARNING: Unable to verify timestamp for ewusbnet.sys
*** ERROR: Module load completed but symbols could not be loaded for ewusbnet.sys
Probably caused by : ewusbnet.sys ( ewusbnet+27b6 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`06a027b6 fffff880`08e758b8 fffff880`08e75110
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Oct 28 05:32:35.404 2010 (UTC - 4:00)
System Uptime: 1 days 22:02:49.930
*** WARNING: Unable to verify timestamp for ewusbnet.sys
*** ERROR: Module load completed but symbols could not be loaded for ewusbnet.sys
Probably caused by : ewusbnet.sys ( ewusbnet+27b6 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`0638f7b6 fffff880`087a48b8 fffff880`087a4110
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Oct 23 11:03:38.133 2010 (UTC - 4:00)
System Uptime: 0 days 2:22:19.569
*** WARNING: Unable to verify timestamp for ewusbnet.sys
*** ERROR: Module load completed but symbols could not be loaded for ewusbnet.sys
Probably caused by : ewusbnet.sys ( ewusbnet+27b6 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`05c7c7b6 fffff880`03b588b8 fffff880`03b58110
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Oct 20 04:41:24.114 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:36.550
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgcsrva.exe
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`01f682a0 00000000`0000ffff 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Oct 20 04:38:20.531 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:19.967
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  drvinst.exe
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`0195dc20 00000000`0000ffff 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Oct  1 09:46:33.474 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:26.910
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36924 )
BUGCHECK_STR:  0x1a_5002
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgcsrva.exe
Bugcheck code 0000001A
Arguments 00000000`00005002 fffff700`01080000 00000000`00001495 08001496`fffffffe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Oct  1 09:40:59.608 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:31.654
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgcsrva.exe
Bugcheck code 0000001A
Arguments 00000000`00041284 00000000`071cd001 00000000`00000000 fffff700`01080000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Sep 30 06:42:36.717 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:01.934
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33a98 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Wow.exe
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`01909da0 00000000`0000ffff 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Sep 30 06:40:01.718 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:31.839
Probably caused by : Ntfs.sys ( Ntfs!memcmp+10 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wmpnetwk.exe
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`07efa708 fffff880`07ef9f60 fffff880`01256cc0
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
08 Nov 2010   #3
IoNGeNeRaL

Windows 10 Pro x64 (UPGRADED - 10/20/2016)
 
 

Another few BSODs.
My System SpecsSystem Spec
.

08 Nov 2010   #4
usasma
Microsoft MVP

 
 

Please remove RivaTuner/EVGA Precision. It has known issues w/Win7.
This is the driver: RTCore64.sys Wed May 25 02:39:12 2005 (42941D90)

Please run Driver Verifier according to these instructions:
Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Code:
Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov  8 08:57:20.631 2010 (UTC - 5:00)
System Uptime: 0 days 0:03:17.644
Probably caused by : win32k.sys ( win32k!UpdateAsyncKeyState+116 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xBE
PROCESS_NAME:  csrss.exe
Bugcheck code 000000BE
Arguments fffff960`001b2f98 1d300001`1b586001 fffff880`02e45650 00000000`0000000b
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov  8 08:52:49.023 2010 (UTC - 5:00)
System Uptime: 0 days 0:12:51.396
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+ca0 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
Bugcheck code 00000019
Arguments 00000000`00000003 fffff8a0`07dc3150 fffff8a0`07f46fdc fffff8a0`07dc3150
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov  8 08:39:04.553 2010 (UTC - 5:00)
System Uptime: 0 days 0:50:04.927
Probably caused by : ntkrnlmp.exe ( nt!IoRemoveIoCompletion+153 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`031cbf03 fffff880`075130c0 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov  8 07:48:05.052 2010 (UTC - 5:00)
System Uptime: 0 days 0:01:46.426
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+ca0 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ipoint.exe
Bugcheck code 00000019
Arguments 00000000`00000003 fffff900`c06ea090 fffff900`c06ea090 fffff900`c06ea010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Nov  7 17:09:02.327 2010 (UTC - 5:00)
System Uptime: 0 days 0:55:52.700
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+1fe )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  GTAIV.exe
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`06c20cc8 fffff880`06c20530 fffff880`012b2c27
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Nov  7 16:11:52.005 2010 (UTC - 5:00)
System Uptime: 0 days 0:03:40.378
Probably caused by : ntkrnlmp.exe ( nt!IoRemoveIoCompletion+153 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`031bff03 fffff880`073030c0 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Nov  7 16:06:53.293 2010 (UTC - 5:00)
System Uptime: 0 days 0:05:03.306
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefix+121 )
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`05acf798 fffff880`05acf000 fffff880`012d1a91
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Nov  7 12:32:12.444 2010 (UTC - 5:00)
System Uptime: 0 days 0:06:34.818
Probably caused by : ntkrnlmp.exe ( nt!IoRemoveIoCompletion+153 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  MsMpEng.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`03176f03 fffff880`0a5430c0 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
13 Nov 2010   #5
IoNGeNeRaL

Windows 10 Pro x64 (UPGRADED - 10/20/2016)
 
 

I have 4 more BSOD bumps for you awesome people to analyze for me.
My System SpecsSystem Spec
13 Nov 2010   #6
usasma
Microsoft MVP

 
 

Lot's of hard drive/file system involvement in these.
Please do the following:
Quote:
CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.
And then do these free tests:
Quote:
I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
Quote:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
It appears that none of the attached dump files are Driver Verifier enabled memory dumps.
Have you enabled Driver Verifier according to the instructions that I posted?

BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 11:26:51.007 2010 (UTC - 5:00)
System Uptime: 0 days 0:04:02.020
Probably caused by : Ntfs.sys ( Ntfs!NtfsLookupAllocation+eb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Xfire.exe
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0b8f2a38 fffff880`0b8f22a0 fffff880`012253cb
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 11:20:58.832 2010 (UTC - 5:00)
System Uptime: 0 days 2:31:22.206
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+ca0 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000019
Arguments 00000000`00000003 fffff8a0`07e224e0 fffff8a0`07e224e0 fffff8a0`07e22460
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 08:47:34.979 2010 (UTC - 5:00)
System Uptime: 0 days 0:08:24.993
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a56 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
Bugcheck code 00000019
Arguments 00000000`00000003 fffff880`02b077b0 fffff880`02b077b0 fffff880`02b07730
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 08:37:33.655 2010 (UTC - 5:00)
System Uptime: 0 days 0:34:57.029
Probably caused by : fileinfo.sys ( fileinfo!FIStreamLog+1be )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`03072615 fffff880`031663a8 fffff880`03165c10
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
Reply

 APC_Index_Mismatch




Thread Tools




Similar help and support threads
Thread Forum
Bsod apc_index_mismatch
Hi All, I have today found BSOD APC Index Mismatch. Spec: Win 7 Ultimate 32bit
BSOD Help and Support
BSOD APC_Index_Mismatch
Hello. This BSOD happened as I was coming out of the screen saver. The message was "BSOD APC_Index_Mismatch." I've had five other BSODs in the past two months, but this is the first one in a while. I had thought they were related to a utility (Listary) I was using and dropped because one BSOD...
BSOD Help and Support
BSOD APC_INDEX_MISMATCH, Network
Getting this BSOD randomly when working on network files from a Novell drive. It's on a Dell Optiplex 3010. I uninstalled/installed the network driver which made no difference. Ran the Dell hardware diagnostics and found no problems. The problem only comes up once or twice a day, usually when...
BSOD Help and Support
BSOD Apc_index_mismatch
I randomly just got this BSOD and error code and have no idea what caused it but it's happening now every time I restart my computer and the only way this doesn't occur is to run it in safe mode. I've attached the zip file with the dump logs and hopefully someone can figure out what's wrong. Thanks.
BSOD Help and Support
BSOD with APC_INDEX_MISMATCH
I've had two or three blue screens and I barely managed to see APC_INDEX_MISMATCH before the PC reset itself. Also, I don't know if it is related or not, at startup my computer almost always does a Boot reloop, getting stuck there. However, if I press F9, which for my Gigabyte BIOS is Info, and...
BSOD Help and Support
Apc_index_mismatch
Dell M4400 Windows 7 Pro x64 Is original installed OS OEM System Hardware = 18 months old OS installation = 9 months old Hello and thank you for taking the time to help with this post. This system has regularly experienced APC_INDEX_MISMATCH BSODs
BSOD Help and Support


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 20:33.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App