Random BSOD

lsuk · 08 Jan 2010

Hello everyone,

I was wondering if you can help me out.
I got a brand new computer on Black Friday and everything was great until January 2nd. That is when my first BSOD happened. I hadn't installed anything recently, but all of a sudden I am getting frequent BSOD. I thought it was my Norton Internet Security, so I uninstalled that, but nope, got one today. If you can look into my minidump log and let me know the culprit, I would really appreciate it. I included all the minidumps I had since the 2nd of January. Thanks in advance.

theog · 08 Jan 2010

As unit is BRAND NEW, take back to retail to check out.

**Pauly** · 08 Jan 2010

Would prob be easier to return it as above, if you cant heres the breakdown

All dumps are different
0xBE ATTEMPTED_WRITE_TO_READONLY_MEMORY
0x3b SYSTEM_SERVICE_EXCEPTION
0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
0x50 PAGE_FAULT_IN_NON_PAGED_AREA

This is probably a driver error, but to start with

Some things to try:
If your OCing stop until this is sorted
Check your drivers are up to date
Run HDD checks HD Diagnostic
Run RAM checks Memory Diagnostics
Open elevated command prompt(start>search>cmd.exe>right click run as admin)type>sfc /scannow

See how you get on post back your results
Hope this helps let us know if you need further assistannce

Paul

lsuk · 08 Jan 2010

Thanks for your quick response.
I wish I can return it, but the return policy has expired so I can't return it.
I called HP's technical support, but after running some test they said it should be a driver and not a hardware problem. I have tried the sfc / scannow last night, but no error was found. HP has a diagnostic program, which HP tech and I have ran 5 times. It test the memory and harddrive and the result shows that all the hardware is still intact. I also tried the verifier program to see if any drivers were causing the problem, but I haven't had a BSOD yet. Should I just go through each driver in device manager and update the drivers? All help is really appreciated.

**Pauly** · 08 Jan 2010

Yes i would update all drivers possible, but dont use the update driver feature or windows update actually go to the manufacturers website for each piece of hardware installed and manually get the lastest driver for that piece of equipment.

Not sure what program HP got you to run, might be worth running the diagnostics linked in the post above just to be on the safe side.

Other than that driver verifier is your best option IMO, if the problem remains it will blue screen sooner or later as driver verifier stresses out the driver concerned, if not the problem might be gone if you already updated some.

See how you get on, post back your results and we can help further if needs be
All the best

Paul

lsuk · 08 Jan 2010

Thank you Pauly for your quick response. I did update the Nvidia GE Force 9100 driver this morning and will try to update the audio drivers later tonight. I think it was from the drivers I downloaded from the HP drivers website. Hopefully after the two updates, there will no longer be any BSOD. I will continue to run verifier until the next BSOD. If you do not hear from me again, I want to say Thank You.

**Pauly** · 08 Jan 2010

No problem we are here to help
Hope all is ok for you now any probs post back and we`ll do are best to get them sorted for you

lsuk · 08 Jan 2010

Oh well, got the mega BSOD a few minutes ago. It was so bad that my computer didn't start again. Please find enclosed the minidump. Last thing i saw was a win32k.sys. Hope it aint that bad. Thanks for all your help. Much appreciated.

lsuk · 08 Jan 2010

Oh another thing, I didn't know what to do after the BSOD and my verifier. I was told to delete my settings, but I haven't yet. Since I go the BSOD, what do I do now? Do I just delete my settings? Is there some log I should provide? Please advise. Thanks.

Tepid · 08 Jan 2010

I recommend 2 things.

A. Take ti back for warranty work, let them figure it out, it's what you have the warranty for. (i wouldn't, but I'm a tech.)

B. Run the Diags discussed above. If RAM or Hard Driver are bad, it doesn't matter what else you try to do, checking all the dumps in the world ain't going to fix it.

I generally say, let the Memtest run 4 to 6 hours with 4G. I would say for you to let it run 6 hours minimum to 8 to 9 hours max. It does generally (not always) work out to about 1 hour per gig these days.

The reason is the way the Memtests work. I don't fully understand it myself, but just know, it's not testing every bit of ram in a single pass. If you get errors right away, you can be pretty sure you have bad ram. But, there are false positives and false negatives.

So, I generally run both Memtest86+ and Windows Memory Diags to double check against each other. I have found that Windows Memory Diags give far less false positives/negatives than Memtest86+ does.

Which leads me to "

- Windows Memory Diagnostic NO LONGER RECOMMENDED"

I would like to see an explanation why.. as I think this is unfounded.