[LØST]Bluescreen i Vista 32-bit, var ram brikkene

[larsi111]

Hei.

 

Jeg sliter med bluescreen hele tiden på min data.

Det spiller ingen rolle om jeg sitter på internett, eller spiller.

 

Får bluescreen sånn ca 10 ganger på en dag

 

Jeg har:

Asus P5N-D

Intel Core 2 Duo E6750 2,67 GHz

XFX Geforce 8800 GTS 650M 512 mb

Coirsair 5300 DDr2 4 gb

Coirair 650w

Western Digital 500 gb

 

Jeg formaterte den for 1 uke siden, i håp om at det skulle gi seg, men det gjorde det ikke

Har innstallert det jeg kommer over av oppdateringer/drivere(Noe sted der jeg ser hvem drivere jeg har lagt inn?)

 

Mvh

Larsi111

Endret 14. april 2009 av larsi111

[Tosha0007]

For det første hadde det vore veldig fint om du skreiv kva feilmeldinga i blåskjermen var. Dette gjer det lettare og finne feilen. Denne guiden kan kanskje vera til hjelp! Vanleg feil kan vera minnebrikkene, varme osb. Har du hatt problemet lenge, eller er det komen heilt nyleg? Satt inn/fjerna maskinvare kanskje?

 

Moderator kan godt flytte tråden der den høyre heime.

[larsi111]

For det første hadde det vore veldig fint om du skreiv kva feilmeldinga i blåskjermen var. Dette gjer det lettare og finne feilen. Denne guiden kan kanskje vera til hjelp! Vanleg feil kan vera minnebrikkene, varme osb. Har du hatt problemet lenge, eller er det komen heilt nyleg? Satt inn/fjerna maskinvare kanskje?

 

Moderator kan godt flytte tråden der den høyre heime.

Den kommer og står i 3 sek, så forsvinner feilmeldinga, men kan ta et bilde av den neste gang.

Har hatt feilen siden november. Det startet med bluescreen en gang i Uka.

 

Har ikke rørt datan innen for kabinettet siden den ble kjøpt(Mai 08)

 

Men hører ikke denne i Windows- Vista?

[Tosha0007]

Men har ein eiga kategori på forumet som heiter maskinen fungerer ikkje. Dersom du ser i guiden meiner eg det står korleis du slår av "auto-restart" etter blåskjerm, iallfall korleis ein får opp feilmelding ved hjelp av Windbg om kva feilen var. Les den er nok det beste tipset eg har no

[larsi111]

Men har ein eiga kategori på forumet som heiter maskinen fungerer ikkje. Dersom du ser i guiden meiner eg det står korleis du slår av "auto-restart" etter blåskjerm, iallfall korleis ein får opp feilmelding ved hjelp av Windbg om kva feilen var. Les den er nok det beste tipset eg har no

Tok den av nå. så får litt lengre tid å lese nå

[larsi111]

Fikk bluescreen nå.

 

dette sto;

"A problem has been detected and Windows has been shut down to prevent damage

to your computer.

 

PFM_LIST_CORRUPT

 

If this is the first time you`ve seen this Stop error screen,

restart your computer. If this screen appears again, follow

these steps:

 

Check to make sure any new hardware or software is properly installed.

If this is a new installation, ask your hardware or software manufacturer

for any Windows updates you might need.

 

If problems continue, disable or remove any newly installed hardware

or software. Disable BIOS memory options such as caching or shadowing.

If you need to use safe Mode to remove or disable components, restart

your computer, press F8 to select Advanced Startup Options, and then

select Safe Mode

 

Technical information:

 

*** STOP: 0x000004E (0x0000008D, 0x0007FF57, 0x0656001, 0XC0007DB8)

 

 

 

Collecting data for crash dump . . .

Initializing disk for crash dump . . .

Beginning dump for physical memory.

Dumping physical memory to disk: 100

Physical memory dump complete

Contact your system admin or technical support for further assistance"

 

Larsi111

[larsi111]

Noen som vet?

 

Tror jeg innstalerer xp/windows 7.

Og ser om det hjelper

[TCi]

Har du feilsøkt slik som det ble tipset om tidligere. Det kan være minnet eller annen maskinvare som da ikke vil bli løst av å installere Windows på nytt.

[larsi111]

Fikk dette i WindBg

 

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: fffbffd4, memory referenced.

Arg2: 00000001, value 0 = read operation, 1 = write operation.

Arg3: bf87a534, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 00000000, (reserved)

 

Debugging Details:

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

 

 

Could not read faulting driver name

 

WRITE_ADDRESS: fffbffd4

 

FAULTING_IP:

win32k!DoNewMouseAccel+ab

bf87a534 8969d4 mov dword ptr [ecx-2Ch],ebp

 

MM_INTERNAL_CODE: 0

 

CUSTOMER_CRASH_COUNT: 4

 

DEFAULT_BUCKET_ID: CODE_CORRUPTION

 

BUGCHECK_STR: 0x50

 

PROCESS_NAME: csrss.exe

 

MISALIGNED_IP:

win32k!DoNewMouseAccel+ab

bf87a534 8969d4 mov dword ptr [ecx-2Ch],ebp

 

LAST_CONTROL_TRANSFER: from bf87a86b to bf87a534

 

STACK_TEXT:

b105f924 bf87a86b b105f94c b105f950 00000000 win32k!DoNewMouseAccel+0xab

b105f944 bf87ab0d fffffffc fffffffe 00000000 win32k!GetMouseCoord+0x178

b105f97c bf879a8d 004f9faa 89a29da8 b105f9d4 win32k!ProcessMouseInput+0x13c

b105f98c 804ff8c4 e1f58618 e1f58640 00000000 win32k!InputApc+0x4e

b105f9d4 80503864 00000000 00000000 00000000 nt!KiDeliverApc+0x124

b105f9ec 804fad98 804fab14 e1783eb0 00000000 nt!KiSwapThread+0xa8

b105fa24 bf807a6c 00000003 89a1fe78 00000001 nt!KeWaitForMultipleObjects+0x284

b105fa5c bf88fbf6 00000002 89a1fe78 bf892b44 win32k!xxxMsgWaitForMultipleObjects+0xb0

b105fd30 bf878ba3 bf9ab100 00000001 b105fd54 win32k!xxxDesktopThread+0x339

b105fd40 bf80108a bf9ab100 b105fd64 007afff4 win32k!xxxCreateSystemThreads+0x6a

b105fd54 8054162c 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23

b105fd54 7c90e4f4 00000000 00000022 00000000 nt!KiFastCallEntry+0xfc

WARNING: Frame IP not in any known module. Following frames may be wrong.

00000000 00000000 00000000 00000000 00000000 0x7c90e4f4

 

 

STACK_COMMAND: kb

 

CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k

15 errors : !win32k (bf87a505-bf87a6e5)

bf87a500 f3 f7 de e9 ee *74 ff ff 8b 4d ec 8b 45 f0 f7 d9 .....t...M..E...

bf87a510 83 d0 00 f7 d8 *63 3b fe ff ff 39 5d e8 7f 06 7c .....c;...9]...|

bf87a520 0f 3b cb 72 0b *79 75 e8 89 4d d4 e9 c6 fd ff ff .;.r.yu..M......

bf87a530 8b f1 f7 de 89 *69 d4 8b 75 e8 eb c3 83 7d e8 00 .....i..u....}..

bf87a540 7f 06 7c 0c 85 *69 72 08 8b 45 e8 e9 05 fe ff ff ..|..ir..E......

bf87a550 8b 45 e8 eb b9 *30 c9 7f 48 7c 04 85 db 73 42 8b .E...0..H|...sB.

bf87a560 fb f7 df 8b f1 *5f d6 00 f7 de 8b 45 0c 8b 00 c1 ....._.....E....

bf87a570 e0 10 99 79 07 *53 d8 83 d2 00 f7 da 3b f2 0f 8f ...y.S......;...

...

bf87a680 1e fc ff 8b 0d *08 b0 9a bf 8b f0 8b 41 38 0f b7 ............A8..

bf87a690 50 0a 0f b7 40 *00 f7 de 1b f6 23 d0 b8 ff fd ff P...@.....#.....

bf87a6a0 ff f7 de 85 d0 *00 10 8b 51 38 0f b7 52 04 23 d0 ........Q8..R.#.

bf87a6b0 52 51 e8 f7 6f *80 ff e8 4a 64 f8 ff 85 f6 74 34 RQ..o...Jd....t4

bf87a6c0 e9 bf 00 00 00 *00 90 90 90 90 8b ff 55 8b ec 83 ............U...

bf87a6d0 ec 18 a1 64 ba *61 bf 8b 48 40 8b 49 0c 0b 88 98 [email protected]....

bf87a6e0 00 00 00 53 84 *46 8b 5d 08 56 57 8b 7d 0c 0f 88 ...S.F.].VW.}...

 

MODULE_NAME: memory_corruption

 

IMAGE_NAME: memory_corruption

 

FOLLOWUP_NAME: memory_corruption

 

DEBUG_FLR_IMAGE_TIMESTAMP: 0

 

MEMORY_CORRUPTOR: STRIDE

 

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

 

BUCKET_ID: MEMORY_CORRUPTION_STRIDE

 

Followup: memory_corruption

 

 

 

 

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: 8c0ebc10, memory referenced

Arg2: 00000002, IRQL

Arg3: 00000001, value 0 = read operation, 1 = write operation

Arg4: b9c32145, address which referenced memory

 

Debugging Details:

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

 

 

WRITE_ADDRESS: 8c0ebc10

 

CURRENT_IRQL: 2

 

FAULTING_IP:

ipnat!NatLookupRedirect+13

b9c32145 008d048520d4 add byte ptr [ebp-2BDF7AFCh],cl

 

CUSTOMER_CRASH_COUNT: 1

 

DEFAULT_BUCKET_ID: CODE_CORRUPTION

 

BUGCHECK_STR: 0xD1

 

PROCESS_NAME: WoW-3.0.1-to-3.

 

LAST_CONTROL_TRANSFER: from b9c3a210 to b9c32145

 

STACK_TEXT:

b7ee370c b9c3a210 00000008 b7ee37e0 00000000 ipnat!NatLookupRedirect+0x13

b7ee37a4 b9c3b5b8 00000000 00000001 b7ee37e0 ipnat!NatpDirectPacket+0xd2

b7ee381c b9c752be b7ee38d0 00000000 b7ee3860 ipnat!NatTranslatePacket+0x45e

b7ee395c b9c8f09a b9cb34d4 88566620 89050020 tcpip!IPTransmit+0x16cf

b7ee39fc b9c8ee61 88f2bb20 88566620 00000103 tcpip!UDPSend+0x41b

b7ee3a20 b9c7f310 00ee3a48 00000000 89050060 tcpip!TdiSendDatagram+0xd5

b7ee3a5c b9c7f332 88bc08f0 88bc09a8 891a35c8 tcpip!UDPSendData+0x61

b7ee3a78 b820941e 891a35c8 88bc08f0 88bc0a80 tcpip!TCPDispatchInternalDeviceControl+0xee

WARNING: Stack unwind information not available. Following frames may be wrong.

b7ee3a94 b8209450 891a35c8 88bc08f0 00000000 avgtdix+0x341e

b7ee3aa8 804eeeb1 891a35c8 88bc08f0 88f94c80 avgtdix+0x3450

b7ee3ab8 b9c127f7 00000000 00000008 b7ee3b1c nt!IopfCallDriver+0x31

b7ee3b10 b9c09bce 88f94c80 029efe1c b9c09bce afd!AfdFastDatagramSend+0x2fd

b7ee3c5c 8057f17b 890a4358 00000001 029efd94 afd!AfdFastIoDeviceControl+0x2a7

b7ee3d00 8057804e 00000224 000011f0 00000000 nt!IopXxxControlFile+0x255

b7ee3d34 8054060c 00000224 000011f0 00000000 nt!NtDeviceIoControlFile+0x2a

b7ee3d34 7c90eb94 00000224 000011f0 00000000 nt!KiFastCallEntry+0xfc

029efde4 00000000 00000000 00000000 00000000 0x7c90eb94

 

 

STACK_COMMAND: kb

 

CHKIMG_EXTENSION: !chkimg -lo 50 -db !ipnat

19 errors : !ipnat (b9c32105-b9c32225)

b9c32100 e8 ab 1b 00 00 *00 68 2c d4 c3 b9 e8 a0 1b 00 00 ......h,........

b9c32110 56 68 38 d4 c3 *00 e8 95 1b 00 00 68 00 01 00 00 Vh8........h....

b9c32120 68 00 d4 c3 b9 *00 86 1b 00 00 5e c3 cc cc cc cc h.........^.....

b9c32130 cc cc 8b ff 55 *00 ec 51 51 53 8b 5d 08 56 8b 75 ....U..QQS.].V.u

b9c32140 0c 57 8d 04 5b *00 8d 04 85 20 d4 c3 b9 50 e8 85 .W..[.... ...P..

b9c32150 1b 00 00 8b 4e *00 89 4d fc e9 aa 00 00 00 8b 45 ....N..M.......E

b9c32160 0c 8b 40 04 83 *00 08 8b 38 3b f8 89 45 f8 0f 84 [email protected];..E...

b9c32170 8e 00 00 00 8b *00 49 f7 d9 1b c9 f7 d1 23 cb c1 ......I......#..

b9c32180 e1 03 8b 55 1c *00 c7 2b c1 83 3a 00 74 06 f6 40 ...U...+..:.t..@

b9c32190 49 10 74 64 8b *00 48 84 d2 79 06 f6 45 18 04 74 I.td..H..y..E..t

b9c321a0 57 f6 c6 01 75 *00 f6 45 18 08 75 4c 8b f2 81 e6 W...u..E..uL....

b9c321b0 00 02 00 00 74 *00 f6 45 18 04 75 3c f6 c2 10 74 ....t..E..u<...t

b9c321c0 08 8b 5d fc 3b *00 4c 75 2f f6 c6 04 74 45 85 f6 ..].;.Lu/...tE..

b9c321d0 8b 75 1c 74 10 *00 7e 08 00 74 05 f6 c6 10 74 18 .u.t..~..t....t.

b9c321e0 8b 55 14 eb 0e *00 7e 04 00 74 05 f6 c6 10 74 08 .U....~..t....t.

b9c321f0 8b 55 10 39 50 *00 74 1b 8b 3f 3b 7d f8 75 83 8b .U.9P.t..?;}.u..

b9c32200 5d 08 8b 45 0c *00 40 08 85 c0 89 45 0c 0f 85 4b ][email protected]

b9c32210 ff ff ff 5f 5e *00 c9 c2 18 00 cc cc cc cc cc cc ..._^...........

b9c32220 8b ff 55 8b ec *00 8b 5d 08 8b 43 48 a9 00 00 00 ..U....]..CH....

 

MODULE_NAME: memory_corruption

 

IMAGE_NAME: memory_corruption

 

FOLLOWUP_NAME: memory_corruption

 

DEBUG_FLR_IMAGE_TIMESTAMP: 0

 

MEMORY_CORRUPTOR: STRIDE

 

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

 

BUCKET_ID: MEMORY_CORRUPTION_STRIDE

 

Followup: memory_corruption

 

 

 

PFN_LIST_CORRUPT (4e)

Typically caused by drivers passing bad memory descriptor lists (ie: calling

MmUnlockPages twice with the same list, etc). If a kernel debugger is

available get the stack trace.

Arguments:

Arg1: 00000099, A PTE or PFN is corrupt

Arg2: 0006847d, page frame number

Arg3: 00000003, current page state

Arg4: 00000000, 0

 

Debugging Details:

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

 

 

BUGCHECK_STR: 0x4E_99

 

CUSTOMER_CRASH_COUNT: 2

 

DEFAULT_BUCKET_ID: DRIVER_FAULT

 

PROCESS_NAME: Repair.exe

 

LAST_CONTROL_TRANSFER: from 80523de9 to 804f9f43

 

STACK_TEXT:

b5784b84 80523de9 0000004e 00000099 0006847d nt!KeBugCheckEx+0x1b

b5784bc8 80523fb8 c0013808 02701000 00000000 nt!MiDeletePte+0x447

b5784c90 8051a628 00001688 0293cfff 00000000 nt!MiDeleteVirtualAddresses+0x164

b5784cac 805b33ac 02430000 0293cfff b5784d64 nt!MiDeleteFreeVm+0x20

b5784d4c 8054162c ffffffff 01a4f2e4 01a4f2fc nt!NtFreeVirtualMemory+0x42e

b5784d4c 7c90e4f4 ffffffff 01a4f2e4 01a4f2fc nt!KiFastCallEntry+0xfc

WARNING: Frame IP not in any known module. Following frames may be wrong.

01a4f244 00000000 00000000 00000000 00000000 0x7c90e4f4

 

 

STACK_COMMAND: kb

 

FOLLOWUP_IP:

nt!MiDeletePte+447

80523de9 8b5008 mov edx,dword ptr [eax+8]

 

SYMBOL_STACK_INDEX: 1

 

SYMBOL_NAME: nt!MiDeletePte+447

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: nt

 

DEBUG_FLR_IMAGE_TIMESTAMP: 48a3fbd9

 

IMAGE_NAME: memory_corruption

 

FAILURE_BUCKET_ID: 0x4E_99_nt!MiDeletePte+447

 

BUCKET_ID: 0x4E_99_nt!MiDeletePte+447

 

Followup: MachineOwner

 

 

 

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: 00005a60, memory referenced

Arg2: 00000002, IRQL

Arg3: 00000000, value 0 = read operation, 1 = write operation

Arg4: b62fd507, address which referenced memory

 

Debugging Details:

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

 

 

READ_ADDRESS: 00005a60

 

CURRENT_IRQL: 2

 

FAULTING_IP:

USBPORT!USBPORT_FindUrbInIrpTable+77

b62fd507 8b7760 mov esi,dword ptr [edi+60h]

 

CUSTOMER_CRASH_COUNT: 3

 

DEFAULT_BUCKET_ID: DRIVER_FAULT

 

BUGCHECK_STR: 0xD1

 

PROCESS_NAME: Idle

 

LAST_CONTROL_TRANSFER: from b6303362 to b62fd507

 

STACK_TEXT:

80551070 b6303362 8ac06028 8aa37008 893a51a0 USBPORT!USBPORT_FindUrbInIrpTable+0x77

805510d8 b63043c6 02b03d00 ffffffff 80546acc USBPORT!USBPORT_FlushPendingList+0x43a

80551108 b630b350 8aca1138 80551140 b630af14 USBPORT!USBPORT_QueueTransferUrb+0x248

80551114 b630af14 8ac06028 8ac90e70 893a51a0 USBPORT!USBPORT_AsyncTransfer+0x30

80551140 b6310088 89d90030 8ac06028 00000090 USBPORT!USBPORT_ProcessURB+0x3f4

80551160 b62f93d2 89d90030 8ac90e70 8ac90e70 USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x7e

80551184 804ef19f 8ac90f28 89d90188 893a51a0 USBPORT!USBPORT_Dispatch+0x148

80551194 b3aa259c 805511bc b3aa682d 8ac90e70 nt!IopfCallDriver+0x31

8055119c b3aa682d 8ac90e70 89d90030 8ac90e70 usbhub!USBH_PassIrp+0x18

805511bc b3aa70ae 8ad960e8 8ac90e70 89d7c148 usbhub!USBH_PdoUrbFilter+0xbd

805511d8 b3aa45e4 893a51a0 8ac90e70 8055121c usbhub!USBH_PdoDispatch+0x202

805511e8 804ef19f 89a70330 8ac90e70 893a51a0 usbhub!USBH_HubDispatch+0x48

805511f8 b054af8f 8ac90e70 89db2800 8ad6f008 nt!IopfCallDriver+0x31

8055121c b054a5bd 89d7c148 8ae12578 8055123b hidusb!HumReadReport+0xef

8055123c ba278e8d 89d7c148 8ac90e70 8ac90e70 hidusb!HumInternalIoctl+0x6b

80551250 ba27a284 89d7c148 8ac90e70 8ac90e70 HIDCLASS!HidpCallDriver+0x3f

8055126c ba27a0ec 89d7c214 8ad6f008 805512b7 HIDCLASS!HidpSubmitInterruptRead+0x84

805512a4 804f16c0 00000000 8ac90e70 00d7c214 HIDCLASS!HidpInterruptReadComplete+0x1d2

805512d4 b63010d5 8ac90e70 89609590 8ac06028 nt!IopfCompleteRequest+0xa2

8055133c b6301d47 893a51a0 00000000 8ac067d8 USBPORT!USBPORT_CompleteTransfer+0x373

8055136c b6302944 026e6f44 8ac060e0 8ac060e0 USBPORT!USBPORT_DoneTransfer+0x137

805513a4 b630413a 8ac06028 80546acc 8ac06230 USBPORT!USBPORT_FlushDoneTransferList+0x16c

805513d0 b631224b 8ac06028 80546acc 8ac06028 USBPORT!USBPORT_DpcWorker+0x224

8055140c b63123c2 8ac06028 00000001 8055c0c0 USBPORT!USBPORT_IsrDpcWorker+0x38f

80551428 80545e7f 8ac0664c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166

80551440 8055be60 ffdffc50 00000000 8055be60 nt!KiRetireDpcList+0x61

80551450 80545d64 00000000 0000000e 00000000 nt!KiIdleThread0

80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28

 

 

STACK_COMMAND: kb

 

FOLLOWUP_IP:

hidusb!HumReadReport+ef

b054af8f 8b4d10 mov ecx,dword ptr [ebp+10h]

 

SYMBOL_STACK_INDEX: d

 

SYMBOL_NAME: hidusb!HumReadReport+ef

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: hidusb

 

IMAGE_NAME: hidusb.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP: 480254c7

 

FAILURE_BUCKET_ID: 0xD1_hidusb!HumReadReport+ef

 

BUCKET_ID: 0xD1_hidusb!HumReadReport+ef

 

Followup: MachineOwner

 

 

Endret 22. januar 2009 av larsi111