• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

System Error

P

paperroll

Junior Member


Source: System Error
Category: 102
Event ID: 1003

Error code 1000007e, parameter1 c000001d, parameter2 804d8f25, parameter3 f7c7dc78, parameter4 f7c7d978.

Sorry if this has been posted before. I did a quick search and couldn't find any similar topics.
 
This is a class of event that you typically see only when a driver for some hardward device has failed in such a way that it prevented the OS from getting any additional information about the failure. All Windows knows is that something in the hardware layer went down and took the system with it. It could be almost anything. I've seen this error when crashing while tweaking an overclock, and I have seen it when BF2 locked up hard when I was having dual core problems.
 
the c000001d exception is not a common one.

ping DClive and see if he'll debug it for you (or call Microsoft).

You can also just throw some general kernel troubleshooting at it:
update all drivers and firmware.

How often is this happening?
 
Maybe once or twice a day. When I turn it off and turn it back it says "Windows has recovered from a serious error" even though it didn't crash or anything.

"szAppName : Drivers.Display szAppVer : 10024E480000021002
szModName : ati2dvag.dll szModVer : 6.14.10.6561 Offset : B43C06EA "

After mutiple shutdowns for the past several weeks it finally says it shutdown due to hardware failure.

My 9800 Pro

Should I just update the driver and I'll be fine?
 
In startup and recovery options (system properties), set your computer to capture a kernel dump and tell it not to reboot after a crash.

Get a copy of the minidump and PM me for my email addy. I can run the minidump through a debugger and at least tell you what was at the top of the stack when the crash happened. This may or may not indicate the culprit.

Save the kernel dump file (memory.dmp) for someone with better debugging skills (dclive does these as a hobby, try reaching him).

Get every driver on your system updated. This means video, chipset, sound, SATA, you name it. Update system bios.
 
If reinstalling latest video drivers doesn't fix it, then:

This "serious error" crap also used to happen to me and nothing was wrong with my PC. It's a known bug and in the MS KB. Just turn off the serious error reporting if doing the page file workaround they have in the following article does not work. I think it worked for me in the first reboot and it still persisted after that and then I decided to turn it off altogether.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q317277

Good luck.
 
Fwiw, I have never seen an erroneous error of this kind. They always occur after a hard crash.

OP, not surprised that it is located in the video driver, as that is where mine all came from as well. If updating the drivers doesn't do it, then it is probably hardware related. I saw similar errors when my previous GeForce card's fan stopped and it overheated.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top