» »

BSOD

BSOD

Andrej_ID ::

Skos mi crasha mašina in sicer dobivam BSODje.

Ko se je zdej nazadnje sesulo sem pognal DEBUGER in dobil že četrtega krivca;
1. chrome.exe
2. steam.exe
3. tretjič ni bil noben proces ampak nek pool corutprion al neki tazga, nisem si zapomnil
4. sidebar.exe

Tule je še celoten izpis:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\local cache*http://msdl.microsoft.com/downloads/sym...
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c59000 PsLoadedModuleList = 0xfffff800`02e96e50
Debug session time: Sun Oct 17 11:17:38.601 2010 (UTC + 2:00)
System Uptime: 0 days 0:10:10.396
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd8018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff96000cabb1b, 8, fffff96000cabb1b, 2}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40ec0 )

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff96000cabb1b, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff96000cabb1b, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


WRITE_ADDRESS: fffff96000cabb1b

FAULTING_IP:
+3131623361363063
fffff960`00cabb1b ?? ???

MM_INTERNAL_CODE: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: sidebar.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff8800a35f530 -- (.trap 0xfffff8800a35f530)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c251a018 rbx=0000000000000000 rcx=0000000000000001
rdx=fffff900c0000750 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000cabb1b rsp=fffff8800a35f6ce rbp=fffff900c1aa3a80
r8=fffff900c0097f20 r9=0000000000000000 r10=00000000000000ff
r11=fffff8800a35f6a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
fffff960`00cabb1b ?? ???
Resetting default scope

UNALIGNED_STACK_POINTER: fffff8800a35f6ce

LAST_CONTROL_TRANSFER: from fffff80002d488f2 to fffff80002cc9740

STACK_TEXT:
fffff880`0a35f3c8 fffff800`02d488f2 : 00000000`00000050 fffff960`00cabb1b 00000000`00000008 fffff880`0a35f530 : nt!KeBugCheckEx
fffff880`0a35f3d0 fffff800`02cc782e : 00000000`00000008 fffff900`c1dd4b70 fffff900`c1aa3a00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`0a35f530 fffff960`00cabb1b : f900c000`0de0f6d0 f900c000`0750ffff f900c000`0750ffff f900c000`0750ffff : nt!KiPageFault+0x16e
fffff880`0a35f6ce f900c000`0de0f6d0 : f900c000`0750ffff f900c000`0750ffff f900c000`0750ffff f900c009`7f20ffff : 0xfffff960`00cabb1b
fffff880`0a35f6d6 f900c000`0750ffff : f900c000`0750ffff f900c000`0750ffff f900c009`7f20ffff f900c000`0de0ffff : 0xf900c000`0de0f6d0
fffff880`0a35f6de f900c000`0750ffff : f900c000`0750ffff f900c009`7f20ffff f900c000`0de0ffff f900c000`0de0ffff : 0xf900c000`0750ffff
fffff880`0a35f6e6 f900c000`0750ffff : f900c009`7f20ffff f900c000`0de0ffff f900c000`0de0ffff f9600000`0000ffff : 0xf900c000`0750ffff
fffff880`0a35f6ee f900c009`7f20ffff : f900c000`0de0ffff f900c000`0de0ffff f9600000`0000ffff 00000000`0000ffff : 0xf900c000`0750ffff
fffff880`0a35f6f6 f900c000`0de0ffff : f900c000`0de0ffff f9600000`0000ffff 00000000`0000ffff 00820000`00000000 : 0xf900c009`7f20ffff
fffff880`0a35f6fe f900c000`0de0ffff : f9600000`0000ffff 00000000`0000ffff 00820000`00000000 00000000`00000000 : 0xf900c000`0de0ffff
fffff880`0a35f706 f9600000`0000ffff : 00000000`0000ffff 00820000`00000000 00000000`00000000 f900c00b`f0f00000 : 0xf900c000`0de0ffff
fffff880`0a35f70e 00000000`0000ffff : 00820000`00000000 00000000`00000000 f900c00b`f0f00000 f900c000`0750ffff : 0xf9600000`0000ffff
fffff880`0a35f716 00820000`00000000 : 00000000`00000000 f900c00b`f0f00000 f900c000`0750ffff f900c23b`3ce0ffff : 0xffff
fffff880`0a35f71e 00000000`00000000 : f900c00b`f0f00000 f900c000`0750ffff f900c23b`3ce0ffff 00050000`0009ffff : 0x820000`00000000


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+40ec0
fffff800`02d488f2 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+40ec0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

FAILURE_BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+40ec0

BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+40ec0

Followup: MachineOwner

-----------------------------------------------------------------------------

A MI LAHKO KDO POMAGA DO REŠITVE?

BALAST ::

Se mi zdi da je problem strojne narave.
Poizkusi z drugim ramom, napajalnikom...

Andrej_ID ::

Kako naj to naredim?

Mislm nimam kle doma kr police z različnimi napajalniki, a obstaja kšn softwerski test za to? Si lahko sposodim kje zadevo?

Steinkauz ::

A si kej navijal proc?

Andrej_ID ::

Vse je stock.

Andrej_ID ::

Pa sej morm met srečo da pridem v windowse in ne krešne.

Prej se je parkrat resetiral kr zaporedoma na različnih točkah, enkrat celo ko sm hotu v safe mode pa so se nalagali driverji. Se je pokazalo modro sam za sekundo pa avtomstski restart.

Pol recimo pride do BIOS zaslona pa se kr ustavi, sploh ne boota. Je treba ugasnit pa mogoče pol pride naprej, včasih pa zašteka pri tistem logotipu WINDOWS ko se nalaga OS.

misek ::

Andrej_ID je izjavil:

Pol recimo pride do BIOS zaslona pa se kr ustavi, sploh ne boota.
Kot je nekdo napisal verjetno hw problem. Če imaš v računalniku več palčk rama odstrani vse razen ene. Pa menjaj jih. Lahko pa poženeš memtest86+ za preverjanje

ncc2000 ::

clear bios ... če bo kaj bolje

Andrej_ID ::

Zdej sem fleshal BIOS na zadnjo non-BETA verzijo. Bomo videli kako bo.

Iatromantis ::

Obvezno mem test, pomnilnik/napajalnik je ponavadi krivec random sesuvanj.

tomos ::

imam problem namreč, ko vklopim računalnik pride do namizja in se po 15 sekundah na njem pojavi tale moder zaslon

podatki o računalniku:
windows 7 ultimate(64-bitni)
amd 955
4gb ram-a
1tb wd green
gtx 460
750w napajalnik
če poskusim z obnovitvijo sistema mi napiše, da ni obnovitvenih točk, lahko pa pridem v safe mode. v zadnjem času nisem naložil nobenih novih programov ali kaj podobnega in me zanima kaj se da storiti oz. če je to da ponovno inštaliram os edina rešitev?
hvala za vse odgovore

Bolf3nk ::

poglej če kaj pomaga

Hi,

Since it works in Safe Mode, the root cause can be the hardware driver.

Based on the current situation, I would like to suggest you perform a Device Clean Boot to narrow down the cause.

Device Clean Boot
==============
Please unplug all unnecessary devices to test the issue. In this situation, your system will only have the basic hardware devices and it should be more stable.

If it is inconvenient to unplug the devices, we can disable them in Device Manager. Please refer to the following steps:

1. Click "Start", type "DEVMGMT.MSC" in the Search textbox and press Enter. Please click “Allow” if the User Account Control window is prompted.
2. Expand "Sound, video and game controllers".
3. Right click on your Sound Card, select "Properties"
4. Click "Driver" tab, click Disable (Disable the selected device). Click OK.
5. Please use the same method to disable other hardware such as: Modem, network card, CD-R drive. Please note some devices such as video adapter are not available to be disabled.

Then, restart your computer. Does it still crash now?

If the system is stable, we can re-enable the devices one by one to narrow down the root cause.

If the issue still persists, the motherboard or CPU may have problems. If that is the case, I recommend asking the computer vendor to examine it.

For a Windows 7 standpoint, you may reinstall Windows 7 to check if this is a hardware issue need to be examined by the computer vendor.

Regards,


http://social.technet.microsoft.com/For...

http://forums.techguy.org/windows-vista...

Zgodovina sprememb…

  • spremenil: Bolf3nk ()


Vredno ogleda ...

TemaSporočilaOglediZadnje sporočilo
TemaSporočilaOglediZadnje sporočilo
»

Blue Screen (ntoskrnl.exe)

Oddelek: Pomoč in nasveti
252301 (1152) fulgur
»

BSOD problem

Oddelek: Pomoč in nasveti
91179 (837) Oktan
»

Adobe Flash povzroča BSOD !!???

Oddelek: Programska oprema
5663 (588) noraguta
»

X server in Nvidia na FC#

Oddelek: Operacijski sistemi
271479 (1306) HellRaiseR
»

xserver-xree86

Oddelek: Operacijski sistemi
61118 (1030) Skrat

Več podobnih tem