BSoD On G53SX

Hello guys I just got my 1st BSoD on this laptop, installed BlueScreenView and had these on the file. please help.
I know its the ntoskrnl, but can you guys provide a more clear or step-by-step idea what to do?

==================================================
Dump File : 061612-16177-01.dmp
Crash Time : 6/16/2012 6:17:10 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`035bc9bc
Parameter 3 : fffff880`02ddcec0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061612-16177-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 285,256
==================================================

It happened only last night, after one BSoD, it never happened again, so far.

 

Download bluescreenview: Blue screen of death (STOP error) information in dump files.

That will let you know what caused the crash.

 

already did, i copied the notepad file on my 1st post.

 

If it's the same address every time,
"Crash Address : ntoskrnl.exe+7f1c0"
..it's still very likely a hardware problem. Typically a bad memory stick.

 

https://www.google.ca/search?q=Crash+Address+%3A+ntoskrnl.exe%2B7f1c0&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-USfficial&client=firefox-a#hl=en&safe=off&client=firefox-a&hs=lkn&rls=org.mozilla:en-US%3Aofficial&sclient=psy-ab&q=Crash+Address+%3A+ntoskrnl.exe%2B7f1c0&oq=Crash+Address+:+ntoskrnl.exe%2B7f1c0&aq=f&aqi=&aql=&gs_l=serp.12...0.0.0.63615.0.0.0.0.0.0.0.0..0.0...0.0.YshcYHu2rx0&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.,cf.osb&fp=6c1b33bf8ec2cb87&biw=1280&bih=926

Others with the same crash address, may be bad memory.

Run Memtest86 on your machine overnight.

 

Fortunately, it hasn't happened again since.

 

That's actually not good news either -- since it means the problem must have been caused programmatically.

You didn't happen to be switching between battery and the power-cable at the time? I had similar problems like that because the power-management software had a tendency to require I had loggen in directly to the admin account. I.e., I would boot to the user-account, it would hang, I would go to the admin account, try to read logs, figure things out. Back to the user-account, couldn't reproduce the problem. Then after a few days, a restart, some new driver, and the problem would be back -- because the admin account hadn't launched the component.

 

It's always plugged in when I am playing games. It was plugged in when it happened.

 

Then it's not that, at least. If it happens again, make sure you look at the event logs and see what sort of service happened right before the hang. And as I was saying, the address is something at the end of a block allocated to a physical memory area. And if it's actually used by something like the sound-card, or something with dma that also allocates memory dynamically, then support would probably be interested in a report.