Blue screen of death AHH the horror
ok well when ever i start doing anything important on my computer, it laggs up then BLUESCREENOFDEATH's on me the code stop codes are 0x00000007e (0x00000005, 0x800190e3, 0xf789e754, 0xf789e450) anyone have any idea on how to fix this?1 person needs an answerI do too
April 18th, 2010 2:43pm

Perhaps there was a mistranscription? Is the second hex number perhaps 0xc0000005? Can you upload the contents of c:\windows\minidump to your SkyDrive and provide a link?
Free Windows Admin Tool Kit Click here and download it now
April 18th, 2010 6:18pm

http://cid-74a41dfa601060e6.skydrive.live.com/home.aspx Hope it helps
April 19th, 2010 10:13am

The frequency and variety of the bugchecks, and that one of the dumps was corrupted, suggests memory corruption is occurring. This can be caused by faulty hardware such as RAM, or a buggy driver/kernel-mode component (legitimate, or malware). Consider scanning your system for malware with e.g. MalwareBytes AntiMalware (the free version) Check out the following general suggestions: Consider running chkdsk on all partitions. Let chkdsk complete on each partition and see if that helps. It can be helpful to use Driver Verifier. To enable Driver Verifier... start->verifier.exe->OK->Create standard settings- >Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out of the dialog. Then, reboot and use the system as you normally would, and wait for a problem. In the event that the system does not boot completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes. Wait for a bugcheck to occur after enabling verifier as described, and then upload it. Also consider running SFC /SCANNOW. If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot? Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily good memory - it just hasn't failed a test. Consider systematically eliminating RAM from the system - run with a couple of modules for a while, and see how things go. Then try the other modules. Other common suggestions include ensuring drivers are up to date (including video drivers), as well as ensuring that you're using the latest BIOS.
Free Windows Admin Tool Kit Click here and download it now
April 19th, 2010 1:57pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics