Bluescreen vid omstart/uppstart/viloläge
Hej! Har haft ett problem med min dator väldigt länge, har haft det uppe i forumet innan men ej fått några tips
så försöker igen och hoppas nån vänlig skäl kan hjälpa.
Problemet är att om man inte dödar strömmen helt - dvs. dra ur den från nätagget, så går det ej att
starta upp den utan att få en bluescreen. Samma sak händer från viloläge och omstart. Så för att systemet
skall gå stabilt måste man döda strömmen helt varje gång.
Har formaterat, gjort driver sweep och nu kört Who crashed ett tag, så jag hoppas
någon kan hjälpa mig att tyda felkoderna bättre.
37 crash dumps have been found and analyzed. Only 15 are included in this report. 3 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
unknown
unknown_module_00000000`00000000.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X6 1090T Processor AMD586, level: 16
6 logical processors, active mask: 63
RAM: 6439886848 total
VM: 2147352576, free: 1940365312
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 2012-04-19 09:35:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041912-11466-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FA3018, 0xFFFFF880069F9080, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Thu 2012-04-19 09:35:55 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FA3018, 0xFFFFF880069F9080, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Thu 2012-04-19 09:34:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041912-12261-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x109 (0xA3A039D8974237B5, 0x0, 0xF4AC4AFC35EDFDEF, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Wed 2012-04-18 06:06:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041812-10810-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000000.sys (Unloaded_Unknown_Module_00000000`00000000+0x1)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F59018, 0xFFFFF8800A669080, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: unknown_module_00000000`00000000.sys .
Google query: unknown_module_00000000`00000000.sys SYSTEM_SERVICE_EXCEPTION
On Wed 2012-04-18 06:05:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041812-12651-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0xD1 (0x20000051, 0x2, 0x0, 0xFFFFF88001668FF9)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 2012-04-16 15:10:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041612-10998-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F5A018, 0xFFFFF8800A7FA080, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 2012-04-16 15:07:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041612-12402-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x109 (0xA3A039D896F194F5, 0x0, 0xABB4C04E05923CE8, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Mon 2012-04-16 15:01:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041612-13712-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x109 (0xA3A039D89749D8BB, 0x0, 0x34B96FE16C7318F7, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Sat 2012-04-14 09:42:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041412-15818-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D1C1)
Bugcheck code: 0xFE (0x6, 0xFFFFFA8007F6E010, 0x43787254, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: USB 1.1 & 2.0 portdrivrutin
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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 Thu 2012-04-12 05:35:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041212-19468-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF880012026E4)
Bugcheck code: 0xA (0x4000000000, 0x2, 0x0, 0xFFFFF80002C7EB12)
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: Unknown .
Google query: Unknown IRQL_NOT_LESS_OR_EQUAL
On Sun 2012-04-08 19:20:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040812-11559-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0xC0000221 (0xFFFFF8A00017D4E0, 0x0, 0x0, 0x0)
Error: STATUS_IMAGE_CHECKSUM_MISMATCH
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 driver or a system DLL has been corrupted.
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. There is a possibility this problem was caused by a virus or other malware.
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 2012-04-03 05:31:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040312-11060-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002DA1038, 0xFFFFF88008654080, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 2012-04-03 05:28:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040312-13899-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70510)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 2012-04-02 13:20:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123109-21340-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D1C1)
Bugcheck code: 0xFE (0x6, 0xFFFFFA8007CA8580, 0x43787254, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: USB 1.1 & 2.0 portdrivrutin
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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 2012-04-02 10:29:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040212-14180-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x50 (0xFFFFF90081AD2C38, 0x0, 0xFFFFF96000105136, 0x2)
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.
1.r4 - SSD 80GB - Raptor - Asus dc2 770 - AX850 - Vengeance 8gb - FX-8350 som hatar OC -corsair h110
2. PHII X3 - Gtx260 - SP 850W - WD Caviar black - Crucial 8gb
Ipad3, Lumia 920, Wii U, ps3, SGS3
