Laptop wylacza sie bez powodu w roznych momentach. Przy wlaczonym prime95 chodzil 3 dni bez problemu. Za to w roznych sytuacjach, np wlaczenie firefoxa, zgranie zdjec z aparatu, czyli totalnie różne niepołączone sytuacje raz czasem się po prostu wyłącza. Nie ma bsodu ani błędu ani restartu. Po prostu klaps.
Dziś po miesiącu od zainstalowania win7(z visty) dostałem pierwszy BSOD, podejrzewam, że nie ma nic wspólnego z wyłączeniami, no ale może choć da jakiś trop(ucieszyłbym się).
Załączam błedy z podglądu zdarzeń i minidumpa(jedyny).
Jakby co to pasta jest wymieniona i jedyne co wydaje mi się być słuszne to albo gdzieś się robi spięcie albo płyta głóna jest uszkodzona. No bo w sumie to podgląd zdarzeń informuje jedynie o tym, że nastąpiło nieoczekiwane zamknięcie systemu bez przyczyny.
Dziś po miesiącu od zainstalowania win7(z visty) dostałem pierwszy BSOD, podejrzewam, że nie ma nic wspólnego z wyłączeniami, no ale może choć da jakiś trop(ucieszyłbym się).
Załączam błedy z podglądu zdarzeń i minidumpa(jedyny).
Jakby co to pasta jest wymieniona i jedyne co wydaje mi się być słuszne to albo gdzieś się robi spięcie albo płyta głóna jest uszkodzona. No bo w sumie to podgląd zdarzeń informuje jedynie o tym, że nastąpiło nieoczekiwane zamknięcie systemu bez przyczyny.
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\admin\Desktop\022812-17440-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbole*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16905.x86fre.win7_gdr.111025-1503
Machine Name:
Kernel base = 0x82a4c000 PsLoadedModuleList = 0x82b94810
Debug session time: Mon Feb 27 23:32:47.146 2012 (UTC - 8:00)
System Uptime: 0 days 0:01:41.440
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {19, a, 0, 8634c920}
Probably caused by : ntkrpamp.exe ( nt!SwapSplayLinks+f6 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000019, memory referenced
Arg2: 0000000a, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8634c920, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82bb4718
Unable to read MiSystemVaType memory at 82b94160
00000019
CURRENT_IRQL: a
FAULTING_IP:
+1a
8634c920 0300 add eax,dword ptr [eax]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 82ad61b9 to 8634c920
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
807e1c78 82ad61b9 87d95c80 badb0d00 00000019 0x8634c920
807e1cb4 82ab415a badb0d00 00000000 00000000 nt!SwapSplayLinks+0xf6
807e1cb8 badb0d00 00000000 00000000 864196b4 nt!KiIdleLoop+0x1a
807e1cbc 00000000 00000000 864196b4 00000001 0xbadb0d00
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!SwapSplayLinks+f6
82ad61b9 85c0 test eax,eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!SwapSplayLinks+f6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ea76ed3
FAILURE_BUCKET_ID: 0xD1_nt!SwapSplayLinks+f6
BUCKET_ID: 0xD1_nt!SwapSplayLinks+f6
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000019, memory referenced
Arg2: 0000000a, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8634c920, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82bb4718
Unable to read MiSystemVaType memory at 82b94160
00000019
CURRENT_IRQL: a
FAULTING_IP:
+1a
8634c920 0300 add eax,dword ptr [eax]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 82ad61b9 to 8634c920
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
807e1c78 82ad61b9 87d95c80 badb0d00 00000019 0x8634c920
807e1cb4 82ab415a badb0d00 00000000 00000000 nt!SwapSplayLinks+0xf6
807e1cb8 badb0d00 00000000 00000000 864196b4 nt!KiIdleLoop+0x1a
807e1cbc 00000000 00000000 864196b4 00000001 0xbadb0d00
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!SwapSplayLinks+f6
82ad61b9 85c0 test eax,eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!SwapSplayLinks+f6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ea76ed3
FAILURE_BUCKET_ID: 0xD1_nt!SwapSplayLinks+f6
BUCKET_ID: 0xD1_nt!SwapSplayLinks+f6
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000019, memory referenced
Arg2: 0000000a, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8634c920, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82bb4718
Unable to read MiSystemVaType memory at 82b94160
00000019
CURRENT_IRQL: a
FAULTING_IP:
+1a
8634c920 0300 add eax,dword ptr [eax]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 82ad61b9 to 8634c920
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
807e1c78 82ad61b9 87d95c80 badb0d00 00000019 0x8634c920
807e1cb4 82ab415a badb0d00 00000000 00000000 nt!SwapSplayLinks+0xf6
807e1cb8 badb0d00 00000000 00000000 864196b4 nt!KiIdleLoop+0x1a
807e1cbc 00000000 00000000 864196b4 00000001 0xbadb0d00
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!SwapSplayLinks+f6
82ad61b9 85c0 test eax,eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!SwapSplayLinks+f6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ea76ed3
FAILURE_BUCKET_ID: 0xD1_nt!SwapSplayLinks+f6
BUCKET_ID: 0xD1_nt!SwapSplayLinks+f6
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000019, memory referenced
Arg2: 0000000a, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8634c920, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82bb4718
Unable to read MiSystemVaType memory at 82b94160
00000019
CURRENT_IRQL: a
FAULTING_IP:
+1a
8634c920 0300 add eax,dword ptr [eax]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 82ad61b9 to 8634c920
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
807e1c78 82ad61b9 87d95c80 badb0d00 00000019 0x8634c920
807e1cb4 82ab415a badb0d00 00000000 00000000 nt!SwapSplayLinks+0xf6
807e1cb8 badb0d00 00000000 00000000 864196b4 nt!KiIdleLoop+0x1a
807e1cbc 00000000 00000000 864196b4 00000001 0xbadb0d00
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!SwapSplayLinks+f6
82ad61b9 85c0 test eax,eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!SwapSplayLinks+f6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ea76ed3
FAILURE_BUCKET_ID: 0xD1_nt!SwapSplayLinks+f6
BUCKET_ID: 0xD1_nt!SwapSplayLinks+f6
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000019, memory referenced
Arg2: 0000000a, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8634c920, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82bb4718
Unable to read MiSystemVaType memory at 82b94160
00000019
CURRENT_IRQL: a
FAULTING_IP:
+1a
8634c920 0300 add eax,dword ptr [eax]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 82ad61b9 to 8634c920
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
807e1c78 82ad61b9 87d95c80 badb0d00 00000019 0x8634c920
807e1cb4 82ab415a badb0d00 00000000 00000000 nt!SwapSplayLinks+0xf6
807e1cb8 badb0d00 00000000 00000000 864196b4 nt!KiIdleLoop+0x1a
807e1cbc 00000000 00000000 864196b4 00000001 0xbadb0d00
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!SwapSplayLinks+f6
82ad61b9 85c0 test eax,eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!SwapSplayLinks+f6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ea76ed3
FAILURE_BUCKET_ID: 0xD1_nt!SwapSplayLinks+f6
BUCKET_ID: 0xD1_nt!SwapSplayLinks+f6
Followup: MachineOwner
---------
