Qosmio x505-q870 BSOD constantly, dying?

vae victus

Honorable
Feb 1, 2013
17
0
10,570
Hi, i was here over a year ago trying to upgrade my ram from the stock 4 gb 1066 1.5v to Patriot 8 gb 1600 1.35v which failed (even though official sources said it'll work, crucial.com as well as toshiba's website) then down to Corsair 8 gb 1333 1.5v ram which now runs to another problem where my laptop BSOD all the damn time. I havent tried using it in months, but now that i'm about to start traveling i really need to fix this asap as im also short on funds to buy a new one. The BSODs occurred before the ram change though.

I've factory reset the laptop a coupla times already but still hasnt solved the problem. I've also updated the bios to v2.9 when i was doing the ram upgrading in my quest to make the 8gb 1600hz ram work (trying to mess with the voltage), so i was wondering if the new bios is messing everything up.

The most common BSOD are memory_management, cache_manager, IRQL_not_less_or_equal, bad_pool_header, pen_list_corrupt, page_fault_in_non-paged_area, and a few others i dont remember. They strike at any time, usually when i try to run programs or browse the net. The fact that it still happens after a factory reset is freaking me out.

Yea so the first several BSOD were mostly the memory related ones so i figured i had bad ram. However after swapping in the new ram (corsair 8gb 1333), i'm still getting the same issues. It might still be the ram, but i'm also thinking of putting the ram in the other memory slots, might be a slot issue. Of course i dont have a clue where the other memory slots are and i cant find any videos or documentation talking about the extra unused memory slots.

I'm coming here begging for help. Last year i was hopeful in upgrading my laptop for better game performance, now i just want the thing to work, as long as its stable browsing and watching videos, i dont care if i play another game on it again.

Also i live the 18.4 inch screen... i have a hard time going back...
 
Solution
From Microsoft:

Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows Advanced Options...

armapker

Distinguished
May 19, 2012
190
0
18,910
From Microsoft:

Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.

Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update.

Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk.

Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.

Also, have you updated your chipset driver? If you give me your OS I can provide that for you
 
Solution