Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD - possible graphics card, PSU, or motherboard failure?


  • Please log in to reply
6 replies to this topic

#1 laceyGB

laceyGB

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:02:06 AM

Posted 24 April 2013 - 09:50 PM

About two weeks ago, my XP machine got cursed by blue screens every time I ran it for more than 20 minutes. Mostly 0XA IRQL_NOT_LESS_OR_EQUAL and 0X1A MEMORY_MANAGEMENT errors. According to BlueScreenView, ntkrnlpa.exe was the main culprit. I tried a whole bunch of things, but they didn't help:

Ran memtest86 for 9 hours, it reported no problems with RAM
Updated graphics card drivers
Removed all graphics card drivers
System restored
Repaired Windows with the installation CD
tried RAM in different slots

Finally I checked my hard drive with Seatools, and it reported 205 bad sectors over 3 long tests. I figured the hard drive was responsible, so I bought a new one and got myself Windows 7 for the fresh install.

The blue screens persist. According to BlueScreenView, 85% of the minidumps are 0X1A MEMORY_MANAGEMENT errors, with the main culprit being ntoskrnl.exe. I ran Memtest86+ again, this time for 24 hours, but again it reported no errors. A bit disappointing, since my RAM has a lifetime warranty.

My system specs are:

Intel Q6600
Asus P5n32e-SLI
Seasonic 900w
Nvidia 8800 GTX
Corsair CM2X2048 - 6400CD
Western Digital 1tb blue

Any idea what the issue could be? Could it be a failing graphics card, motherboard, or PSU?

 

Thanks :)


Edited by laceyGB, 24 April 2013 - 09:58 PM.


BC AdBot (Login to Remove)

 


#2 TwinHeadedEagle

TwinHeadedEagle

  • Security Colleague
  • 352 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Serbia
  • Local time:02:06 AM

Posted 25 April 2013 - 04:39 AM

Please download and install Who Crashed --> http://www.resplendence.com/download/whocrashedSetup.exe
 
Run the program and click on Analyze. When program finishes analyzing, click on OK. Then right click --> Select All --> right click Copy
 
Copy the content here.


#3 laceyGB

laceyGB
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:02:06 AM

Posted 25 April 2013 - 05:46 AM

Hi TwoHeadedEagle, here you go:

 

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

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 2145968128 total
VM: 2147352576, free: 1954783232


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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 25/04/2013 06:02:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042513-20670-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41284, 0x237AF001, 0x1B7E1, 0xFFFFF70001080000)
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 that cannot be identified at this time.



On Thu 25/04/2013 06:02:34 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0x16D8)
Bugcheck code: 0x1A (0x41284, 0x237AF001, 0x1B7E1, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 25/04/2013 02:21:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042513-30716-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41284, 0x23C5F001, 0x1D1FC, 0xFFFFF70001080000)
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 that cannot be identified at this time.



On Thu 25/04/2013 01:40:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042513-20233-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41284, 0x21B81001, 0x19142, 0xFFFFF70001080000)
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 that cannot be identified at this time.



On Thu 25/04/2013 00:18:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042513-10389-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC500144B0, 0x80E0000004536802, 0xFFFFF6FD400009A1)
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 that cannot be identified at this time.



On Thu 25/04/2013 00:15:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042513-32307-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC50002FB0, 0x80B000000399C882, 0xFFFFF6FC40009969)
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 that cannot be identified at this time.



On Wed 24/04/2013 20:12:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042413-22011-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41284, 0xFFFFF980276A5001, 0xBC42, 0xFFFFF780C0000000)
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 that cannot be identified at this time.



On Wed 24/04/2013 19:01:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042413-22604-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41284, 0x23B8F001, 0xE9F0, 0xFFFFF70001080000)
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 that cannot be identified at this time.



On Tue 23/04/2013 16:28:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042313-21262-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x4E (0x99, 0x7471, 0x2, 0x5DFF0)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time.



On Tue 23/04/2013 16:02:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042313-26722-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x4E (0x2, 0x3E00, 0x7FEEF, 0x1)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time.



On Tue 23/04/2013 14:54:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042313-24304-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x4E (0x99, 0x17B2, 0x0, 0x1772)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time.



On Tue 23/04/2013 13:14:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042313-22432-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41284, 0x22551001, 0x1C6A1, 0xFFFFF70001080000)
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 that cannot be identified at this time.



On Tue 23/04/2013 12:27:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042313-24242-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41284, 0x232C1001, 0xA8F9, 0xFFFFF70001080000)
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 that cannot be identified at this time.


Edited by laceyGB, 25 April 2013 - 05:49 AM.


#4 TwinHeadedEagle

TwinHeadedEagle

  • Security Colleague
  • 352 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Serbia
  • Local time:02:06 AM

Posted 25 April 2013 - 12:09 PM

I would test the RAM memory for errors

Here is the tutorial --> http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Edited by TwinHeadedEagle, 25 April 2013 - 12:09 PM.


#5 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,752 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:05:06 PM

Posted 25 April 2013 - 01:04 PM

 Please download MiniToolBox  , save it to your desktop and run it.

 Checkmark the following checkboxes:

  List last 10 Event Viewer log
  List Installed Programs
  List Users, Partitions and Memory size.


 Click on Go to start the scan.  Once it is finished highlight the text, copy it and paste it in your next post.

 

Please use the following link to provide us with information about your computer so that we can assist you.

How to Publish a Snapshot using Speccy


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#6 laceyGB

laceyGB
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:02:06 AM

Posted 25 April 2013 - 04:18 PM

I would test the RAM memory for errors

Here is the tutorial --> http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

Hmm, I already ran memtest86+ for 24 hours - it didn't detect any errors.



#7 laceyGB

laceyGB
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:02:06 AM

Posted 25 April 2013 - 04:32 PM

 Please download MiniToolBox  , save it to your desktop and run it.

 Checkmark the following checkboxes:

  List last 10 Event Viewer log
  List Installed Programs
  List Users, Partitions and Memory size.


 Click on Go to start the scan.  Once it is finished highlight the text, copy it and paste it in your next post.

 

Please use the following link to provide us with information about your computer so that we can assist you.

How to Publish a Snapshot using Speccy

 

Hi, here's the Speccy snapshot:

 

http://speccy.piriform.com/results/tI0r0tllcfMbZqkSxMGvTSA

 

 

and the MiniToolBox log:

MiniToolBox by Farbar  Version:21-04-2013
Ran by Username (administrator) on 25-04-2013 at 22:22:06
Running from "C:\Users\Username\Desktop"
Windows 7 Professional Service Pack 1 (X64)
Boot Mode: Normal
***************************************************************************

========================= Event log errors: ===============================

Application errors:
==================
Error: (04/25/2013 09:41:40 PM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (04/25/2013 08:02:05 PM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (04/25/2013 02:41:42 PM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (04/25/2013 02:15:50 PM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (04/25/2013 07:03:38 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (04/25/2013 05:35:28 AM) (Source: Application Error) (User: )
Description: Faulting application name: Core Temp.exe, version: 1.0.0.0, time stamp: 0x5130cd0e
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0xd40
Faulting application start time: 0xCore Temp.exe0
Faulting application path: Core Temp.exe1
Faulting module path: Core Temp.exe2
Report Id: Core Temp.exe3

Error: (04/25/2013 04:47:32 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (04/25/2013 03:22:54 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (04/25/2013 02:41:18 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (04/25/2013 01:23:02 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003


System errors:
=============
Error: (04/25/2013 09:41:38 PM) (Source: BugCheck) (User: )
Description: 0x0000001a (0x0000000000041284, 0x00000000272d9001, 0x0000000000013feb, 0xfffff70001080000)C:\Windows\MEMORY.DMP042513-21512-01

Error: (04/25/2013 09:41:37 PM) (Source: EventLog) (User: )
Description: The previous system shutdown at 21:39:47 on ?25/?04/?2013 was unexpected.

Error: (04/25/2013 08:02:03 PM) (Source: BugCheck) (User: )
Description: 0x0000004e (0x0000000000000099, 0x0000000000003eaa, 0x0000000000000002, 0x0000000000003b2d)C:\Windows\MEMORY.DMP042513-23212-01

Error: (04/25/2013 08:02:01 PM) (Source: EventLog) (User: )
Description: The previous system shutdown at 20:00:40 on ?25/?04/?2013 was unexpected.

Error: (04/25/2013 07:56:40 PM) (Source: bowser) (User: )
Description: The master browser has received a server announcement from the computer 7-PC
that believes that it is the master browser for the domain on transport NetBT_Tcpip_{E5BC91BE-AEF2-4F3A-A3CB-6AAC6F4DB149}.
The master browser is stopping or an election is being forced.

Error: (04/25/2013 05:14:28 PM) (Source: bowser) (User: )
Description: The master browser has received a server announcement from the computer 7-PC
that believes that it is the master browser for the domain on transport NetBT_Tcpip_{E5BC91BE-AEF2-4F3A-A3CB-6AAC6F4DB149}.
The master browser is stopping or an election is being forced.

Error: (04/25/2013 04:13:04 PM) (Source: Microsoft-Windows-HAL) (User: )
Description: The platform firmware has corrupted memory across the previous system power transition.  Please check for updated firmware for your system.

Error: (04/25/2013 03:10:07 PM) (Source: bowser) (User: )
Description: The master browser has received a server announcement from the computer 7-PC
that believes that it is the master browser for the domain on transport NetBT_Tcpip_{E5BC91BE-AEF2-4F3A-A3CB-6AAC6F4DB149}.
The master browser is stopping or an election is being forced.

Error: (04/25/2013 02:41:40 PM) (Source: BugCheck) (User: )
Description: 0x0000004e (0x0000000000000099, 0x0000000000007814, 0x0000000000000002, 0x0000000000007812)C:\Windows\MEMORY.DMP042513-19936-01

Error: (04/25/2013 02:41:39 PM) (Source: EventLog) (User: )
Description: The previous system shutdown at 14:40:31 on ?25/?04/?2013 was unexpected.


Microsoft Office Sessions:
=========================
Error: (04/25/2013 09:41:40 PM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (04/25/2013 08:02:05 PM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (04/25/2013 02:41:42 PM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (04/25/2013 02:15:50 PM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (04/25/2013 07:03:38 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (04/25/2013 05:35:28 AM) (Source: Application Error)(User: )
Description: Core Temp.exe1.0.0.05130cd0entdll.dll6.1.7601.177254ec4aa8ec000037400000000000c40f2d4001ce416e485320c4C:\Program Files\Core Temp\Core Temp.exeC:\Windows\SYSTEM32\ntdll.dll8d6be894-ad61-11e2-8138-001d6030ecb3

Error: (04/25/2013 04:47:32 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (04/25/2013 03:22:54 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (04/25/2013 02:41:18 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (04/25/2013 01:23:02 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003


CodeIntegrity Errors:
===================================
  Date: 2013-04-25 03:22:37.600
  Description: Windows is unable to verify the image integrity of the file \Device\HarddiskVolume2\Windows\System32\drivers\nvlddmkm.sys because file hash could not be found on the system. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.


=========================== Installed Programs ============================

µTorrent (Version: 2.2.1)
Adobe Flash Player 11 Plugin (Version: 11.7.700.169)
ASUS Xonar DG Audio Driver
avast! Free Antivirus (Version: 8.0.1483.0)
CamStudio version 2.7 (Version: 2.7)
Cisco EAP-FAST Module (Version: 2.2.14)
Cisco LEAP Module (Version: 1.0.19)
Cisco PEAP Module (Version: 1.1.6)
Core Temp 1.0 RC5 (Version: 1.0)
CrystalDiskInfo 5.6.0 (Version: 5.6.0)
Edimax RT2860 Wireless LAN Card (Version: 1.5.5.0)
Fallout: New Vegas
Host OpenAL (ADI)
Microsoft .NET Framework 4 Client Profile (Version: 4.0.30319)
Microsoft .NET Framework 4 Extended (Version: 4.0.30319)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17 (Version: 9.0.30729)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161 (Version: 9.0.30729.6161)
Microsoft Visual C++ 2010  x64 Redistributable - 10.0.30319 (Version: 10.0.30319)
Microsoft Visual C++ 2010  x86 Redistributable - 10.0.30319 (Version: 10.0.30319)
Mozilla Firefox 20.0.1 (x86 en-US) (Version: 20.0.1)
MPC-HC 1.6.6.6957 (3975d54) (64-bit) (Version: 1.6.6.6957)
Nexus Mod Manager (Version: 0.44.8)
NVIDIA Control Panel 314.22 (Version: 314.22)
NVIDIA Graphics Driver 314.22 (Version: 314.22)
NVIDIA Install Application (Version: 2.1002.115.743)
NVIDIA PhysX (Version: 9.12.1031)
NVIDIA PhysX System Software 9.12.1031 (Version: 9.12.1031)
Speccy (Version: 1.21)
Steam (Version: 1.0.0.0)
Update for Microsoft .NET Framework 4 Client Profile (KB2468871) (Version: 1)
Update for Microsoft .NET Framework 4 Client Profile (KB2533523) (Version: 1)
Update for Microsoft .NET Framework 4 Client Profile (KB2600217) (Version: 1)
Update for Microsoft .NET Framework 4 Extended (KB2468871) (Version: 1)
Update for Microsoft .NET Framework 4 Extended (KB2533523) (Version: 1)
Update for Microsoft .NET Framework 4 Extended (KB2600217) (Version: 1)
WhoCrashed 4.01
WinRAR 4.20 (64-bit) (Version: 4.20.0)

========================= Memory info: ===================================

Percentage of memory in use: 53%
Total physical RAM: 2046.55 MB
Available physical RAM: 953.6 MB
Total Pagefile: 4093.11 MB
Available Pagefile: 2713.19 MB
Total Virtual: 4095.88 MB
Available Virtual: 3978.92 MB

========================= Partitions: =====================================

1 Drive c: () (Fixed) (Total:931.41 GB) (Free:876.97 GB) NTFS

========================= Users: ========================================

User accounts for \\COMPUTERNAME

Administrator            Username                     Guest                    


**** End of log ****

 

thanks :)


Edited by laceyGB, 25 April 2013 - 04:38 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users