BSOD mainly while using Firefox

[Dantzeil]

Hi all first time posting here. Been encountering BSODs while using firefox recently. Heres what i copied from the BSOD screen.

STOP: 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF80002CE9E11, 0xFFFFF880039695C8, 0xFFFFF88003968E20)

I've posted in some other forum before and some guys told me its a RAM issue. Been using chrome since. Just now it BSOD-ed while i was playing Crysis 2 but im not sure if i had firefox running in the background.

Windows 7 . . .
- 64-bit
- the originally installed OS on the system
- Full retail

- Age of system (hardware): Bought in June 2010
- Age of OS installation: No re-installations since June 2010

Can it still be saved or is it screwed?

 

[zigzag3143]

Hi all first time posting here. Been encountering BSODs while using firefox recently. Heres what i copied from the BSOD screen.

STOP: 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF80002CE9E11, 0xFFFFF880039695C8, 0xFFFFF88003968E20)

I've posted in some other forum before and some guys told me its a RAM issue. Been using chrome since. Just now it BSOD-ed while i was playing Crysis 2 but im not sure if i had firefox running in the background.

Windows 7 . . .
- 64-bit
- the originally installed OS on the system
- Full retail

- Age of system (hardware): Bought in June 2010
- Age of OS installation: No re-installations since June 2010

Can it still be saved or is it screwed?

These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[Dantzeil]

Just now it crashed even when i was using chrome.
STOP: 0x000000D1 (0x0000000000200018, 0x00000000000000002, 0x0000000000000000, 0xFFFFF88003C2D2A3)

Then it rebooted and did a scan on the hard disk by itself and then crashed again.
STOP: 0x0000003B (0x00000000C0000005, 0xFFFFF80002CF8A10, 0xFFFFF88003FD3EC0, 0xFFFFF88003C2D2A3)

Will now try what zigzag3143 suggested and update again.

Edit: Memtest for 2 hours before i was bored to death and decided to do it at night.

 

[Dantzeil]

Sorry for the late reply, finally got memtest to work for 7 hours and 7 passes. 0 errors.. so it means memory isnt causing the BSOD?

 

[zigzag3143]

Sorry for the late reply, finally got memtest to work for 7 hours and 7 passes. 0 errors.. so it means memory isnt causing the BSOD?

Probably not rarm, now for verifier!

 

[Dantzeil]

What is the aim of the verifier test? If there are no BSODs, means everything is alright?

 

[zigzag3143]

What is the aim of the verifier test? If there are no BSODs, means everything is alright?

Not necessarily. It means you just havent used the driver that makes it crash in the sequence that crashes it. May take 36 hours sometimes more.

 

[Dantzeil]

Then when should i stop it?

 

[zigzag3143]

Then when should i stop it?

If it hasnt crashed after 24 hours of continuous use you can disable it. If it does BOSD please upload the DMP file.

 

[Dantzeil]

Does it necessarily have to be continuous use? i do not think i can hold out that long. Shld i stop once i get one bsod? I think my computer will give me bsods the whole time