Hjelp! - Pcen Bluescreener!

[Jonas`C]

Heihei, jeg har en Acer Aspire One her, som har begynt å bluescreeene, gjerne en eller to ganger om dagen. Det skjedde nå nettopp, så jeg paster inn den delen som så ut til å være den viktigste av rapporten:

 

Problem Event Name: BlueScreen

OS Version: 6.1.7601.2.1.0.256.48

Locale ID: 1044

 

Er det noen her som har litt peiling på data og vet hva jeg skal gjøre? Beklager hvis jeg har postet dette feil, men jeg vil veldig gjerne ha hjelp. Takk på forhånd

[Brede_Skapstroppen]

du må gjerne beskrive litt mer om forutsetningene når du opplever bluescreen. Skjer dette helt vilkårlig eller i forbindelse med bestemte programmer. Skjer det etter at du for eksempel har sittet og spilt lenge, eller kan det skje mens maskinen står uten å være i bruk på desktop.

 

Bluescreen kan jo være relatert til mye rart, men ofte så er det på grunn av at temperaturene blir for høye inne i maskinen (les støv), Det kan være at harddisker begynner å få problemer (ikke moro), eller så kan det være at det er konflikter med drivere osv.

[Jonas`C]

En bluescreen oppstår som oftest når jeg bruker pcen normalt (skype, vegas og youtube). Jo, det kan være Symantec, står ofte "this driver is not compatible, and has been disabled". Skal jeg da bare bytte over til Microsoft security essentials?

[Brede_Skapstroppen]

sjekk device manager og se om det ligger noen gule trekanter med utropstegn på noe der inne. Det vil iallefall gi en indikasjon på hilken driver det er.

 

Ellers så ville jeg rett og slett tatt en grundig gjennomgang av pcen, og oppdatert til nyeste drivere av brikkesett, grafikk-kort og lyddrivere.

 

Acer har vel en download side som har Acer sine egne driverpakker har de ikke det da?

[Uderzo]

Last ned whocrashed. Programmet analyserer minidump fila og gir deg en beskrivelse på hva som krasjet.

Endret 28. april 2011 av Uderzo

[Jonas`C]

Disablet Symantec, og har ikke fått bluescreen siden. Håper dette var problemet!

[Jonas`C]

Huff, for et rot! Pcen bluescreener gjerne en gang om dagen, så jeg bestemte meg for å laste ned Whocrashed. Bluescreeninfo ligger i Spoiler.

 

On Mon 02.05.2011 16:20:40 GMT your computer crashed

crash dump file: C:\Windows\Minidump\050211-65692-01.dmp

This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9AF)

Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFFB456A520, 0xFFFFFFFFB456A100, 0xFFFFFFFF818E224B)

Error: NTFS_FILE_SYSTEM

file path: C:\Windows\system32\drivers\ntfs.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT File System Driver

Bug check description: This indicates a problem occurred in the NTFS file system.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

 

 

On Mon 02.05.2011 16:20:40 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9AF)

Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFFB456A520, 0xFFFFFFFFB456A100, 0xFFFFFFFF818E224B)

Error: NTFS_FILE_SYSTEM

file path: C:\Windows\system32\drivers\ntfs.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT File System Driver

Bug check description: This indicates a problem occurred in the NTFS file system.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

 

 

On Sun 01.05.2011 18:27:59 GMT your computer crashed

crash dump file: C:\Windows\Minidump\050111-73788-01.dmp

This was probably caused by the following module: hal.sys (hal+0x3829)

Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFFFFF8181F829)

Error: IRQL_NOT_LESS_OR_EQUAL

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .

Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL

 

 

 

 

On Fri 29.04.2011 14:27:18 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042911-85285-01.dmp

This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x26DA5)

Bugcheck code: 0xA (0xFFFFFFFFC4C00004, 0x2, 0x1, 0xFFFFFFFF818C1254)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\dxgmms1.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: DirectX Graphics MMS

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

 

 

On Tue 26.04.2011 08:52:18 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042611-93007-01.dmp

This was probably caused by the following module: symevent.sys (SYMEVENT+0x141C9)

Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF855A29E0, 0xFFFFFFFF855A2B4C, 0xFFFFFFFF81A31EA0)

Error: CRITICAL_OBJECT_TERMINATION

file path: C:\Windows\system32\drivers\symevent.sys

product: SYMEVENT

company: Symantec Corporation

description: Symantec Event Library

Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: symevent.sys (Symantec Event Library, Symantec Corporation).

Google query: symevent.sys Symantec Corporation CRITICAL_OBJECT_TERMINATION

 

 

 

 

On Mon 25.04.2011 12:57:00 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042511-77594-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x5ED57)

Bugcheck code: 0x50 (0xFFFFFFFF890A38D9, 0x0, 0xFFFFFFFF81A80482, 0x0)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that invalid system memory has been referenced.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

 

On Sun 24.04.2011 09:13:31 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042411-94770-01.dmp

This was probably caused by the following module: symevent.sys (SYMEVENT+0x141C9)

Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFFFFF8180B829)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\symevent.sys

product: SYMEVENT

company: Symantec Corporation

description: Symantec Event Library

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: symevent.sys (Symantec Event Library, Symantec Corporation).

Google query: symevent.sys Symantec Corporation IRQL_NOT_LESS_OR_EQUAL

 

 

 

 

On Fri 22.04.2011 16:52:06 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042211-65645-01.dmp

This was probably caused by the following module: npfs.sys (Npfs+0x9EFC)

Bugcheck code: 0x50 (0xFFFFFFFFFF69CB99, 0x0, 0xFFFFFFFF8BA3DEFC, 0x0)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\drivers\npfs.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NPFS Driver

Bug check description: This indicates that invalid system memory has been referenced.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

 

 

On Fri 22.04.2011 16:34:30 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042211-65894-01.dmp

This was probably caused by the following module: symevent.sys (SYMEVENT+0x141C9)

Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF8549F728, 0xFFFFFFFF8549F894, 0xFFFFFFFF819FFA50)

Error: CRITICAL_OBJECT_TERMINATION

file path: C:\Windows\system32\drivers\symevent.sys

product: SYMEVENT

company: Symantec Corporation

description: Symantec Event Library

Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: symevent.sys (Symantec Event Library, Symantec Corporation).

Google query: symevent.sys Symantec Corporation CRITICAL_OBJECT_TERMINATION

 

 

 

 

On Fri 22.04.2011 08:36:55 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042211-78094-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x20D5E2)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF81A4F5E2, 0xFFFFFFFFADF28B28, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

 

On Wed 20.04.2011 18:21:56 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042011-69779-01.dmp

This was probably caused by the following module: ntfs.sys (Ntfs+0xA8CA1)

Bugcheck code: 0x50 (0xFFFFFFFFDEA2475E, 0x0, 0xFFFFFFFF86CBBCA1, 0x2)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\drivers\ntfs.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT File System Driver

Bug check description: This indicates that invalid system memory has been referenced.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

 

 

On Mon 18.04.2011 15:42:19 GMT your computer crashed

crash dump file: C:\Windows\Minidump\041811-79310-01.dmp

This was probably caused by the following module: symevent.sys (SYMEVENT+0x141F9)

Bugcheck code: 0x1A (0x41284, 0xE560001, 0xDB5, 0xFFFFFFFFC0402000)

Error: MEMORY_MANAGEMENT

file path: C:\Windows\system32\drivers\symevent.sys

product: SYMEVENT

company: Symantec Corporation

description: Symantec Event Library

Bug check description: This indicates that a severe memory management error occurred.

This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: symevent.sys (Symantec Event Library, Symantec Corporation).

Google query: symevent.sys Symantec Corporation MEMORY_MANAGEMENT

 

 

 

 

On Fri 08.04.2011 13:37:03 GMT your computer crashed

crash dump file: C:\Windows\Minidump\040811-78952-01.dmp

This was probably caused by the following module: stream.sys (STREAM+0x7200)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF937A7200, 0xFFFFFFFF865E7BB8, 0xFFFFFFFF865E7790)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\drivers\stream.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: WDM CODEC Class Device Driver 2.0

Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

 

 

On Sun 03.04.2011 12:00:46 GMT your computer crashed

crash dump file: C:\Windows\Minidump\040311-77844-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x5EBA6)

Bugcheck code: 0x1A (0x41287, 0x18, 0x0, 0x0)

Error: MEMORY_MANAGEMENT

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a severe memory management error occurred.

This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

 

On Sun 27.03.2011 10:37:01 GMT your computer crashed

crash dump file: C:\Windows\Minidump\032711-69919-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x5EBA6)

Bugcheck code: 0x50 (0xFFFFFFFF94FFE000, 0x0, 0xFFFFFFFF8187DCD3, 0x0)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that invalid system memory has been referenced.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

 

[Woltox]

Reinstaller Windows.

Det er windows filer som kræsjer.

[Bender Rodriguez]

[Brede_Skapstroppen]

Når det gjelder han fyre på bildet så ville han sikkert hatt ressurser til å fikse problemet, men han hadde ikke lagt opp til at du skulle gjøre noe med det selv....og det blir ikke gratis

 

Ja du bør prøve å reinstallere windows, men det kan være at dette problemet faktisk ligger i hardwaren din. Den filen som nevnes som årsak til krasjen er vesentlig i forbindelse med harddisken så vidt jeg kan huske, og når denne står som årsak til stadige og tilfeldige BSOD så ville jeg anta at det kan være et tegn på at harddisken din er i ferd med å ta kvelden.

 

Sørg iallefall for at du har tatt backup av de filene du ikke vil miste, reinstaller windows med en skikkelig formattering.

 

Hvis ikke dette hjelper så tipper jeg at problemet gradvis vil forverre seg frem til det er definitivt slutt for harddisker.

Endret 3. mai 2011 av Brede_Skapstroppen

[Jonas`C]

Situasjonen forverrer seg, desverre. I dag har pcen bluescreenet to ganger, og fryst to ganger. Kan det være Symantec det er noe galt med? Lest litt igjennom WhoCrashed, og det ser ut som at mange av bluescreenene er i forbindelse med Symantec. Nå er jo ikke jeg noen dataproff, så dette får dere svare på . Er det noe jeg har gjort med pcen, eller var dette "dømt til å skje"? Atm er dette den eneste pcen jeg har tilgang til, så ville vært kjipt om denne gikk i vasken. Vil gjerne slippe å reinstallere Windows, så hvis dere har en "magic fix" så forguder jeg dere! Tusen takk for alle svar

 

 

On Fri 06.05.2011 17:28:58 GMT your computer crashed

crash dump file: C:\Windows\Minidump\050611-72056-01.dmp

This was probably caused by the following module: msrpc.sys (msrpc+0x8D1C)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF86DADD1C, 0xFFFFFFFFBE40B6E8, 0xFFFFFFFFBE40B2C0)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\drivers\msrpc.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Kernel Remote Procedure Call Provider

Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

 

 

On Fri 06.05.2011 17:28:58 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x1E)

Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFFFF86DADD1C, 0xFFFFFFFFBE40B6E8, 0xFFFFFFFFBE40B2C0)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

 

On Fri 06.05.2011 12:27:27 GMT your computer crashed

crash dump file: C:\Windows\Minidump\050611-88717-01.dmp

This was probably caused by the following module: hal.sys (hal+0x3839)

Bugcheck code: 0xA (0xFFFFFFFFF1F18001, 0x2, 0x1, 0xFFFFFFFF81817839)

Error: IRQL_NOT_LESS_OR_EQUAL

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .

Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL

 

 

 

 

On Thu 05.05.2011 14:23:34 GMT your computer crashed

crash dump file: C:\Windows\Minidump\050511-75270-01.dmp

This was probably caused by the following module: symevent.sys (SYMEVENT+0x141F9)

Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFFFFF81C12829)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\symevent.sys

product: SYMEVENT

company: Symantec Corporation

description: Symantec Event Library

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: symevent.sys (Symantec Event Library, Symantec Corporation).

Google query: symevent.sys Symantec Corporation IRQL_NOT_LESS_OR_EQUAL

 

 

 

 

On Thu 05.05.2011 13:07:01 GMT your computer crashed

crash dump file: C:\Windows\Minidump\050511-69935-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x38C5B)

Bugcheck code: 0xA (0xFFFFFFFFC0805B10, 0x0, 0x1, 0xFFFFFFFF818A1886)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

 

On Tue 03.05.2011 12:57:15 GMT your computer crashed

crash dump file: C:\Windows\Minidump\050311-68016-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x24A6CC)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF81A676CC, 0xFFFFFFFF94E82BDC, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

 

On Mon 02.05.2011 16:20:40 GMT your computer crashed

crash dump file: C:\Windows\Minidump\050211-65692-01.dmp

This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9AF)

Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFFB456A520, 0xFFFFFFFFB456A100, 0xFFFFFFFF818E224B)

Error: NTFS_FILE_SYSTEM

file path: C:\Windows\system32\drivers\ntfs.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT File System Driver

Bug check description: This indicates a problem occurred in the NTFS file system.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

 

 

On Sun 01.05.2011 18:27:59 GMT your computer crashed

crash dump file: C:\Windows\Minidump\050111-73788-01.dmp

This was probably caused by the following module: hal.sys (hal+0x3829)

Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFFFFF8181F829)

Error: IRQL_NOT_LESS_OR_EQUAL

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .

Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL

 

 

 

 

On Fri 29.04.2011 14:27:18 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042911-85285-01.dmp

This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x26DA5)

Bugcheck code: 0xA (0xFFFFFFFFC4C00004, 0x2, 0x1, 0xFFFFFFFF818C1254)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\dxgmms1.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: DirectX Graphics MMS

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

 

 

On Tue 26.04.2011 08:52:18 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042611-93007-01.dmp

This was probably caused by the following module: symevent.sys (SYMEVENT+0x141C9)

Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF855A29E0, 0xFFFFFFFF855A2B4C, 0xFFFFFFFF81A31EA0)

Error: CRITICAL_OBJECT_TERMINATION

file path: C:\Windows\system32\drivers\symevent.sys

product: SYMEVENT

company: Symantec Corporation

description: Symantec Event Library

Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: symevent.sys (Symantec Event Library, Symantec Corporation).

Google query: symevent.sys Symantec Corporation CRITICAL_OBJECT_TERMINATION

 

 

 

 

On Mon 25.04.2011 12:57:00 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042511-77594-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x5ED57)

Bugcheck code: 0x50 (0xFFFFFFFF890A38D9, 0x0, 0xFFFFFFFF81A80482, 0x0)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that invalid system memory has been referenced.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

 

On Sun 24.04.2011 09:13:31 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042411-94770-01.dmp

This was probably caused by the following module: symevent.sys (SYMEVENT+0x141C9)

Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFFFFF8180B829)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\symevent.sys

product: SYMEVENT

company: Symantec Corporation

description: Symantec Event Library

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: symevent.sys (Symantec Event Library, Symantec Corporation).

Google query: symevent.sys Symantec Corporation IRQL_NOT_LESS_OR_EQUAL

 

 

 

 

On Fri 22.04.2011 16:52:06 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042211-65645-01.dmp

This was probably caused by the following module: npfs.sys (Npfs+0x9EFC)

Bugcheck code: 0x50 (0xFFFFFFFFFF69CB99, 0x0, 0xFFFFFFFF8BA3DEFC, 0x0)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\drivers\npfs.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NPFS Driver

Bug check description: This indicates that invalid system memory has been referenced.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

 

 

On Fri 22.04.2011 16:34:30 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042211-65894-01.dmp

This was probably caused by the following module: symevent.sys (SYMEVENT+0x141C9)

Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF8549F728, 0xFFFFFFFF8549F894, 0xFFFFFFFF819FFA50)

Error: CRITICAL_OBJECT_TERMINATION

file path: C:\Windows\system32\drivers\symevent.sys

product: SYMEVENT

company: Symantec Corporation

description: Symantec Event Library

Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: symevent.sys (Symantec Event Library, Symantec Corporation).

Google query: symevent.sys Symantec Corporation CRITICAL_OBJECT_TERMINATION

 

 

 

 

On Fri 22.04.2011 08:36:55 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042211-78094-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x20D5E2)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF81A4F5E2, 0xFFFFFFFFADF28B28, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.