Random BSODs after updating dv6-6135DX's BIOS

I bought the HP Pavilion dv6-6135DX around a month and a half ago and for a month it worked beautifully. After I learned how easy it would be to overclock I set about updating it completely in preparation so everything should work perfectly. However after updating the BIOS to the F.21 revision my laptop started randomly giving me BSODs (without any overclock applied). After viewing with BlueScreenView it seems most of my BSODs are SYSTEM_SERVICE_EXCEPTION errors related to my ntoskrnl.exe. I can't seem to find how exactly to fix this problem so any help I can get would be appreciated.

This is a link to my minidumps if it helps at all: http://dl.dropbox.com/u/347853/Minidump.rar

 

Try update the BIOS again? and man.. that is alot of BSODs in a week. Try do a memtest.

 

I want to ask the question, were you running the F.1A or F.20 BIOS previously? I have the F.21 bios installed and have random BSOD(I updated the BIOS first thing when I bought it). I somehow doubt I will get a reply after so long.

F.20 contains update information that says it as updated to fix a 0x101 stop error while running STALKER benchmark. I'm thinking either that fix messed things up, OR that this fix was removed in F.21.

I am going to try all the BIOSes and see if any fix my problem (which is identical to a T!). If the older ones fix it, there will be a lot of happy dv6-3135DX owners!

If either gets rid of the problem, I will bring it to HP's attention and ask for a REAL fix.

 

*edit* Sure enough, the video bios was reverted to one dated 2001/04/06 with F.20. I will run this for now and see if the BSOD come back (I'lll leave Melty Blood:AACC on all night in demo mode with Crossfire enabled). If it goes away, then I will call this problem solved and go yell at HP for releasing an unstable POS bios.

 

No sure what happened on the above post there. I planned to edit my original post.

F.20 was a flop? (I might need to fix my strange driver config), installing F.1D

 

Solved!

HP issued a software fix for windows on 11/23/2011.

I found this while looking at the dv6-6135dx support page, under the "show
Operating System - Enhancements and QFEs" section. Seriously, this should be under a category called "critical system updates," where people will look for a show stopping BSOD fix?!

sp55279.exe

This fix applies to the following laptops:
DEVICES SUPPORTED :
Compaq 435 Notebook PC
Compaq 436 Notebook PC
Compaq Mini CQ10 NetBook PC
Compaq Presario CQ57 Notebook PC
HP 2000 Notebook PC
HP 430 Notebook PC
HP 431 Notebook PC
HP 435 Notebook PC
HP 630 Notebook PC
HP 631 Notebook PC
HP 635 Notebook PC
HP ENVY 14
HP ENVY 17
HP ENVY Envy 15
HP ENVY Envy 17
HP Folio 13 Notebook PC
HP G4 Notebook PC
HP Mini 110 NetBook PC
HP Mini 210 NetBook PC
HP Pavilion dm1 Notebook PC
HP Pavilion dm4 Notebook PC
HP Pavilion dv4 Notebook PC
HP Pavilion dv6 Notebook PC
HP Pavilion dv7 Notebook PC
HP Pavilion g4 Notebook PC
HP Pavilion g6 Notebook PC
HP Pavilion g7 Notebook PC
Presario CQ43 Notebook PC
Presario CQ57 Notebook PC

ENHANCEMENTS:

Includes the following fix from Microsoft Knowledge Base Article:
KB2584454 - FIX: "0x0000003B" Stop error when you run certain applications in Windows 7 or in Windows Server 2008 R2
KB2551127 - FIX: "0x0000010E" Stop error occurs on a computer that uses hybrid graphics in a heterogeneous GPU configuration and that is running Windows 7 or Windows Server 2008 R2
KB2505454 - FIX: The startup process is delayed on a computer that has a large hard disk installed and is running Windows 7 or Windows Server 2008 R2
KB2550648 - FIX: The English (India) keyboard is not listed after you add the Rupee supplement to an English version Windows 7 image

 

Didn't appear in my DV6 support page.. but i install it anyway. Thanks for the heads up.

 

I had better luck downloading the actual KB2551127 from Microsoft. Every time I save changes or reset defaults to the BIOS, I must uninstall and reinstall this (hence, I better stop making changes DUR).

I took the KB apart trying to figure out what it actually does (so its only theory so far). I think it might by sending EEPROM changes to switch hidden features in the BIOS. Still exploring it.

I guess the KB addresses issues with the graphics switching.

From my research, it appears that after flashing the video BIOS (which is included in F.21), some users who were perfectly fine start experiencing this issue. F.20 also has a Video BIOS update, but I experienced the same issues. The original BIOS does not appear to contain Video BIOS code, so there is no TRUE way to flash back to original shipping.

This applies to the dv6-6135DX though. I don't know about other dv6 models.

I am still testing this out. I'm not 100% its actually working. I managed to run Heaven Benchmark for 8 hours+ overnight after installing in duel mode.

*edit* Update didn't help me, I'm returning this thing. I'm done with it.