The Terror of the Blue Screen Error after Windows Update
A windows update popup on the screen for available update, so I clicked ok then restart. Within few minutes after the system startup, the computer magically shuts down then displays a blue screen error for seconds before dissapearing. And everytime I log in, it shuts down and shows the error again. It was a never ending loop.

Noooo!!! I panicked, the laptop was just weeks old since we bought it. Did it just crash? I only clicked for windows update or didn’t I? Was it a conflict with the Norton anti-virus update? Because I saw norton just finished an idle update before the windows update. I didn’t update any other software/hardware too. Was the laptop I got simply faulty?
It came to the point where I got so impatient searching the net for answers. Typing keywords after keywords of BCCODE 1000007e, Vista blue screen error, Stop 0×00000050, Windows minidump, disabled Consumer IR Devices, HP dv4 blue screen error, norton and windows update conflict, random crash, corrupt hard drive to System Restore but nada, coudn’t really determine how to mend it. I was frustrated and was already planning to go to Staples (where we bought it) for a fix.
I was already in the process of having a headache from reading different post/forums and my eyes already dry and slightly red. Then, the phone rang, it was a good excuse to take my glued eyes off the monitor. Bu was on the other line, he suggested to look for KB973879 error. It seems that the recent windows update is causing Windows Vista 64-bit edition the blue screen error, especially affecting the HP Pavilion dv series laptops and few cases for other manufacturers.
In safe mode go to:
Control Panel -> Programs and Features -> Installed Updates
Select KB973879 updates -> Uninstall
Restart
Suggested site: TECHERATOR for detailed repair. Just uninstall KB973879 and viola! It did solve the issue. I am just glad that my lappy is running and normal again
All these process made me … HUNGRY! Now let me attack some food! ^_^

I got into same problem. Thanks!! This solved it.