Can anyone read BSOD technical info??

IsThisIt???

Hey all,
New laptop, new problem,
Get the blue screen of death a bit sporadically and i'm not sure why. Anyway the technical information that comes up is:

STOP: 0x0000000A (0x0000000000000018, 0x000000000000000B, 0x0000000000000001, 0xFFFFF80002A78543)

Don't know if anyone on here knows what this means but if they do that'd be great

Spacedog

no detail here really, it's not something you ban decode into a message like 'try taking the battery out and turning it off and on again'

it is simply telling you the memory location that it failed to read the next instruction.

you can try using this tool to test your memory...

http://www.memtest86.com/

Allyall

Hi,

The common reason for that error code followed by IRQL_NOT_LESS_OR_EQUAL is a driver problem.

http://msdn.microsoft.com/en-us/library/ff560129%28v=VS.85%29.aspx

Gadgetman496

This might help you get more information?

It can read and display Blue Screen error logs.

Blue Screen View

-

seithon

It is possible to decode a blue screen of death, however you would need the entire screen and the .dmp file created and a few other things.
That said these days BSOD's are usually caused by either massive driver problems, a broken windows install or hardware borked.

So generally speaking just follow the troubleshooting steps people outline for those three things.

jimmycrackcorm

Just format and forget. If you ain't backing up then tough.

MASTER...of the bra

gadgetman496 wrote: »

This might help you get more information?

It can read and display Blue Screen error logs.

Blue Screen View

-

yup, give this a go.

Feelgood

Easiest way to resolve BSOD is install Linux and fcuk windows out the window!.

MASTER...of the bra

Feelgood wrote: »

Easiest way to resolve BSOD is install Linux and fcuk windows out the window!.

Bill needs money for charity.:rolleyes:

Esel

jimmycrackcorm wrote: »

Just format and forget. If you ain't backing up then tough.

Your 'advice' is more than a bit radical, no?

practice

A nice little program here it might help

www.resplendence.com/whocrashed

"If your computer unexpectedly reset or shut down, it is suggested that you run WhoCrashed. WhoCrashed will tell you if crash dumps are enabled on your computer, if not it offer you suggestions on how to enable them"

Cuddlesworth

practice wrote: »

A nice little program here it might help

www.resplendence.com/whocrashed

"If your computer unexpectedly reset or shut down, it is suggested that you run WhoCrashed. WhoCrashed will tell you if crash dumps are enabled on your computer, if not it offer you suggestions on how to enable them"

They will take your money and tell you nothing more then Bluescreen view and a quick google will. Another internet rip off merchant masquerading as a helpful tool.

Gadgetman496

Cuddlesworth wrote: »

They will take your money and tell you nothing more then Bluescreen view and a quick google will. Another internet rip off merchant masquerading as a helpful tool.

It is available free for personal use when you go to actually down it the choice of free or Pro is there. It really uses Microsoft's WinDbg SDK tools anyway I think?

I suppose for free it's no harm to have it in the toolbox?

-

practice

Cuddlesworth wrote: »

They will take your money and tell you nothing more then Bluescreen view and a quick google will. Another internet rip off merchant masquerading as a helpful tool.

Did not take any money from me. were you fool enough to pay

"WhoCrashed shows the drivers which have been crashing your computer with a single click. In most cases it can pinpoint the offending drivers which have been causing misery on your computer system in the past. It does post-mortem crashdump analysis and presents all gathered information in a comprehensible way."

tmcw

OP, curious as to what OS you're using?

I honestly can't recall having a BSOD after maybe 6 years of using XP Pro (refreshed once a year at the most).

IsThisIt???

Its Windows 7, bought it a few weeks ago and its happened pretty much since the start.

Haven't had a chance to try any of these yet but will do tomorrow. Thanks for everyones help!

seithon

If it's doing it since day one, try a factory reset using the supplied recovery disks or whatever method the manufacturer included.
If it's still doing it after that take it back for replacement.

Dublin_Gunner

seithon wrote: »

If it's doing it since day one, try a factory reset using the supplied recovery disks or whatever method the manufacturer included.
If it's still doing it after that take it back for replacement.

Just take it back now and have them fix it / replace it.