Fake windows xp shutdown error with bsod

->>>> Click Here to Download <<<<<<<-

All the dumps are the same, and this points to a software problem. I've seen the stack info in the dumps before, but without a resolution. Something common to both is software from either Veritas Software or Sonic Solutions. Try updating whatever this is. One of the files is drvmcdb. Customer has had problem for about a year now, and is only just trying to get it sorted now. It doesn't seem like hardware because it is not random, just on shutdown and always exactly the same.

Click to expand Run it up, get online, then go offline, do a System Tools disk Cleanup and shutdown. Any change? No - hit restart, use Internet Options DON'T go online and delete cookies, files including offline and history and shutdown. CCT said:.

On start-up, run HijackThis and do a printout. Then, after going online and then offline repeat. Any differences in running programs? Similar threads P. Wi-fi card software causing memory parity crash -BSOD errot. Pete Williams Sep 30, Ask a Question. Learn why people trust wikiHow. Download Article Explore this Article methods. Tips and Warnings. Related Articles. Article Summary. Method 1. Save your work.

Forcing a Blue Screen on your computer will cause you to lose any unsaved changes, therefore it is very important for you to save anything you were working on before continuing. Search "regedit. You can do this by selecting "Edit" and then going to "New. Your default may already be set to this option. Reboot your computer. Close the Registry Editor and restart your computer in order for the changes to take effect.

Force a Blue Screen. You can do this by holding down the furthest most right "Control" key then pressing the "Scroll Lock" key twice. Once this is completed, a blue screen should pop up. If you are using Windows 8 or later, the Blue Screen is slightly different. Rather than lines of code, Windows 8 and later presents you with a sad emoticon and an error message.

This, however, is still the BSoD. Method 2. Open the Task Manager. This method will only work for Windows 8 and lower. You can open Task Manager by right-clicking on the taskbar at the bottom of your screen and finding "Start Task Manager" in the drop down menu that appears.

Select the "Details" tab. If you are prompted for an administrator password, enter the password and click OK. Once you have done so, select "End Task. Wait for a dialog box to appear. In this dialog box, tick the box next to "Abandon unsaved data and shut down" and click "Shut Down.

Enjoy your blue screen! You can get rid of the blue screen by restarting your computer. Method 3. It is safe, unless you have unsaved work or, in rare circumstances, your startup files were corrupted in the process. You can also do it in a virtual machine if you want to not damage your own computer. Not Helpful 11 Helpful It sounds like the OS was doing a major file transfer, and the files got corrupted.

The only thing you can do is reinstall the operating system. Not Helpful 13 Helpful Not Helpful 8 Helpful Technically, this could corrupt files. It may even return at a later time; we'll see. In reply to Code Cheese's post on April 4, I gave you 2 suggestions. Did you get them? DD's post on April 4, The next time I have access to his machine, it will probably have a fresh install of xp. So most of what would be mentioned here would be theoretical unless someone has experienced this exact situation before.

I'm open to anything. I understand my not being able to try things will probably deter people from trying to add input, but that's fine as well. Download BlueScreenView from here:. Unzip and run it BSV installs nothing and let it finish scanning all your crash dump files.

If you double click on of the dumps, you will get some information about it including the Caused By Driver field and you may be able to spot the problem right away - especially if you see a pattern in the dumps where the Caused by Driver field is the same start with that driver. BlueScreenView tries to locate the right driver or module that caused the blue screen by looking inside the crash stack. Select highlight one or more of the most recent dump files by clicking them and holding down the Ctrl key to select multiples files.

Try to select just the most recent ones that relate to your issue maybe five or so dump files to get started. Open BSOD. Send the information from the last 5 memory dumps if you don't have 5 memory dumps yet, send the most recent ones you have.

This site in other languages x.