cjseymour
asked on
Getting BSOD with message 0x0000007E (0xC0000005 0xF3577B52 0xF7C393FC F7C390F8) since install of flat screen monitor drivers
I started getting the message shown above after installing the ".inf" file while updating my monitor to a Dell 1905FP flat screen.
Everything worked fine when I physically replaced my old monitor with the new one, but the problem occurred when I was trying to install the correct drivers for the monitor.
When I tried to install the drivers using device manager and the Dell CD, Windows would never find the driver, so I opted to open the CD in Windows Explorer; right-clicked on the 1905FP.inf file and selected install.
Now when I start the PC I get BSOD when performing a normal boot, or any other flavor after F8, except Safe Boot. When I Safe Boot I cannot change any monitor settings and have a "default monitor" setup according to Display Properties. The drivers option is not accessable as the proerties option is grayed out from the Display Properties/Advanced/Monito
I have read other answers that cover the 0x0000007E issue, and haven't gained any further insight to the problem. The 0x0000007E error seems to be so wide-ranging.
Any guidance with debugging this situation would be appreciated.
Thanks,
Chris
Everything worked fine when I physically replaced my old monitor with the new one, but the problem occurred when I was trying to install the correct drivers for the monitor.
When I tried to install the drivers using device manager and the Dell CD, Windows would never find the driver, so I opted to open the CD in Windows Explorer; right-clicked on the 1905FP.inf file and selected install.
Now when I start the PC I get BSOD when performing a normal boot, or any other flavor after F8, except Safe Boot. When I Safe Boot I cannot change any monitor settings and have a "default monitor" setup according to Display Properties. The drivers option is not accessable as the proerties option is grayed out from the Display Properties/Advanced/Monito
I have read other answers that cover the 0x0000007E issue, and haven't gained any further insight to the problem. The 0x0000007E error seems to be so wide-ranging.
Any guidance with debugging this situation would be appreciated.
Thanks,
Chris
Its the driver for sure, Check if gecko's suggestion will work then try uninstalling the driver following these steps.
Click Start, right-click My Computer, and then click Properties.
7. In the System Properties dialog box, click the Hardware tab, and then click Device Manager.
8. In Device Manager, expand the Monitors node.
9. Right-click the Montitor device, and then click Uninstall.
10. On the Device Manager toolbar, click Action, and then click Scan for hardware changes to reinstall the device with an uncorrupted driver.
11. Restart your computer in Normal mode.
Click Start, right-click My Computer, and then click Properties.
7. In the System Properties dialog box, click the Hardware tab, and then click Device Manager.
8. In Device Manager, expand the Monitors node.
9. Right-click the Montitor device, and then click Uninstall.
10. On the Device Manager toolbar, click Action, and then click Scan for hardware changes to reinstall the device with an uncorrupted driver.
11. Restart your computer in Normal mode.
Also you can do a manual search for the file and delete it. Then when you restart you'll get the unknown driver pop up asking for the upgrade driver.
Bugcheck code 7E is usually caused by the faulty ram. Reseat the memory stick to another memory slot may resolve the problem.
https://www.experts-exchange.com/questions/21299105/Blue-Screen-of-Death.html
https://www.experts-exchange.com/questions/21312265/XP-intermittent-crash.html
https://www.experts-exchange.com/questions/21363977/URGENT-Windows-XP-Stop-Error.html#13712378
If reseat memory does not work, rum memtest to stress test the ram (http://www.memtest86.com)
https://www.experts-exchange.com/questions/21299105/Blue-Screen-of-Death.html
https://www.experts-exchange.com/questions/21312265/XP-intermittent-crash.html
https://www.experts-exchange.com/questions/21363977/URGENT-Windows-XP-Stop-Error.html#13712378
If reseat memory does not work, rum memtest to stress test the ram (http://www.memtest86.com)
ASKER
cpc2004,
I reseated the memory sticks and this didn't solve the problem. I will try memtest laster tonight.
Thanks,
Chris
I reseated the memory sticks and this didn't solve the problem. I will try memtest laster tonight.
Thanks,
Chris
ASKER
moh10ly,
I checked for the monitor node under Device Manager and it is * not * there. I rescanned and it did not find the device. Any thoughts?
Also, what do you mean by performing a manual search and delete of the driver in your second message?
Thanks,
Chris
I checked for the monitor node under Device Manager and it is * not * there. I rescanned and it did not find the device. Any thoughts?
Also, what do you mean by performing a manual search and delete of the driver in your second message?
Thanks,
Chris
If it is a faulty ram error, you will have a huge Dr Watson log with a lot of access violation error messages failing at diferenet modules.
C:\Documents and Settings\All Users\Documents\DrWatson\d
If it is true, you will to replace the memory stick.
C:\Documents and Settings\All Users\Documents\DrWatson\d
If it is true, you will to replace the memory stick.
ASKER
cpc2004,
I checked for any Dr Watson files under C:\Documents and Settings\All Users and there were none. How do I check if Dr Watson is activated on my machine?
Also, I have two memory sticks that I reseated in different combinations, and they all produced the same BSOD.
Thanks,
Chris
I checked for any Dr Watson files under C:\Documents and Settings\All Users and there were none. How do I check if Dr Watson is activated on my machine?
Also, I have two memory sticks that I reseated in different combinations, and they all produced the same BSOD.
Thanks,
Chris
Refer this webpage
http://support.microsoft.com/default.aspx?scid=kb;en-us;308538
Maybe one of the memory stick is bad. Take out a memory stick.
http://support.microsoft.com/default.aspx?scid=kb;en-us;308538
Maybe one of the memory stick is bad. Take out a memory stick.
Cjseymour, i meant that you open my computer and search for the file .inf and delete in safe mode, when you restart your computer in normal mode, it'll ask you for the driver file, so it'll cancle the one that made the error.
Or trying to restore to an earlier point, using system restore on safe mode.
Good luck
Or trying to restore to an earlier point, using system restore on safe mode.
Good luck
ASKER
moh10ly,
There is no .inf file matching the name of my Dell flat screen monitor, and when I renamed the oem.infs to oem.inf.xxx the system still failed.
I cannot run a system restore as I had turned the feature off.
There is no .inf file matching the name of my Dell flat screen monitor, and when I renamed the oem.infs to oem.inf.xxx the system still failed.
I cannot run a system restore as I had turned the feature off.
ASKER
cpc2004,
I have checked the attributes according to the KB article and there are no Dr Watson log files. I am also confused as I don't see any event 1001's in my event log, and I was of the understanding that I would see one every time I had a BSOD. If this were the case I would post a mini dump for analysis.
I have checked the attributes according to the KB article and there are no Dr Watson log files. I am also confused as I don't see any event 1001's in my event log, and I was of the understanding that I would see one every time I had a BSOD. If this were the case I would post a mini dump for analysis.
Have you tried sfc/scannow , this command will scan the system files on your system and if there's any bad system files, will replace them with the original once, probably you'll have the windows cd near you.
Do you partition your hard disk or do you have more than one hard disk?
ASKER
cpc2004,
I have two HDDs in my PC and both have a singla partition on them. This has been consistant for a while and the configuration has not been changed recently. What are you thinking may be the issue? Let me know if I can provide more information.
I have two HDDs in my PC and both have a singla partition on them. This has been consistant for a while and the configuration has not been changed recently. What are you thinking may be the issue? Let me know if I can provide more information.
ASKER
moh10ly,
I will try your suggestion when I get home tonight and will post the results. Thanks to you and cpc2004 for your help.
I will try your suggestion when I get home tonight and will post the results. Thanks to you and cpc2004 for your help.
Also have alook at this link:-
http://windows.about.com/od/performancetopics/l/aa030599.htm
The driver you have on your system need to be uninstalled and you need to log on to your account anyhow, Try using windows 2000 cd, to boot into windows xp box. you can use the windows 2000 cd to boot into the recovery console and then act in windows xp like if you are an admin.
http://windows.about.com/od/performancetopics/l/aa030599.htm
The driver you have on your system need to be uninstalled and you need to log on to your account anyhow, Try using windows 2000 cd, to boot into windows xp box. you can use the windows 2000 cd to boot into the recovery console and then act in windows xp like if you are an admin.
Do you have minidumps at the folder \windows\minidump? Maybe you disable the minidump option.
Enable minidump option
Control Panel --> System --> Advance --> Startup and Recovery --> Write debugging information --> Tick minidump
If the minidump option is enabled and no minidump was captured. Maybe your system is configured with a separate partition for disk cache (ie not the default c drive). Or your paging space is allocated not at drive c:.
Modify the dump setting to minidump. Do you get any usuall message such as "If your C partition is configured with less than 0 MB cache, it is possible that a log file cannot be stored".
Enable minidump option
Control Panel --> System --> Advance --> Startup and Recovery --> Write debugging information --> Tick minidump
If the minidump option is enabled and no minidump was captured. Maybe your system is configured with a separate partition for disk cache (ie not the default c drive). Or your paging space is allocated not at drive c:.
Modify the dump setting to minidump. Do you get any usuall message such as "If your C partition is configured with less than 0 MB cache, it is possible that a log file cannot be stored".
ASKER
moh10ly,
I ran the sfc /scannow command and received the following error:
Windows File Protection could not initiate a scan of protected system files.
The specific errror code is 0x000006ba [The RPC server is unavailable.].
Any suggestions?
I ran the sfc /scannow command and received the following error:
Windows File Protection could not initiate a scan of protected system files.
The specific errror code is 0x000006ba [The RPC server is unavailable.].
Any suggestions?
ASKER
cpc2004,
The minidump option is selected (actually it is"Small memory dump (64KB)") with the directory set to %systemroot%\Minidump. The last file in that directory is dated 4/25/05 and was written before I started with the BSOD problem.
The minidump option is selected (actually it is"Small memory dump (64KB)") with the directory set to %systemroot%\Minidump. The last file in that directory is dated 4/25/05 and was written before I started with the BSOD problem.
ASKER
I have increased the point value; so if anyone has been watching from the sideline and has not chimed in with a suggestion, here is your incentive. I am pretty close to reinstalling Win XP, so your help would be appreciated.
Do you find any red alert event at system event log when your windows crashes? Attach your the minidump mini042505-01.dmp to any webspace. Maybe I can find out some clues on the dump.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I am sorry to say that I had to resort to format/reload windows/restore backup files to recover my PC. I am sure there was a logical solution to the problem at hand, but I don't have enough time to tinker around anymore.
moh10ly,
I tried all the RPC stuff you suggested, but even in Recovery Console I couldn't get things to run properly. Thanks for all you help.
cpc2004,
I didn't get a chance to tell you that Memtest ran fine and produced no errors. Thank you for all your advice.
LeeTutor,
Can I split the points between moh10ly and cpc2004? I don't know if it is acceptable to give points without an answer, but they both hung in there and provided me with a wealth of great ideas. Let me know.
moh10ly,
I tried all the RPC stuff you suggested, but even in Recovery Console I couldn't get things to run properly. Thanks for all you help.
cpc2004,
I didn't get a chance to tell you that Memtest ran fine and produced no errors. Thank you for all your advice.
LeeTutor,
Can I split the points between moh10ly and cpc2004? I don't know if it is acceptable to give points without an answer, but they both hung in there and provided me with a wealth of great ideas. Let me know.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Other then that I can only suggest that you get your minidumps and upload 4 or 5 of them to a website :) So that other experts can analyse them or w/e you wanna call it to help us a little more with regards to solving your problem :)