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

CI.dll Problem.... Please help me solve it!


  • Please log in to reply
20 replies to this topic

#1 Anders.lsantos

Anders.lsantos

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:02:23 PM

Posted 12 June 2013 - 08:22 AM

Hello guys, I was simply using my computer when it suddenly crashed and the BSOD appeared. It showed the error message that the CI.dll was at fault. The problem is that I've done everything that I could to solve this problem to no avail!!

I even tried formatting my hard drive and the problem persisted. I've re-installed windows 7 lots of times now, and no matter what I do the problem comes back.

The only hint I have why the problem is occuring is that almost everytime I install any kind of drivers and have to restart windows I get the BSOD or even if I use the computer for a long period of time, let's say... 10 hours.

I hope you guys can help me solving this annoying problem.

 

Thank you.


Edited by hamluis, 13 June 2013 - 02:32 PM.
Moved from Win 7 to Internal Hardware - Hamluis.


BC AdBot (Login to Remove)

 


#2 Sirawit

Sirawit

    Bleepin' Brony


  • Malware Response Team
  • 4,161 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Thailand
  • Local time:05:23 AM

Posted 12 June 2013 - 08:58 AM

CI.dll is a Code Integrity Modules. Of course this is a critical file. Read more here : http://www.dll-files.com/dllindex/dll-files.shtml?ci

 

Before you reinstall windows,did you format the partition? If you not do that, the OS will always crash by files corrupt in Windows directory.

 

But, after some searching, some people said that this file isn't the real problem,but the virus in Master Boot Record is a real problem.  Read more here : http://answers.microsoft.com/en-us/windows/forum/windows_7-system/boot-critical-file-ccidll-is-corrupt/2c1cf7a6-db71-e011-8dfc-68b599b31bf5


Edited by Sirawit, 12 June 2013 - 09:02 AM.

If I don't reply back to you in 2 days, feel free to send me a PM.

 

“You’re lying… just like you were lying to me before. You have to hate me. I’ve been the worst daughter in the world… you should hate me.”

“But I don’t, Nyx. Because, Nyx, I’m your mother, and a mother will always love her daughter, no matter what.” -Past sins by Pen stroke.


#3 hamluis

hamluis

    Moderator


  • Moderator
  • 56,090 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:23 PM

Posted 12 June 2013 - 12:29 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 Go and paste the content into your next post.

 

Also...please Publish a Snapshot using Speccy - http://www.bleepingcomputer.com/forums/topic323892.html/page__p__1797792#entry1797792 , taking care to post the link.

 

Louis



#4 Anders.lsantos

Anders.lsantos
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:02:23 PM

Posted 12 June 2013 - 07:49 PM

Here's Minitoolbox result plus Speccy.

 

MiniToolBox by Farbar  Version:21-04-2013
Ran by Anders (administrator) on 12-06-2013 at 21:38:31
Running from "C:\Users\Anders\Downloads"
Windows 7 Ultimate Service Pack 1 (X64)
Boot Mode:
***************************************************************************

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

Application errors:
==================
Error: (06/12/2013 11:25:19 AM) (Source: Software Protection Platform Service) (User: )
Description: The Software Protection service failed to start. 0x80070002
6.1.7601.17514

Error: (06/12/2013 11:24:50 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (06/12/2013 10:08:15 AM) (Source: Software Protection Platform Service) (User: )
Description: The Software Protection service failed to start. 0x80070002
6.1.7601.17514

Error: (06/12/2013 10:07:48 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (06/12/2013 10:07:10 AM) (Source: Software Protection Platform Service) (User: )
Description: The Software Protection service failed to start. 0x80070002
6.1.7601.17514

Error: (06/12/2013 07:08:15 AM) (Source: MsiInstaller) (User: NVIDIACOMPUTER)
Description: Product: NetSpeedMonitor 2.5.4.0 x86 -- This install package only supports 32-bit operating systems.

Error: (06/11/2013 08:43:44 PM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

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

Error: (06/11/2013 07:46:59 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (06/11/2013 07:45:44 AM) (Source: Application Error) (User: )
Description: Faulting application name: mbamgui.exe, version: 1.70.0.0, time stamp: 0x512fc066
Faulting module name: mbamgui.exe, version: 1.70.0.0, time stamp: 0x512fc066
Exception code: 0x40000015
Fault offset: 0x0003b525
Faulting process id: 0x6dc
Faulting application start time: 0xmbamgui.exe0
Faulting application path: mbamgui.exe1
Faulting module path: mbamgui.exe2
Report Id: mbamgui.exe3


System errors:
=============
Error: (06/12/2013 11:25:19 AM) (Source: Service Control Manager) (User: )
Description: The Software Protection service terminated with the following error:
%%2

Error: (06/12/2013 11:23:18 AM) (Source: Service Control Manager) (User: )
Description: The following boot-start or system-start driver(s) failed to load:
spldr

Error: (06/12/2013 11:23:05 AM) (Source: Service Control Manager) (User: )
Description: The Link-Layer Topology Discovery Responder service failed to start due to the following error:
%%646

Error: (06/12/2013 11:23:05 AM) (Source: Service Control Manager) (User: )
Description: The Link-Layer Topology Discovery Mapper I/O Driver service failed to start due to the following error:
%%646

Error: (06/12/2013 11:23:03 AM) (Source: EventLog) (User: )
Description: The previous system shutdown at 11:19:55 on ?12/?06/?2013 was unexpected.

Error: (06/12/2013 10:08:15 AM) (Source: Service Control Manager) (User: )
Description: The Software Protection service terminated with the following error:
%%2

Error: (06/12/2013 10:07:11 AM) (Source: Service Control Manager) (User: )
Description: The Software Protection service terminated with the following error:
%%2

Error: (06/12/2013 10:06:14 AM) (Source: Microsoft-Windows-WHEA-Logger) (User: NT AUTHORITY)
Description: A fatal hardware error has occurred.

Component: AMD Northbridge
Error Source: 3
Error Type: 2
Processor ID: 0

The details view of this entry contains further information.

Error: (06/12/2013 10:06:14 AM) (Source: Service Control Manager) (User: )
Description: The following boot-start or system-start driver(s) failed to load:
spldr

Error: (06/12/2013 10:06:07 AM) (Source: Service Control Manager) (User: )
Description: The Link-Layer Topology Discovery Responder service failed to start due to the following error:
%%646


Microsoft Office Sessions:
=========================
Error: (06/12/2013 11:25:19 AM) (Source: Software Protection Platform Service)(User: )
Description: 0x800700026.1.7601.17514

Error: (06/12/2013 11:24:50 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (06/12/2013 10:08:15 AM) (Source: Software Protection Platform Service)(User: )
Description: 0x800700026.1.7601.17514

Error: (06/12/2013 10:07:48 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (06/12/2013 10:07:10 AM) (Source: Software Protection Platform Service)(User: )
Description: 0x800700026.1.7601.17514

Error: (06/12/2013 07:08:15 AM) (Source: MsiInstaller)(User: NVIDIACOMPUTER)
Description: Product: NetSpeedMonitor 2.5.4.0 x86 -- This install package only supports 32-bit operating systems.(NULL)(NULL)(NULL)(NULL)(NULL)

Error: (06/11/2013 08:43:44 PM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

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

Error: (06/11/2013 07:46:59 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (06/11/2013 07:45:44 AM) (Source: Application Error)(User: )
Description: mbamgui.exe1.70.0.0512fc066mbamgui.exe1.70.0.0512fc066400000150003b5256dc01ce66bab26d68e0C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbamgui.exeC:\Program Files (x86)\Malwarebytes' Anti-Malware\mbamgui.exef9dcaba0-d2ad-11e2-b831-14dae9bc0b59


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

Adobe Flash Player 11 Plugin (Version: 11.7.700.224)
ASIO4ALL (Version: 2.11 Beta2)
DAEMON Tools Lite (Version: 4.47.1.0333)
Malwarebytes Anti-Malware version 1.75.0.1300 (Version: 1.75.0.1300)
Microsoft .NET Framework 4 Client Profile (Version: 4.0.30319)
Microsoft .NET Framework 4 Extended (Version: 4.0.30319)
Mozilla Firefox 21.0 (x86 pt-BR) (Version: 21.0)
Mozilla Maintenance Service (Version: 21.0)
Native Instruments Controller Editor (Version: 1.5.1.1124)
Native Instruments Rig Kontrol 3 (Version: 3.0.0.625)
Native Instruments Service Center (Version: 2.3.2.926)
NVIDIA Control Panel 320.18 (Version: 320.18)
NVIDIA GeForce Experience 1.5 (Version: 1.5)
NVIDIA Graphics Driver 320.18 (Version: 320.18)
NVIDIA Install Application (Version: 2.1002.124.810)
NVIDIA PhysX (Version: 9.12.1031)
NVIDIA PhysX System Software 9.12.1031 (Version: 9.12.1031)
NVIDIA Update 4.11.9 (Version: 4.11.9)
NVIDIA Update Components (Version: 4.11.9)
Skype™ 6.5 (Version: 6.5.158)
WinRAR 4.20 (32-bit) (Version: 4.20.0)

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

Percentage of memory in use: 28%
Total physical RAM: 4095.23 MB
Available physical RAM: 2923.2 MB
Total Pagefile: 8188.64 MB
Available Pagefile: 6859.23 MB
Total Virtual: 4095.88 MB
Available Virtual: 3987.12 MB

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

1 Drive c: () (Fixed) (Total:49.9 GB) (Free:28.76 GB) NTFS
2 Drive d: (Files) (Fixed) (Total:415.76 GB) (Free:369.21 GB) NTFS

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

User accounts for \\NVIDIACOMPUTER

Administrator            Anders                   Guest                    
UpdatusUser              


**** End of log ****
 

 

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

 

I forgot to mention in my last post that I've already formatted the partition and tried fixing mbr.

 

Thanks for the help!



#5 hamluis

hamluis

    Moderator


  • Moderator
  • 56,090 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:23 PM

Posted 13 June 2013 - 09:58 AM

Thanks :).

 

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html .

 

Double-click BlueScreenView.exe file.

 

When autoscan is done (screen comes up), click Edit/Select All...then File/Save Selected Items.

 

Save the report as BSOD.txt.

 

Open BSOD.txt in Notepad, copy all content and paste it into your next reply.

 

Louis



#6 Anders.lsantos

Anders.lsantos
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:02:23 PM

Posted 13 June 2013 - 10:30 AM

Hello again, here's the log you asked me.

 

==================================================
Dump File         : 061213-17799-01.dmp
Crash Time        : 12/06/2013 10:05:53
Bug Check String  :
Bug Check Code    : 0x00000124
Parameter 1       : 00000000`00000000
Parameter 2       : fffffa80`04c0f8f8
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4af34c
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.22280 (win7sp1_ldr.130318-1534)
Processor         : x64
Crash Address     : ntoskrnl.exe+4af34c
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\061213-17799-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 262.144
Dump File Time    : 12/06/2013 10:06:05
==================================================

==================================================
Dump File         : 061013-32495-01.dmp
Crash Time        : 10/06/2013 01:26:20
Bug Check String  : DRIVER_VERIFIER_DETECTED_VIOLATION
Bug Check Code    : 0x000000c4
Parameter 1       : 00000000`00000091
Parameter 2       : 00000000`00000000
Parameter 3       : fffffa80`0621f060
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+72680
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.22280 (win7sp1_ldr.130318-1534)
Processor         : x64
Crash Address     : ntoskrnl.exe+72680
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\061013-32495-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 262.144
Dump File Time    : 10/06/2013 01:27:39
==================================================

==================================================
Dump File         : 061013-23493-01.dmp
Crash Time        : 10/06/2013 00:41:45
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : 00000000`031a89e8
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000000
Parameter 4       : fffff880`0164cd29
Caused By Driver  : tcpip.sys
Caused By Address : tcpip.sys+4bd29
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+72680
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\061013-23493-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 270.928
Dump File Time    : 10/06/2013 00:44:37
==================================================
 

I'm running windows on directory services restore mode.



#7 hamluis

hamluis

    Moderator


  • Moderator
  • 56,090 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:23 PM

Posted 13 June 2013 - 11:32 AM

Error: (06/12/2013 10:06:14 AM) (Source: Microsoft-Windows-WHEA-Logger) (User: NT AUTHORITY)
Description: A fatal hardware error has occurred.

Component: AMD Northbridge
Error Source: 3
Error Type: 2
Processor ID: 0

The details view of this entry contains further information
.

 

Please...go to Event Viewer...look up this error, go to Details View and post whatever is revealed as detailed data.

 

Louis

 

 



#8 Anders.lsantos

Anders.lsantos
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:02:23 PM

Posted 13 June 2013 - 11:44 AM

Here's the detailed information about the error:

 

- System
    - Provider
      [ Name] Microsoft-Windows-WHEA-Logger       [ Guid] {C26C4F3C-3F66-4E99-8F8A-39405CFED220}
      EventID 20       Version 0       Level 2       Task 0       Opcode 0       Keywords 0x8000000000000000     - TimeCreated
      [ SystemTime] 2013-06-12T18:06:14.865600000Z
      EventRecordID 4203     - Correlation
      [ ActivityID] {904CE255-7F38-4D87-B897-EA1DF4876191}
    - Execution
      [ ProcessID] 1352       [ ThreadID] 1416
      Channel System       Computer NvidiaComputer     - Security
      [ UserID] S-1-5-19
- EventData
    ErrorSource 3     ApicId 0     MCABank 4     MciStat 0xa200001000020c0f     MciAddr 0x0     MciMisc 0x0     ErrorType 2     Length 928     RawData 435045521002FFFFFFFF03000100000002000000A0030000350512000C060D140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BB21B44D789767CE0102000000000000000000000000000000000000000000000058010000C00000000102000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000080100000102000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002040000030000430F10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000000000000000000430F10000008040009208000FFFB8B170000000000000000000000000000000000000000000000000000000000000000B3F8F31CB1C5A249AA595EEF92FFA63C01000000000000009E07C0860600000000000000000000000000000000000000000000000000000000000000000000000100000002000000A0787F7A9767CE010000000000000000000000000000000000000000040000000F0C0200100000A2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000


#9 hamluis

hamluis

    Moderator


  • Moderator
  • 56,090 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:23 PM

Posted 13 June 2013 - 02:32 PM

Well...I've sees some very wild guesses as to what this might be...but I would not put any faith in any of them.

 

Taking the error message at face value...there is a hardware problem that seems to point to the chipset.  Now...I can't say it's not a motherboard problem, but I cannot say that it is.

 

I literally have no idea whether it's truly a hardware problem, other than the fact that formatting/reinstalling doesn't seem to eliminate it.

 

Moving topic to Internal Hardware for other opinions/ideas.

 

Louis



#10 Anders.lsantos

Anders.lsantos
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:02:23 PM

Posted 13 June 2013 - 07:43 PM

But the thing is... I only get this error when trying to use Windows 7. Before this I was using Windows 8 and XP normally. My guess is that if it was a hardware problem it would happen the same with different Windows systems right? I even tried installing windows from another media, but I still get the same error. Windows 8 or XP works just fine.



#11 hamluis

hamluis

    Moderator


  • Moderator
  • 56,090 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:23 PM

Posted 14 June 2013 - 02:23 PM

Are you saying that you have a multiboot right now?  You have Win 8 and/or XP installed right now?

 

Windows, not me, says it's a hardware problem, see the error message.  I have no clue to what it is, but I believe that Windows is more capabable of pointing you in the right direction...than I am right now :).

 

If you multiboot...and you only experience issue in a given O/S...chances are that it's an O/S, file system, or partition problem...but it could still be a hardware problem since motherboard problems, PSU problems can be intermitten at some stage.

 

Louis


Edited by hamluis, 14 June 2013 - 02:28 PM.


#12 Anders.lsantos

Anders.lsantos
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:02:23 PM

Posted 14 June 2013 - 07:36 PM

No, I don't have a multiboot right now, Windows 7 is installed alone. What I'm saying is that I had Windows 8 previously installed and everything was fine, but due to compatibility issues I decided to change to windows 7.

I already tried a clean install and it didn't solve the problem. Then I tried installing XP after and it ran just as normal.

That's why I think it can only be a Windows 7 problem.


Edited by Anders.lsantos, 14 June 2013 - 07:37 PM.


#13 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:03:53 AM

Posted 15 June 2013 - 06:46 AM

Hi

 

Asus M4N68T-M LE is a Windows 7 certified motherboard so compatibility is not the issue here. Blue screen view simply blames legit Windows files and hence not useful. Analyzing the dumps may be helpful to identify the real cause. Can you please upload the dump files to a free file hosting site ?. Just zip the C:\Windows\minidump folder and upload it to either Mediafire or Box.com.

 

 

 http://www.mediafire.com/

 

 https://www.box.com/



#14 Anders.lsantos

Anders.lsantos
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:02:23 PM

Posted 15 June 2013 - 11:38 PM

Hello Anshad, here are the dump files you asked. Thanks for your help.

 

http://www.mediafire.com/?0g18y5475c3sq1j



#15 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:03:53 AM

Posted 16 June 2013 - 05:02 AM

Hi

 

Out of the 4 dumps you posted , 2 of the shows STOP code 0x124 WHEA_UNCORRECTABLE_ERROR  which is a hardware related error code. One of the other dump is a Driver Verfier enabled one which blames legit Microsoft files as the cause. It also indicates in the direction of a  possible hardware fault.

 

Please follow the below steps.

 

1 ) Update all the drivers to the latest version available.

 

 Download chipset and audio drivers from Asus site.

 

 http://support.asus.com/download.aspx?SLanguage=en&m=M4N68T-M%20LE&p=1&s=24&os=30&hashedid=viXEi1RXKBFzjFt9

 

Download video driver from Nvidia site.

 

http://www.nvidia.in/Download/index.aspx?lang=en-in

 

 

2 ) Verify that the RAM used is compatible with your motherboard.

 

  On the Asus driver download page, you can find the Qualified Vendor list. Verify that the memory module is fully compatible.

 

3 ) Re-seat all components.

 

     Connectivity problems can often produce Machine Check Exceptions (MSE ) . Remove and reconnect all parts especially CPU and RAM. Precuations should be taken to avoid static electricity damage when disassembling. Here is an excellent guide on how to properly disassemble the components.

 

 
 
If the issue remains, we have to run stress tests on each individual components.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users