Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Blue Screens [PAGE_FAULT_IN_NONPAGED_AREA & DRIVER_IRQL_NOT_LESS_O

Started by dOCTAWAALd , Jun 02 2012 06:37 AM

  • This topic is locked This topic is locked

#1
dOCTAWAALd
Posted 02 June 2012 - 06:37 AM

dOCTAWAALd

    New Member

  • Member
  • Pip
  • 7 posts
Hi all,

Since a few weeks i started gettings blue screens for PAGE_FAULT_IN_NONPAGED_AREA & DRIVER_IRQL_NOT_LESS_OR_EQUAL
I didnt make any HW changes to my system

I already tried memtest86 wich didnt give any errors.
I also tried updating my drivers with DriverPack Solution 11 wich updated 56 drivers.

The crashes mostly appear when i play a game.

Info & List :

==================================================
Dump File         : 060212-42541-01.dmp
Crash Time        : 2/06/2012 13:42:30
Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code    : 0x00000050
Parameter 1       : fffffa80`29e6bc00
Parameter 2       : 00000000`00000000
Parameter 3       : fffff800`02ffbdd3
Parameter 4       : 00000000`00000002
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processor         : x64
Crash Address     : ntoskrnl.exe+7f1c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\060212-42541-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 280.568
==================================================

==================================================
Dump File         : 060212-25381-01.dmp
Crash Time        : 2/06/2012 8:08:48
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : fffffa80`2e46e578
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff880`0415eb3d
Caused By Driver  : dxgmms1.sys
Caused By Address : dxgmms1.sys+5b3d
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7f1c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\060212-25381-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276.200
==================================================

==================================================
Dump File         : 060212-24117-01.dmp
Crash Time        : 2/06/2012 7:50:03
Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code    : 0x00000050
Parameter 1       : fffff8a0`2020bc50
Parameter 2       : 00000000`00000000
Parameter 3       : fffff880`05950586
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgmms1.sys
Caused By Address : dxgmms1.sys+1011b
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7f1c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\060212-24117-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276.200
==================================================

==================================================
Dump File         : 060112-25662-01.dmp
Crash Time        : 1/06/2012 20:25:03
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : fffff880`268ef9c8
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000008
Parameter 4       : fffff880`268ef9c8
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processor         : x64
Crash Address     : ntoskrnl.exe+7f1c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\060112-25662-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 316.120
==================================================

==================================================
Dump File         : 052512-17144-01.dmp
Crash Time        : 25/05/2012 13:53:38
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : fffff880`209ee720
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff800`02e85943
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processor         : x64
Crash Address     : ntoskrnl.exe+7f1c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\052512-17144-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276.256
==================================================

==================================================
Dump File         : 052412-18392-01.dmp
Crash Time        : 24/05/2012 18:50:09
Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code    : 0x00000050
Parameter 1       : fffff960`203a4498
Parameter 2       : 00000000`00000000
Parameter 3       : fffff960`00178ab1
Parameter 4       : 00000000`00000002
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processor         : x64
Crash Address     : ntoskrnl.exe+7f1c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\052412-18392-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276.200
==================================================

==================================================
Dump File         : 052412-17409-01.dmp
Crash Time        : 24/05/2012 18:23:21
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : fffff880`23168610
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff800`02ed3547
Caused By Driver  : USBPORT.SYS
Caused By Address : USBPORT.SYS+1156a
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7f1c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\052412-17409-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276.200
==================================================

==================================================
Dump File         : 052412-15100-01.dmp
Crash Time        : 24/05/2012 17:57:21
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : fffffa80`2a2b8108
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff800`02ee1570
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processor         : x64
Crash Address     : ntoskrnl.exe+7f1c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\052412-15100-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276.200
==================================================

==================================================
Dump File         : 051012-33789-01.dmp
Crash Time        : 10/05/2012 13:38:11
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : fffff880`231d9af0
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000000
Parameter 4       : fffff800`02e8e321
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processor         : x64
Crash Address     : ntoskrnl.exe+7f1c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\051012-33789-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276.200
==================================================

Any help on this ?

Greetz dOCTAWAALd

Edited by dOCTAWAALd, 02 June 2012 - 06:49 AM.

  • 0

Advertisements

#2
happyrock
Posted 02 June 2012 - 10:05 AM

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
Hi dOCTAWAALd ... :wave: ..:welcome:

download and install WhoCrashed from http://www.softpedia...oCrashed.shtml' class='bbc_url' title='External link' rel='nofollow external'>here..
This program checks for any drivers which may have been causing your computer to crash....

click on it...then run...then next...put a tick in accept...then next..put a tick in the don't create a start menu folder..then next...put a tick in create a desktop icon..then install.. then make sure there is a tick in launch whocrashed...then finish...then click Analyze ...

if you get a message
This software requires the right version of Windows Debugging Tools for your type of computer. Because this is not normally installed and is not redistributable, we suggest you select the download option from below. Then the right package will be downloaded to a temporary folder and the required files will be extracted from the package automatically. You only need to do this once
click on download then try running it again
WhoCrashed will create report...you have to scroll down to see it
Copy and paste it into your next reply..
  • 0

#3
dOCTAWAALd
Posted 04 June 2012 - 09:11 AM

dOCTAWAALd

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Hi,

Thanks for your reply :D

I also did another run on Memtest86
Wich gave the following errors :
-=[PICTURE LINK]=-

I ran the program called 'Who Crashed'
Here's my output.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: DOCTAWAALD-I7
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™ i7 CPU 920 @ 2.67GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 12875587584 total
VM: 2147352576, free: 1962541056



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sat 2/06/2012 11:39:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060212-42541-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFA8029E6BC00, 0x0, 0xFFFFF80002FFBDD3, 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.


On Sat 2/06/2012 11:39:49 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x9D2C)
Bugcheck code: 0x50 (0xFFFFFA8029E6BC00, 0x0, 0xFFFFF80002FFBDD3, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 Sat 2/06/2012 6:06:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060212-25381-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x5B3D)
Bugcheck code: 0xD1 (0xFFFFFA802E46E578, 0x2, 0x1, 0xFFFFF8800415EB3D)
Error: DRIVER_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 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 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 Sat 2/06/2012 5:48:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060212-24117-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF8A02020BC50, 0x0, 0xFFFFF88005950586, 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.


On Fri 1/06/2012 18:22:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060112-25662-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0xFFFFF880268EF9C8, 0x2, 0x8, 0xFFFFF880268EF9C8)
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 Fri 25/05/2012 11:52:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052512-17144-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFF880209EE720, 0x2, 0x1, 0xFFFFF80002E85943)
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 Thu 24/05/2012 16:48:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052412-18392-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF960203A4498, 0x0, 0xFFFFF96000178AB1, 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.


On Thu 24/05/2012 16:21:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052412-17409-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x1156A)
Bugcheck code: 0xA (0xFFFFF88023168610, 0x2, 0x1, 0xFFFFF80002ED3547)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Poortstuurprogramma voor USB 1.1 en 2.0
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 Thu 24/05/2012 15:55:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052412-15100-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFFA802A2B8108, 0x2, 0x1, 0xFFFFF80002EE1570)
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 Thu 10/05/2012 11:35:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051012-33789-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFF880231D9AF0, 0x2, 0x0, 0xFFFFF80002E8E321)
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 1/05/2012 9:02:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050112-40451-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x79E0)
Bugcheck code: 0x116 (0xFFFFFA800A70F010, 0xFFFFF880044079E0, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR




On Mon 16/04/2012 17:28:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041612-28828-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800BE9D028, 0xFA000000, 0x400405)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 16/04/2012 15:08:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041612-26535-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800C06A028, 0xFE000000, 0x40014A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 2/02/2012 8:52:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020212-28938-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800BF3D028, 0xBE000000, 0x40014A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

14 crash dumps have been found and analyzed. A third party driver has 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:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
  • 0

#4
happyrock
Posted 04 June 2012 - 09:32 AM

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
you can't have any errors with memtest so if you have more than 1 stick of ram remove 1 then test the ram again...stop the test as soon as you see the first error...as that stick will have to be replaced...test any other sticks of ram one by one

its important you unplug from the wall before removing the ram...also be ESD safe
  • 0

#5
dOCTAWAALd
Posted 04 June 2012 - 10:02 AM

dOCTAWAALd

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Hi,

Thanks , i will retry with only 1 ram-piece tommorow.

Ill post the results ;)

Greetz dOCTAWAALd
  • 0

#6
dOCTAWAALd
Posted 07 June 2012 - 09:39 AM

dOCTAWAALd

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Hi,

I tested every RAM-piece

This time none of them gave any errors.

RAM 1 :
-=[PIC 1]=-

RAM 2 :
-=[PIC 2]=-
**This one tested for 9 hours the first time. But forgot to take a picture so did another 5hr test**

RAM 3 :
-=[PIC 3]=-

So any ideas on this situation ?

Greetz dOCTAWAALd

Edited by dOCTAWAALd, 07 June 2012 - 09:44 AM.

  • 0

#7
happyrock
Posted 07 June 2012 - 10:04 AM

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
only put 2 sticks of the good ram back in...they should be in the same colored slots...whatever color is closest to the cpu
then go here and run the AMD Driver Autodetect detects your graphics card and operating system and tells you if a new driver is available. If there is a new driver, the tool will download it with a click of a button and start the installation process...after the install reboot
  • 0

#8
dOCTAWAALd
Posted 07 June 2012 - 10:07 AM

dOCTAWAALd

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
I have the lastest driver installed.
And why only 2 rampieces ?
  • 0

#9
happyrock
Posted 07 June 2012 - 10:20 AM

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
when you run 3 sticks of ram your system will only run in single channel mode...
2 sticks will run in dual channel mode that nets you a higher throughput...
when you replace that bad stick it has to be the exact same make and model number or you can have more problems...
try uninstalling your video driver...then run the auto detect again...that way you will get a fresh copy...
  • 0

#10
dOCTAWAALd
Posted 07 June 2012 - 11:16 AM

dOCTAWAALd

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
I reinstalled the drivers.
But no RAM-pieces gave any errors.
So there's no need to replace any of them
  • 0

#11
happyrock
Posted 07 June 2012 - 03:44 PM

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
well whats this then if you have no errors...as long as the sticks have no errors they do not need to be replaced...only if they have errors

Attached Thumbnails

  • errors.jpg

  • 0

#12
dOCTAWAALd
Posted 08 June 2012 - 02:39 AM

dOCTAWAALd

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Well my problems seems to be solved.

Thanks :D
  • 0

#13
happyrock
Posted 08 June 2012 - 08:24 AM

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
your welcome... :thumbsup:
  • 0
Back to Windows Vista and Windows 7 · Next Unread Topic →




Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

  1. Geeks to Go Forum
  2. → Retired Forums
  3. → Windows Vista and Windows 7

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP