If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Blue screen using Regedit
Whenever I do a search within my registry, the search engine
always crashes into a Windows blue screen fatal error: "A fatal exception 0E has occured at 0028:C023A652 in VXD Perf(05) + 000001B6" I was able to trooubleshoot the Keys that cause the error and they a HKEY_DYN_DATA\PerfStats\StartStat HKEY_DYN_DATA\PerfStats\StatData HKEY_DYN_DATA\PerfStats\StopStat If I delete the \PerfStats root Key, the problem disappears but the keys are regenerated at boot up. What could the problem be ? Could it be a virtual driver that fails to install properly at startup ? -- Charles A. Gilbert CHUCK Electronics http://www.chucktronic.ca/ |
#2
|
|||
|
|||
Blue screen using Regedit
Have a read - see if this helps:
"Once every month or so, a client calls me with a typical Win9x problem: Windows has somehow trashed its own Registry. The damage is never quite the same twice. Typically, there's been an unexpected crash, followed by new and undesirable behaviors. Windows loses track of devices, loses user preferences, starts crashing sporadically, won't run certain processes, or what-have-you. The cause, apparently, is that Windows has crashed while in process of re-writing Registry data to the hard drive (which it seems to do very frequently). The next startup, it repairs the damage after a fashion, re-assessing hardware and such, but most often data is lost that can't be recovered. I manage to fix it manually about half the time, with device re-installs and such. The rest of the time, I usually have to reinstall Windows. The latest patient had lost its ability to run a video display -- any video display -- at any but the most basic setting: 16 colors, 640X480. Any setting involving higher resolution or more colors would cause a complete crash, or a totally out-of-sync display. Alternate video cards and driver re-installs did nothing. The system was squirrely in other ways too, running slowly, hanging on shutdown and prone to crashing for no apparent reason. After several efforts to deal with the symptoms, I concluded that as there was no backup, and since the Registry was virtually unrepairable, what the machine needed was to have Windows re-installed. BUT. The client, because of the many applications and the large amount of personal data on the system, didn't want that; except as an absolute last resort. I thought it over. When Windows trashes its Registry, it typically LOSES data. I have never yet seen it retain corrupted data; I think it usually either ignores or discards whatever may have been garbled. So, what I needed was -- if possible -- to somehow restore what was lost, while retaining what I had left of the Registry. I needed a functional new Registry onto which I could overlay the surviving Registry data. I formed a likely plan, and I did this: 1. Exported the entire Registry to a .reg file on the desktop. 2. Rebooted to a command prompt-only session. Typed in these commands: C:\attrib -s -h -r system.1st (This makes visible/movable the backup copy of the _original_ SYSTEM.DAT as first installed by Windows.) C:\attrib -s -h -r c:\windows\*.dat (This makes the current Registry files visible/movable.) C:\copy c:\windows\system.dat c:\windows\system.da1 C:\copy c:\windows\user.dat c:\windows\user.da1 (These commands create backups of the hammered Registry just in case.) C:\copy /y system.1st c:\windows\system.dat (This reverts the Registry to a new-Windows-setup state.) 3. Rebooted to Windows. It started up as if for the first time ever, demanding a product ID and so forth. It went all through the hardware recognition process, which I helped along at a couple of points. It required a couple of reboots to complete. 4. Once Windows was up and running properly, I immediately double-clicked on the .reg file I had earlier created. Regedit reported success importing its data. 5. Rebooted to a command prompt-only session. Typed in these commands: C:\attrib -s -h -r c:\windows\*.dat (This makes the hidden Registry files visible/movable.) C:\copy c:\windows\system.dat c:\windows\system.da2 C:\copy c:\windows\user.dat c:\windows\user.da2 (These commands create backups of the new "hybridized" Registry -- just in case.) 6. Rebooted to Windows. Tested all applications, various file associations, the video performance (of course), etc. Result: 100% success. Every app worked, video problems totally solved, no weird behaviors, Windows was starting and running much faster, and shutting down properly. I'm sure I'm not the first to think of this approach, but it's new to me, and I did think it up on my own. I think I can add a feather to my PC-Service-Dude propeller-beanie. pchelp OK, note this also: I just realized, steps 4 and 5 are reversed in my original account. I didn't back up the "hybridized" registry, I backed up the one I'd just built in the new-setup process. Then I incorporated the .reg file and rebooted without making a backup." pchelp "Chucktronic" wrote in message ... Whenever I do a search within my registry, the search engine always crashes into a Windows blue screen fatal error: "A fatal exception 0E has occured at 0028:C023A652 in VXD Perf(05) + 000001B6" I was able to trooubleshoot the Keys that cause the error and they a HKEY_DYN_DATA\PerfStats\StartStat HKEY_DYN_DATA\PerfStats\StatData HKEY_DYN_DATA\PerfStats\StopStat If I delete the \PerfStats root Key, the problem disappears but the keys are regenerated at boot up. What could the problem be ? Could it be a virtual driver that fails to install properly at startup ? -- Charles A. Gilbert CHUCK Electronics http://www.chucktronic.ca/ |
#3
|
|||
|
|||
Blue screen using Regedit
I know the procedure and I always keep a backup of my registry.
I tried to restore my backup more than one time and didn't solve my problem. Thnx anyway ... "Touch Base" wrote in message ... Have a read - see if this helps: "Once every month or so, a client calls me with a typical Win9x problem: Windows has somehow trashed its own Registry. The damage is never quite the same twice. Typically, there's been an unexpected crash, followed by new and undesirable behaviors. Windows loses track of devices, loses user preferences, starts crashing sporadically, won't run certain processes, or what-have-you. The cause, apparently, is that Windows has crashed while in process of re-writing Registry data to the hard drive (which it seems to do very frequently). The next startup, it repairs the damage after a fashion, re-assessing hardware and such, but most often data is lost that can't be recovered. I manage to fix it manually about half the time, with device re-installs and such. The rest of the time, I usually have to reinstall Windows. The latest patient had lost its ability to run a video display -- any video display -- at any but the most basic setting: 16 colors, 640X480. Any setting involving higher resolution or more colors would cause a complete crash, or a totally out-of-sync display. Alternate video cards and driver re-installs did nothing. The system was squirrely in other ways too, running slowly, hanging on shutdown and prone to crashing for no apparent reason. After several efforts to deal with the symptoms, I concluded that as there was no backup, and since the Registry was virtually unrepairable, what the machine needed was to have Windows re-installed. BUT. The client, because of the many applications and the large amount of personal data on the system, didn't want that; except as an absolute last resort. I thought it over. When Windows trashes its Registry, it typically LOSES data. I have never yet seen it retain corrupted data; I think it usually either ignores or discards whatever may have been garbled. So, what I needed was -- if possible -- to somehow restore what was lost, while retaining what I had left of the Registry. I needed a functional new Registry onto which I could overlay the surviving Registry data. I formed a likely plan, and I did this: 1. Exported the entire Registry to a .reg file on the desktop. 2. Rebooted to a command prompt-only session. Typed in these commands: C:\attrib -s -h -r system.1st (This makes visible/movable the backup copy of the _original_ SYSTEM.DAT as first installed by Windows.) C:\attrib -s -h -r c:\windows\*.dat (This makes the current Registry files visible/movable.) C:\copy c:\windows\system.dat c:\windows\system.da1 C:\copy c:\windows\user.dat c:\windows\user.da1 (These commands create backups of the hammered Registry just in case.) C:\copy /y system.1st c:\windows\system.dat (This reverts the Registry to a new-Windows-setup state.) 3. Rebooted to Windows. It started up as if for the first time ever, demanding a product ID and so forth. It went all through the hardware recognition process, which I helped along at a couple of points. It required a couple of reboots to complete. 4. Once Windows was up and running properly, I immediately double-clicked on the .reg file I had earlier created. Regedit reported success importing its data. 5. Rebooted to a command prompt-only session. Typed in these commands: C:\attrib -s -h -r c:\windows\*.dat (This makes the hidden Registry files visible/movable.) C:\copy c:\windows\system.dat c:\windows\system.da2 C:\copy c:\windows\user.dat c:\windows\user.da2 (These commands create backups of the new "hybridized" Registry -- just in case.) 6. Rebooted to Windows. Tested all applications, various file associations, the video performance (of course), etc. Result: 100% success. Every app worked, video problems totally solved, no weird behaviors, Windows was starting and running much faster, and shutting down properly. I'm sure I'm not the first to think of this approach, but it's new to me, and I did think it up on my own. I think I can add a feather to my PC-Service-Dude propeller-beanie. pchelp OK, note this also: I just realized, steps 4 and 5 are reversed in my original account. I didn't back up the "hybridized" registry, I backed up the one I'd just built in the new-setup process. Then I incorporated the .reg file and rebooted without making a backup." pchelp "Chucktronic" wrote in message ... Whenever I do a search within my registry, the search engine always crashes into a Windows blue screen fatal error: "A fatal exception 0E has occured at 0028:C023A652 in VXD Perf(05) + 000001B6" I was able to trooubleshoot the Keys that cause the error and they a HKEY_DYN_DATA\PerfStats\StartStat HKEY_DYN_DATA\PerfStats\StatData HKEY_DYN_DATA\PerfStats\StopStat If I delete the \PerfStats root Key, the problem disappears but the keys are regenerated at boot up. What could the problem be ? Could it be a virtual driver that fails to install properly at startup ? -- Charles A. Gilbert CHUCK Electronics http://www.chucktronic.ca/ |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Beginning dump of physical memory htoskrnl.exe brings blue screen | Rasoul Khoshravan Azar | Internet | 1 | July 12th 04 02:00 PM |
Blue screen of death | Irvin | Monitors & Displays | 1 | July 3rd 04 02:06 PM |
Blue Screen of Death on Bootup | JBarnett | General | 5 | July 2nd 04 01:24 AM |
Blue screen saying error at 0167:BFF74587 | Eeeel | General | 1 | June 12th 04 12:19 PM |
BLUE SCREEN when USB device plugged in | JDP | Plug & Play | 2 | June 5th 04 09:20 AM |