|
Subject:The Long Awaited Blue Screen of Death Message
Posted by: jeepman83706
Date:2/7/2003 7:12:33 PM
Ok everybody who has been reading my past couple posts. Remember that Acid was crashing when I was trying to record audio after already having some tracks laid out, and not crashing when audio was my first recorded track. Acid closes, then a few moments later, this blue screen of death appears: ------------------------------------ A problem has been detected and windows has been shut down to prevent damage to your computer. PROCESS_HAS_LOCKED_PAGES 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: 0x00000076 (0x00000000, 0x81934020, 0x00000003, 0x00000000) Beginning dump of physical memory Dumping physical memory to disk: (numbers start counting up from here) ------------------------------------ So, if anyone is wondering why I'm posting this, please read my "The verdict is in" thread. Now, like I said before, I ran the RAM through some tests and everything is great. Is this or is this not because of my sound card? Thanks for the much needed help! |
|
Subject:RE: The Long Awaited Blue Screen of Death Message
Reply by: nlamartina
Date:2/7/2003 8:59:14 PM
Oh it's THAT kind of BSOD? Oh I was confused. I forgot you were running XP. Okay, that so totally screams hardware problem. If I were you, I'd try completely reinstalling the sound card. As in take it out, wipe the registry clean of its traces, and then install it again using the latest drivers. Oh, did you try resetting that playback buffer setting? Try that before you start tearing out cards. HTH, Nick |
|
Subject:RE: The Long Awaited Blue Screen of Death Message
Reply by: jeepman83706
Date:2/7/2003 9:03:05 PM
Well, it is the sound card that came with my computer, and unfortunately it is integrated into the motherboard. I have already downloaded the latest drivers for it and I did reset that playback buffer thingy, but it still crashes. I do have a couple open PCI slots in there, so would getting a new soundcard for recording, like Echo Mia or Audiophile solve my crashing probs? |
|
Subject:RE: The Long Awaited Blue Screen of Death Message
Reply by: Vocalpoint
Date:2/8/2003 12:33:56 AM
All, Here's the deal on this message...it's a wee bit technical but worth a look: NOTE - If you don't feel comfy in the Registry...then please do not attempt this fix! The "STOP: 0x00000076 (0xY,0xY,0xY,0xY) PROCESS_HAS_LOCKED_PAGES" error message is caused by a driver not cleaning up completely after an I/O operation. Parameter 1 - 0 Parameter 2 - process address Parameter 3 - number of locked pages Parameter 4 - pointer to driver stacks (if enabled) or 0 if not In your message: STOP: 0x00000076 (0x00000000, 0x81934020, 0x00000003, 0x00000000 <- we can't see the driver details here in the last parameter yet....so Windows XP includes a registry value that you can use to save stack traces that enable you to identify the problem driver. Use Registry Editor (Regedt32.exe) to view the following registry key: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management Add the following registry value, and then restart your computer: Value Name: TrackLockedPages Value Type: REG_DWORD Value Data: 1 Radix: hexadecimal After you make this change, Windows saves stack traces so that you can identify the problem driver. There is no other way to determine which driver is neglecting to clean up the I/O operations. After you enable this flag, if the driver commits the error again, you see the following error message: STOP: 0x000000CB (0xY,0xY,0xY,0xY) DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS Parameter 1 - The calling address in the driver that locked the pages Parameter 2 - The caller of the calling address in the driver that locked the pages Parameter 3 - A pointer to the MDL containing the locked pages Parameter 4 - The problem driver's name (Unicode string) The problem driver's name is listed on the blue "Stop" screen and is available for dumping again as the fourth parameter in the "Stop" data. After you identify and update or remove the problem driver, you should remove the TrackLockedPages value from the registry. Let us know what you find out (if you go through with it!) Cheers, Cuzin B |
|
Subject:RE: The Long Awaited Blue Screen of Death Message
Reply by: jeepman83706
Date:2/8/2003 2:19:43 AM
Ok CuzinB, I did what you said and this is what appeared: ----------------------------------------- The problem seems to be caused by the following file: usbmm2x2.sys DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (Same 3 paragraphs as original post) Technical Information: *** STOP: 0x000000CB (0xF8851500, 0x81CF8030, 0x81CE9DD0, 0x00000003) *** usbmm2x2.sys - Address F8851500 base at F884F000, Datestamp 3C866436 Beginning dump of physical memory Dumping physical memory to disk: (numbers going up) ----------------------------------------- So what does all this mean and what am I supposed to do to fix it? I may be way off, but I did recently attach a MidiSport 2x2 USB interface to my computer for midi recording, but i don't record audio through it, so don't know why that would be a problem. I can sense we're almost there! Thanks for the help! |
|
Subject:RE: The Long Awaited Blue Screen of Death Message
Reply by: fulani
Date:2/8/2003 2:45:08 AM
jeepman: "So what does all this mean and what am I supposed to do to fix it?" CuzinB: "identify and update or remove the problem driver...(then)you should remove the TrackLockedPages value from the registry." I havent run this Reg. Test yet, but I have also gotten the PROCESS_HAS_LOCKED_PAGES error and I too am running XP with a midiman 2x2. -fulani |
|
Subject:RE: The Long Awaited Blue Screen of Death Message
Reply by: Vocalpoint
Date:2/8/2003 7:57:34 AM
Well...well...we have found our culprit. *** STOP: 0x000000CB (0xF8851500, 0x81CF8030, 0x81CE9DD0, 0x00000003) *** usbmm2x2.sys - Address F8851500 base at F884F000, Datestamp 3C866436 Okay - This could be a number of things: 1. Just cause you don't record through the Midiman, doesn't mean ACID is seeing it in a bad way. 2. Lots for folks have this unit but are not reporting issues. Could be a conflict with it and your specific machine. To Test - Get this thing out of your recording loop completely (uninstall, unattach etc etc) and see if your problem goes away (I bet it will). If it does - congrats. Just in case this is a real low level bug that may interest SF, you may want to forward it on to them. Final note - Between you, me and the fencepost - I had this interface about a year ago and took it back immediately...gave me all kinds of grief. Just went back to a cheap $45 Soundblaster Live and I use the gameport connector for my Midi IN. It's not pretty but I haven't had a single issue that I can remember. Congrats on finding the problem. Cuzin B |
|
Subject:RE: The Long Awaited Blue Screen of Death Message
Reply by: pwppch
Date:2/8/2003 9:37:25 AM
Cuzin, Thanks for going through this with jeepman. Jeepman, thanks for going through this painful excersise. Please, remove/uninstall the MIDISport and see if the problem persists. I have emailed MAudio, pointing them here for a review of the problems. If I find anything out from them, I will be sure to post the results here. Thanks again. Peter |
|
Subject:RE: The Long Awaited Blue Screen of Death Message
Reply by: Vocalpoint
Date:2/8/2003 10:11:57 AM
Peter, No problem. Always try to help when I can. Hope this is a driver issue and not something in the ACID infrastructure. Cheers, Cuzin B |
|
Subject:RE: The Long Awaited Blue Screen of Death Message
Reply by: luces
Date:2/8/2003 12:18:15 PM
No offense to MAudio, but I highly suspect it is the Midisport. I say this b/c I tried installing it on my laptop (w/o Acid installed) and I am using Win 98se on my laptop, and it completely locked up EVRYTHING! However , I am using the Audiophile 2496 card on my main box(also w/Win 98se) and it works like a charm! Jeepman, I know that things seem to be pointing to the Midisport, but I would also highly suspect that the "onboard" soundcard is way below standard to run something like Acid. Even though you may have a fast processor using an onboard card will definitely tax your system more than a dedicated soundcard. I also tried to use my onboard sound with Acid once upon a time, and it sounded very choppy and yes it made my system crash. Now with the Audiophile, I am able to run approx. 36-40 tracks with each having approx.3-5 FX in a chain per track. And all of this in glorious 96k 24 bit playback!!!! I know money is an issue for everybody, but you could probably find a decent deal on an SB card and I also use one of those as well. Good luck. system specs: 700 Athlon Win 98se 20gig main drive 80gig project drive Audiophile Card SB Live 5.1 card Ati Rage IIc Vid card |
|
Subject:RE: The Long Awaited Blue Screen of Death Message
Reply by: MarkWWW
Date:2/8/2003 1:04:07 PM
Ahah! This sounds like it might be another manifestation of a crash-to-blue-screen problem that shows up very occasionally with the MidiSport 2X2 (and 4X4 I think) in Sonar. M-Audio have just released a new beta version of the MidiSport drivers (V.4.1.20 beta) and early indications suggest that this may have solved the problem in Sonar. If the cause of your problem is indeed the same, and assuming the new drivers really do fix it (it's a bit too soon to tell for certain yet), there's a good chance they might solve the problem you're having with Acid too. Best of luck. Mark |
|
Subject:RE: The Long Awaited Blue Screen of Death Message
Reply by: pwppch
Date:2/8/2003 3:17:11 PM
Hard, if not impossible since we install no kernel code, for us to crash to a BSOD. Even if we were calling a MIDI i/o API wrong, the driver shouldn't crash to a BSOD. Again, thanks. Peter |