Bluescreen

kimrenea · 16. desember 2010

Hei.. helt siden jeg kjøpte pcen min fra Komplett.no har det kommet opp Bluscreen en gang i blandt.. begynner å bli lei av det.. om noen av dere kunne hjolpet meg med å finne ut av hva det er som er feil, så hadde det vært fint.. under er kopi av hvilken melding jeg får etter windows har startet igjen.

Problemsignatur:

Navn på problemhendelse: BlueScreen

OS-versjon: 6.1.7600.2.0.0.256.48

ID for nasjonal innstilling: 1044

Tilleggsinformasjon om problemet:

BCCode: d1

BCP1: 0000000000000068

BCP2: 0000000000000002

BCP3: 0000000000000001

BCP4: FFFFF88004281E60

OS Version: 6_1_7600

Service Pack: 0_0

Product: 256_1

Mechablast · 16. desember 2010

Feilmelding er IRQL_NOT_LESS_OR_EQUAL.

Det har stort sett med dårlige drivere å gjøre, prøv å oppdater alle drivere på maskinen.

Det hadde hjulpet om du poster minidumpfilene, kunne sett om jeg finner ut hva som forårsaker bluescreen.

For mere info om minidump så kan du se her.

https://www.diskusjon.no/index.php?showtopic=919442

kimrenea · 17. desember 2010

Det her er hva som kommer når jeg kjørte analyse

*******************************************************************************

* *

* 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: 0000000000000068, memory referenced

Arg2: 0000000000000002, IRQL

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

Arg4: fffff8800431ce60, address which referenced memory

Debugging Details:

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

WRITE_ADDRESS: 0000000000000068

CURRENT_IRQL: 2

FAULTING_IP:

e1q62x64+18e60

fffff880`0431ce60 f00fc14168 lock xadd dword ptr [rcx+68h],eax

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffff88003c6b7e0 -- (.trap 0xfffff88003c6b7e0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=00000000ffffffff rbx=0000000000000000 rcx=0000000000000000

rdx=fffffa8006998010 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8800431ce60 rsp=fffff88003c6b970 rbp=00000000000000e9

r8=0000000000000001 r9=0000000000000000 r10=0000000000000000

r11=000000000000fffb r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na po nc

e1q62x64+0x18e60:

fffff880`0431ce60 f00fc14168 lock xadd dword ptr [rcx+68h],eax ds:00000000`00000068=????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002c72ca9 to fffff80002c73740

STACK_TEXT:

STACK_COMMAND: kb

FOLLOWUP_IP:

e1q62x64+18e60

fffff880`0431ce60 f00fc14168 lock xadd dword ptr [rcx+68h],eax

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: e1q62x64+18e60

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: e1q62x64

IMAGE_NAME: e1q62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4af31807

FAILURE_BUCKET_ID: X64_0xD1_e1q62x64+18e60

BUCKET_ID: X64_0xD1_e1q62x64+18e60

Followup: MachineOwner

---------

Mechablast · 17. desember 2010

Det er etter hva jeg kan se e1q62x64.sys som lager problemer, e1q62x64.sys er Intel Gigabit ethernet driver.

Så prøv å oppdatere drivere, evt deaktivere kortet og se om den slutter å komme med bluescreen.

Du kan også ta en kikk her.

kimrenea · 18. desember 2010

Vet ikke helt hvor jeg finner disse driverene ?.. men har "intel® 82583v gigabit network connection" Prosessor: " AMD PHENOM II X4 965 processor" Skjermkort: "ATI RADEON HD 5800 Series" =D VELDIG glad om du gidder ?

Phyltre · 18. desember 2010

vel avhenging av hva slags operativ system du bruker og navn påprodusent av hovedkort og modell, samt produsent av skjermkort, så bør du kanskjeta å sjekke de nevnte for oppdatering av drivere ? google.no / google.com og så søker du på navn til de tidligere nevnte tingene.

Mechablast · 18. desember 2010

Det hadde vært greit å ha navn på HW (hardware) ja, vanskelig å hjelpe uten mere info.

Endret 18. desember 2010 av arjato

kimrenea · 17. januar 2011

dette er hva som står på den nyeste BSOD'n :

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Loading Dump File [C:\Users\Kim Alfredsen\Desktop\011711-32885-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

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`02c51000 PsLoadedModuleList = 0xfffff800`02e8ee50

Debug session time: Mon Jan 17 19:46:37.203 2011 (UTC + 1:00)

System Uptime: 0 days 2:41:24.888

Loading Kernel Symbols

...............................................................

................................................................

..........................

Loading User Symbols

Loading unloaded module list

......

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {28, 2, 0, fffff8800159e342}

Probably caused by : NETIO.SYS ( NETIO!RtlCopyMdlToMdlIndirect+32 )

Followup: MachineOwner

---------

3: 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: 0000000000000028, memory referenced

Arg2: 0000000000000002, IRQL

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

Arg4: fffff8800159e342, address which referenced memory

Debugging Details:

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

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef90e0

0000000000000028

CURRENT_IRQL: 2

FAULTING_IP:

NETIO!RtlCopyMdlToMdlIndirect+32

fffff880`0159e342 448b7128 mov r14d,dword ptr [rcx+28h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffff88002717420 -- (.trap 0xfffff88002717420)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=fffffa80063297a0 rbx=0000000000000000 rcx=0000000000000000

rdx=fffff88002717748 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8800159e342 rsp=fffff880027175b0 rbp=fffff88002717700

r8=fffff88002717768 r9=fffff88002717730 r10=fffff8800179e3c0

r11=0000000000000002 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe nc

NETIO!RtlCopyMdlToMdlIndirect+0x32:

fffff880`0159e342 448b7128 mov r14d,dword ptr [rcx+28h] ds:9110:00000000`00000028=????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002cc0ca9 to fffff80002cc1740

STACK_TEXT:

fffff880`027172d8 fffff800`02cc0ca9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffff880`027172e0 fffff800`02cbf920 : 00000000`00000000 fffff880`02717730 fffffa80`048aa898 fffffa80`05556880 : nt!KiBugCheckDispatch+0x69

fffff880`02717420 fffff880`0159e342 : 00000000`00000008 00000000`00000010 00000000`000001b0 fffffa80`03e5e010 : nt!KiPageFault+0x260

fffff880`027175b0 fffff880`01646bb4 : fffff880`02717778 fffff880`02717748 fffff880`02717768 fffff880`02717730 : NETIO!RtlCopyMdlToMdlIndirect+0x32

fffff880`02717650 fffff880`0167df86 : fffff880`02717900 fffffa80`046e9cf0 fffffa80`046e9cf0 fffff880`017170e5 : tcpip!TcpSatisfyReceiveRequests+0x1f4

fffff880`02717930 fffff880`0167ea99 : fffffa80`066c36d0 fffffa80`00000288 00000000`00000003 fffffa80`054eda20 : tcpip!TcpDeliverDataToClient+0x106

fffff880`02717ab0 fffff880`01678298 : fffffa80`05acc030 fffff880`02717e50 fffffa80`0488efe8 fffffa80`06345100 : tcpip!TcpDeliverReceive+0xa9

fffff880`02717bb0 fffff880`01678e95 : fffffa80`063298f0 fffffa80`063298f0 fffffa80`0557c714 00000000`00000000 : tcpip!TcpTcbFastDatagram+0x208

fffff880`02717d70 fffff880`0167d86a : fffffa80`049d5e80 fffffa80`062f7100 fffffa80`04879a01 00000000`00000000 : tcpip!TcpTcbReceive+0x1f5

fffff880`02717f20 fffff880`0167d3b7 : fffffa80`0588f32c fffffa80`049e61d0 00000000`00000000 fffffa80`0488ef00 : tcpip!TcpMatchReceive+0x1fa

fffff880`02718070 fffff880`0167f191 : fffffa80`05569669 00000000`0000d0f0 fffffa80`055f9669 00000000`00000001 : tcpip!TcpPreValidatedReceive+0x177

fffff880`02718120 fffff880`01676e22 : fffffa80`0556a230 fffffa80`056cdbb0 fffffa80`056c0006 00000000`00000000 : tcpip!IpFlcReceivePreValidatedPackets+0x4a1

fffff880`02718280 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xa2

STACK_COMMAND: kb

FOLLOWUP_IP:

NETIO!RtlCopyMdlToMdlIndirect+32

fffff880`0159e342 448b7128 mov r14d,dword ptr [rcx+28h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: NETIO!RtlCopyMdlToMdlIndirect+32

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18a

FAILURE_BUCKET_ID: X64_0xD1_NETIO!RtlCopyMdlToMdlIndirect+32

BUCKET_ID: X64_0xD1_NETIO!RtlCopyMdlToMdlIndirect+32

Followup: MachineOwner

---------

3: kd> lmvm NETIO

start end module name

fffff880`01595000 fffff880`015f5000 NETIO (pdb symbols) c:\symbols\netio.pdb\4ACD68B3A9824AAAB3C53C0077FC611F2\netio.pdb

Loaded symbol image file: NETIO.SYS

Mapped memory image file: c:\symbols\NETIO.SYS\4A5BC18A60000\NETIO.SYS

Image path: \SystemRoot\system32\drivers\NETIO.SYS

Image name: NETIO.SYS

Timestamp: Tue Jul 14 01:21:46 2009 (4A5BC18A)

CheckSum: 0005F36C

ImageSize: 00060000

File version: 6.1.7600.16385

Product version: 6.1.7600.16385

File flags: 0 (Mask 3F)

File OS: 40004 NT Win32

File type: 3.6 Driver

File date: 00000000.00000000

Translations: 0409.04b0

CompanyName: Microsoft Corporation

ProductName: Microsoft® Windows® Operating System

InternalName: netio.sys

OriginalFilename: netio.sys

ProductVersion: 6.1.7600.16385

FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)

FileDescription: Network I/O Subsystem

kimrenea · 17. januar 2011

Her er "innmaten" i pcen( Bortsett fra CPU-kjølere osv som sikkert ikke er nødvendig å vite):

Seagate Barracuda 7200.12 1TB Sata 3.0 gb/s, 32MB

Chieftec Super Series 750 W PSU

Samsung DVD RW burner

AMD Phenom 2 X4 965 Black Edition AM3

Sapphire Radeon HD 5870 2GB Gddr5 HEXAD Pci-express 2.0, eyefinity 6, 6xmini-displayport, full retail

ASUS crosshair IV extreme, socket-AM3

Kingston DDR3 HyperX 1600MHz 4 gb xmp

Bruker forresten Windows 7.

Endret 17. januar 2011 av kimrenea

kimrenea · 17. januar 2011

Nå fikk jeg enda en.. i det jeg drev å søkte rundt på google..

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Loading Dump File [C:\Users\Kim Alfredsen\Desktop\011711-30248-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

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`02c0a000 PsLoadedModuleList = 0xfffff800`02e47e50

Debug session time: Mon Jan 17 20:46:43.193 2011 (UTC + 1:00)

System Uptime: 0 days 0:09:05.504

Loading Kernel Symbols

...............................................................

................................................................

...........................

Loading User Symbols

Loading unloaded module list

.....

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {a0, 2, 0, fffff88004140867}

Unable to load image \SystemRoot\system32\DRIVERS\e1q62x64.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for e1q62x64.sys

*** ERROR: Module load completed but symbols could not be loaded for e1q62x64.sys

Probably caused by : e1q62x64.sys ( e1q62x64+1b867 )

Followup: MachineOwner

---------

2: 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: 00000000000000a0, memory referenced

Arg2: 0000000000000002, IRQL

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

Arg4: fffff88004140867, address which referenced memory

Debugging Details:

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

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb20e0

00000000000000a0

CURRENT_IRQL: 2

FAULTING_IP:

e1q62x64+1b867

fffff880`04140867 488b88a0000000 mov rcx,qword ptr [rax+0A0h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffff880027407e0 -- (.trap 0xfffff880027407e0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000

rdx=0000000000000251 rsi=0000000000000000 rdi=0000000000000000

rip=fffff88004140867 rsp=fffff88002740970 rbp=0000000000000051

r8=0000000000000200 r9=0000000000000000 r10=0000000000000000

r11=00000000000001ff r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl nz na pe nc

e1q62x64+0x1b867:

fffff880`04140867 488b88a0000000 mov rcx,qword ptr [rax+0A0h] ds:21a0:00000000`000000a0=????????????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002c79ca9 to fffff80002c7a740

STACK_TEXT:

fffff880`02740698 fffff800`02c79ca9 : 00000000`0000000a 00000000`000000a0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffff880`027406a0 fffff800`02c78920 : fffffa80`05676ab0 00000000`00000000 00000000`00000001 00000000`00000001 : nt!KiBugCheckDispatch+0x69

fffff880`027407e0 fffff880`04140867 : fffffa80`05439e50 fffffa80`058e7000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260

fffff880`02740970 fffffa80`05439e50 : fffffa80`058e7000 00000000`00000000 00000000`00000000 00000000`00000000 : e1q62x64+0x1b867

fffff880`02740978 fffffa80`058e7000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`04148ad5 : 0xfffffa80`05439e50

fffff880`02740980 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`04148ad5 fffffa80`00000000 : 0xfffffa80`058e7000

STACK_COMMAND: kb

FOLLOWUP_IP:

e1q62x64+1b867

fffff880`04140867 488b88a0000000 mov rcx,qword ptr [rax+0A0h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: e1q62x64+1b867

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: e1q62x64

IMAGE_NAME: e1q62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c364c04

FAILURE_BUCKET_ID: X64_0xD1_e1q62x64+1b867

BUCKET_ID: X64_0xD1_e1q62x64+1b867

Followup: MachineOwner

---------

Logg inn

Bluescreen

Anbefalte innlegg

kimrenea

Lenke til kommentar

Videoannonse

Mechablast

Lenke til kommentar

kimrenea

Lenke til kommentar

Mechablast

Lenke til kommentar

kimrenea

Lenke til kommentar

Phyltre

Lenke til kommentar

Mechablast

Lenke til kommentar

kimrenea

Lenke til kommentar

kimrenea

Lenke til kommentar

kimrenea

Lenke til kommentar

Opprett en konto eller logg inn for å kommentere

Opprett konto

Logg inn

Populær nå

Hvorfor flytter rikinger til Sveits? 1 2

Hvem er aktive 0 medlemmer