BSOD with various messages

Code:

BugCheck 7F, {8, 80050031, 6f8, fffff80002ed9ef6}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Code:

Usual causes:  Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

Code:

2: kd> k
Child-SP          RetAddr           Call Site
fffff880`02f6ace8 fffff800`02ecd129 nt!KeBugCheckEx
fffff880`02f6acf0 fffff800`02ecb5f2 nt!KiBugCheckDispatch+0x69
fffff880`02f6ae30 fffff800`02ed9ef6 nt!KiDoubleFaultAbort+0xb2
fffff880`0bd91f00 00000000`00000000 nt!MmAccessFault+0xd6

The system seems to have crashed, due to a exception (error) occurring during the processing of another exception. The exception which seems to have been a memory access fault, this is usually drivers referencing memory which is invalid or not present, therefore the MmAccessFault routine is called, which is essentially the exception handler for the access fault.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

Please also enable the Special Pool option, it should be listed underneath "Select individual settings".

awesome.. i will try that!! thanks :)

Hi!
I have been running the Driver Verifier, according to your instructions, for about 24 hours now (with a few hours off when i went to work). I have had no blue screens, but have had two of the other kinds of crashes. One when the screen just goes black, and another where the screen goes white with a lot of static lines across it. In both of these instances when this happen I am left with no option but to power off and restart the computer with the on/off switch to get it going. Are these the same as a blue screen? Do they create the dump files too?

You may disable Driver Verifier, and those not related to BSODs, a black screen is usually a hardware incompatibility issue or hardware failure.

• RAM - Test with Memtest86+

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Arc said:

No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

Ok, thanks I will try that also. However, I have just found out that I was not running the driver verifier properly. I had gone in to check the special pool option, but there I think i needed to also re-tick the Force pending I/O requests and IRP Logging. Which I had ticked on page before, but was lost when i went into individual settings selection. When I did that, it also required that I tick I/O verification to allow the force pending I/O requests. So I did that. Once i restarted my system, the crashes started right away. But they were not BSOD. They were just screen freezing.. looking like either a white or blue screen.. depending on what background had been at time of crash, with static lines in it. Only way to get system back on was to force a reboot by powering off and on. It crashed repeatedly either on start up.. or very soon after the moment I tried to operate anything. This happened about 5 times within minutes of turning on verifier. I turned it off at that point. Should I run the verifier for 24 hours if it is doing this, and not creating BSOD? Will it record what you need to see?

After the MemTest86+ test, go back into Driver Verifier, and then enable all the individual driver settings, apart from the Low Resources Simulation.

thanks will do. A question on the Memtest. How do i know if i only have one RAM stick. MY laptop came with 8g RAM. Would that be one stick?

Check your laptop support page, and it's most likely like 2x4GB sticks.

Ok, tried the Memtest. However the computer black screens every time without even completing one pass. You are right, there are two memory sticks. Do i take it that it is a hardware problem and send it to the warranty people for repairs?

Do you have warranty? If so, I would use it.