Before you guys go telling him to disembowel his laptop, Jesus... You can't just throw suggestions around about registry cleaners and to completely open up his laptop for all we DON'T know yet could be a simple driver / software issue. You have to at least know what the probable cause is, and then follow through from that point. Telling him to run Driver Sweeper when you don't even know if AMD/ATI drivers are a probable fault cause is pointless, and can only lead to FURTHER issues.
In the simple dump descrip. he posted above, it lists netw5s64.sys as the probable cause, that's the Intel 5100 wifi driver. It can either be a direct cause and the driver itself can be updated here
, or that's NOT the direct cause, and something else (most likely software / driver related) caused the wifi driver itself to crash.
I'm not trying to be high & mighty, and I know you're all just doing your best to help, but seriously.. think about it. Just going to cause confusion.
OP, how many passes did you run Memtest for? It's best to let it run for 6-7 passes (several hours) to ensure your RAM is working 100% as intended. Also, you mentioned your laptop shut down during the test. That is not supposed to happen, so that is why I am also saying to let it run longer (6-7 passes).
Regardless, if Memtest shows no errors and all is well after at least 6-7 passes, I'd like you to enable Driver Verifier
. Drivier Verifier will force a BSOD if it finds a driver at fault and hopefully give us more info as to what is causing your BSODs.
Also, can you please zip up and attach your latest dump file(s) to your next post?
Originally Posted by wirefox
irql usually has to do with gpu drivers no? maybe reinstall your gpu.... and do a driver sweeper before you do
Not exactly, IRQL bugcheck is usually related to a bug in a driver / software, memory issues or page file corruption (being the least common).Edited by pjBSOD - 2/25/12 at 6:08pm