Solved BSOD while loading Mixcraft :: APC_INDEX_MISMATCH ntoskrnl.exe+75c40

[soundsquire]

A little recent history - I built a new PC pretty much for music production using Mixcraft 6 Pro Studio.
Asrock Z77 Pro3
Intel Core i7 3770K
8GB DDR3-1600
Sandisk Extreme 120GB SSD
WD Caviar Green 1.5TB
Corsair CX500 Power Supply
NZXT Silent Case
Win 7 Pro 64

All was well until I started getting the dreaded 'blue screen of death'.

This seems to be happening only on Mixcraft and only when I launch. The error is APC_INDEX_MISMATCH. After googling this for a bit it seems a driver thing or a hard disk error. Drivers are the usual suspect so I dug through the logs. M-Audio Fast Track C-400 is showing several errors in the log. I updated the interface drivers and am still getting the BSOD when I launch Mixcraft?

Some other history. I installed mixcraft on a non-default drive...The E drive which is the Caviar Green 1.5TB. The OS is on the C drive...the Sandisk 120GB SSD. No apparent problems there...I guess.

Please note the crash when launching Mixcraft is intermittent. Sometimes it's fine and launches no problem, bang out some tunes and then other times I get the blue screen with the APC error.

This crash happens only when I load this one program. Photoshop is fine, surfing no problem, etc. Any help is appreciated.

 

[Dsprague]

I have seen this particular BSOD as of late being caused by antivirus software, and I notice that you have Norton internet security installed. Please for the sake of testing uninstall it with this tool: Norton Removal Tool and then replace it with MSE and Mbam. Tip: Be sure to uncheck the box asking you to start a free trial when installing Mbam

Also please run the following commands from an elevated command prompt:

sfc /scannow

and

chkdsk /r/ f

 

[soundsquire]

Dsprague - Thank you for the reply.

I guess Norton was bundled with something? Maybe my AsRock utilities disk. Norton has been removed.

Running the scans you recommended now.

 

[soundsquire]

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 2/28/2013 7:22:04 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: NZXT
Description:


Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
122368 file records processed.

File verification completed.
183 large file records processed.

0 bad file records processed.

2 EA records processed.

41 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
168912 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
122368 file SDs/SIDs processed.

Cleaning up 46 unused index entries from index $SII of file 0x9.
Cleaning up 46 unused index entries from index $SDH of file 0x9.
Cleaning up 46 unused security descriptors.
Security descriptor verification completed.
23273 data files processed.

CHKDSK is verifying Usn Journal...
36197552 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
122352 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
18459780 free clusters processed.

Free space verification is complete.
Windows has checked the file system and found no problems.

117115903 KB total disk space.
42986668 KB in 96870 files.
62212 KB in 23274 indexes.
0 KB in bad sectors.
227903 KB in use by the system.
65536 KB occupied by the log file.
73839120 KB available on disk.

4096 bytes in each allocation unit.
29278975 total allocation units on disk.
18459780 allocation units available on disk.

Internal Info:
00 de 01 00 58 d5 01 00 18 79 03 00 00 00 00 00 ....X....y......
24 01 00 00 29 00 00 00 00 00 00 00 00 00 00 00 $...)...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

 

[soundsquire]

SFC details attached.

 

[Dsprague]

Everything looks good with the scans, Let us know if you continue to have BSODs

 

[soundsquire]

Thank you for the update. I had the same crash again this morning. Same software launch causes the BSOD. Same error.

Attaching a new grab from the diagnostics. Thank you again for you help!

 

[Dsprague]

Ok had another look at the logs from the chkdsk and noticed it didnt check the disk that mixcraft is insatlled on so please run the following command:

chkdsk E: /r /f

let us know the results

 

[soundsquire]

Chkdsk was executed in read/write mode.

Checking file system on E:
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) Volume dismounted. All opened handles to this volume are now invalid.
Volume label is Data.

CHKDSK is verifying files (stage 1 of 5)...
62720 file records processed. File verification completed.
11 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
75374 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
62720 file SDs/SIDs processed. Cleaning up 26 unused index entries from index $SII of file 0x9.
Cleaning up 26 unused index entries from index $SDH of file 0x9.
Cleaning up 26 unused security descriptors.
Security descriptor verification completed.
6328 data files processed. CHKDSK is verifying Usn Journal...
35684904 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
62704 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
344842204 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

1465136127 KB total disk space.
85535060 KB in 51523 files.
23496 KB in 6329 indexes.
0 KB in bad sectors.
208751 KB in use by the system.
65536 KB occupied by the log file.
1379368820 KB available on disk.

4096 bytes in each allocation unit.
366284031 total allocation units on disk.
344842205 allocation units available on disk.

 

[Dsprague]

OK... so that looks alright, please enable driver verifier and allow it to run for 24 hours or untill your computer crashes:

Driver Verifier - Enable and Disable

once your computer has crashed with driver verifier enabled please post the new dump files here.

Tip: if you can not boot normally into windows after enabling driver verifier please enter safe mode by pressing the F8 key before the windows logo appears, once in safe mode disable driver verifier.

 

[soundsquire]

I could not boot after enabling the driver verifier:

The problem seems to be caused by the following file: NIWinCDEmu.sys

DRIVER_VERIFIER_IOMANAGER_VIOLATION

 

[Dsprague]

Quick question, do you have a program that you use for mounting ISO files?

 

[soundsquire]

Thank you for checking in on me.

No ISO mount on this PC. I just built it about a month ago. I have one on my other PC for playing old games. Duels of the Planeswalkers from Microprose. LOL!

ETA: I re-installed some drivers for my Audio Interface and also re-installed Mixcraft on the C drive. Mixcraft crashed on launch again this morning.

 

[soundsquire]

Re-installing the drivers and Mixcraft on the C drive did not help. Any other suggestions or tests you can recommend?

 

[Arc]

Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Now enable Driver verifier again. Make it sure that you are not selecting any driver provided by "microsoft" or "unknown". Let us know the situation.

 

[Dsprague]

I have contacted other BSOD annalists to take a look.

 

[Pauly]

I always like to verify hardware as a precaution and prefer a bootable HDD check rather than windows utility, also ensure your SSD is running the latest firmware and check your bios is upto date, lots of Z77 boards were manufactured before latest CPUs were released so i always advise bios update to ensure they are all playing nice together
Hard Drive Diagnostic Procedure
SeaTools | Seagate
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[soundsquire]

I have updated all the drivers on my system as well as the firmware for the AsRock MB. Also removed the startup items that Arc suggested. Will start running the tests you mentioned.

I am still getting the crash but all seems to be fine on a fresh boot. The pattern seems to be after the PC has sat idle overnight that I get the crash but again only Mixcraft shows this symptom.

Thanks again to Dsprague, Arc and Pauly!

 

[Arc]

What is the situation now? If you have got any further crash, post those following the BSOD posting instructions.

 

[soundsquire]

Here is the blue screen I get now with the driver verifier enabled:

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: NIWinCDEmu.sys

DRIVER_VERIFIER_IOMANAGER_VIOLATION

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x000000c9 (0x0000000000000215, 0xfffff88005a92eab, 0xfffff98009a2ee10,
0x0000000000000000)

Note this happens before a complete boot to the desktop.