BSOD acer aspire 5740g

Witam niedawno kupiem nowego lapka w/w. w Anglii. I mam z nim problem mianowicie od czasu do czasu pojawiają sie BSOD-y. Na początku myślałem ze to wina sterowników od grafy bo zainstalowałem nowe. Następnie przetestowałem pamiątki Memtestem i wszystko ok. Ale to nie to nadal pojawiały się BSOD-y. Wiec zrobiłem tryb Recovery wszystko wróciło do ustawień fabrycznych i pomyślałem ze ok aż tu nagle reset ale tym razem już bez blue screena tylko się zresetował i tak 2-3 razy i na kilka godzin jest spoko następnie znowu się resetuje. Dodam ze pracuje na zasilaczu nie na baterii.wrzucam szczegóły błędu:
Mam nadzieje ze ktoś pomoże bo nie wiem co mam robić. Nowy laptop i takie jazdy dodam ze Windows 7 HP x64. jak nie znajdę rozwiązania to chyba go wyślę do Anglii żeby Siora go oddala bo dzwoniłem do serwisu pl ale koleś powiedział ze do serwisu jedynie do Czech mogę się udać bądź do Niemiec Śmiech Jeżeli będą potrzebne jakieś inne szczegóły proszę pisać będę się starał na bieżąco odpisywać.Pozdrawiam
Podpis problemu:
Nazwa zdarzenia problemu: Blue Screen
Wersja systemu operacyjnego: 6.1.7600.2.0.0.768.3
Identyfikator ustawień regionalnych: 1045

Dodatkowe informacje o problemie:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8004AC5028
BCP3: 00000000BE000000
BCP4: 0000000000800136
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Pliki pomagające opisać problem:
C:\Windows\Minidump\052510-30217-01.dmp
C:\Users\Mac\AppData\Local\Temp\WER-63554-0.sysdata.xml

Podpis problemu:
Nazwa zdarzenia problemu: BlueScreen
Wersja systemu operacyjnego: 6.1.7600.2.0.0.768.3
Identyfikator ustawień regionalnych: 1045

Dodatkowe informacje o problemie:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8004ACD028
BCP3: 00000000BE000000
BCP4: 000000000080011A
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Pliki pomagające opisać problem:
C:\Windows\Minidump\052510-28953-01.dmp
C:\Users\Mac\AppData\Local\Temp\WER-64241-0.sysdata.xml

witam oto zrzut minidmp z programu WinDBG:

Microsoft ® Windows Debugger Version 6.6.0007.5
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Mac\Desktop\052510-25506-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Vista Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Kernel base = 0xfffff800`02c64000 PsLoadedModuleList = 0xfffff800`02ea1e50
Debug session time: Tue May 25 13:11:02.805 2010 (GMT+2)
System Uptime: 0 days 0:06:13.366
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
................................................................................
............................................................................
Loading User Symbols
Loading unloaded module list
....
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004b36028, be000000, 800136}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+71f00 )

Followup: MachineOwner
---------