Computer started having BSOD's (Windows Ultimate x64)

Wrench97 · Aug 2, 2013

It's going to be hard to say, 1600 is not one of the pre-set Jdec or XMP settings for those sticks. It may work or it may not.

Bodies · Aug 2, 2013

Yes I installed a lot of windows updates yesterday, one of which was SP1 so that's good. I will update this topic if another bsod happens (computer has ran for 2 days without one so maybe the issue is fixed).
It's fine, I will start doing that myself. :)

Bodies · Aug 2, 2013

Wrench97 said:
It's going to be hard to say, 1600 is not one of the pre-set Jdec or XMP settings for those sticks. It may work or it may not.

So do you think I should change it to 1033mhz, 1600mhz or keep it at Auto?

Wrench97 · Aug 2, 2013

Try it the way it is now if you have any issues switch it to auto.

Bodies · Aug 2, 2013

It is auto right now.

Bodies · Aug 3, 2013

After 3 days of normal daily usage and no problems, the computer BSOD today while I watched a movie on BSPlayer. MEMORY_MANAGEMENT. Interestingly enough, the last time my system bsod (before I formated) was while I was watching a series on BSPlayer too. The video files are located in a disk partition.
I attached dump files for this BSOD.

View attachment Desktop.rar

I've been told to try and remove my cpu oc, I currently have i5 750 @ 3.1Ghz (160 BCLK on bios) with 45ºc idle and 55/60ºc load. Do you guys think it can be the cause of these BSOD's? I've had oc on the cpu for 3 years now, originally it was at 3.7ghz but I lowered it because it is very hot these months where I live right now and I didn't like some high temps I saw sometimes.

Thank you

Wrench97 · Aug 3, 2013

viahduaa.sys Wed Aug 4 03:51:53 2010

Try updating the Via VT2020 audio driver, the Via site shows one a couple months newer(10/1/2010)> VIA Drivers Download - VIA Technologies, Inc.

Also run driver verifier. > https://www.sysnative.com/forums/bs...river-verifier-blue-screen-death-related.html

Code:

2013 Aug 03 11:16:31 AM     98-dbug   Sysnative  BSOD scripts
              …………………………………………………………………………………………………………………………………………………………………………………………………………………………

                         TOTAL DUMP FILES PROCESSED THIS RUN:  1
                         TOTAL DUMP FILES PROCESSED  TO DATE:  318

              …………………………………………………………………………………………………………………………………………………………………………………………………………………………





Debug session time: Sat Aug  3 08:25:59.191 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\080313-22464-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:48:47.596
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3211c )
BugCheck 1A, {403, fffff6800009f500, c100000131b09847, fffff6000009f500}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff6800009f500
Arg3: c100000131b09847
Arg4: fffff6000009f500
BUGCHECK_STR:  0x1a_403
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+3211c
MaxSpeed:     2670
CurrentSpeed: 3052
 
Processor may be overclocked!
Expected Frequency:   2670
Actual Frequency:     3052
Overclock Ratio:      1.14307
 
BiosVersion = 2003   
BiosReleaseDate = 12/14/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``




		***   3rd PARTY DRIVER LIST   *** 
		***   3rd PARTY DRIVER LIST   *** 




ASACPI.sys                  Wed May 13 21:25:17 2009 (4A0B72FD)
IOMap64.sys                 Thu Feb  4 20:55:34 2010 (4B6B7A96)
MpFilter.sys                Fri Jun  7 19:01:11 2013 (51B26637)
Rt64win7.sys                Tue Jun 18 03:52:16 2013 (51C011B0)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
nvhda64v.sys                Tue Jul  3 11:25:04 2012 (4FF30ED0)
nvlddmkm.sys                Thu Aug 30 11:50:16 2012 (503F8BB8)
viahduaa.sys                Wed Aug  4 03:51:53 2010 (4C591C19)






http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
http://www.carrona.org/drivers/driver.php?id=IOMap64.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=viahduaa.sys


   --- E O J ---   2013 Aug 03 11:16:31 AM    _98-dbug   Copyright 2012 Sysnative Forums
   --- E O J ---   2013 Aug 03 11:16:31 AM    _98-dbug   Copyright 2012 Sysnative Forums
   --- E O J ---   2013 Aug 03 11:16:31 AM    _98-dbug   Copyright 2012 Sysnative Forums

Bodies · Aug 3, 2013

I just got another one while I was playing dota. I'll attach the new dumpfiles for this one when I finish installing Windows Updates and that driver you advised me to install.
I also removed the oc from my cpu, making it 133 BCLK value (which is its default).
Also, does Driver Verifier really need to run for 24h? I've never tried that before.

Wrench97 · Aug 3, 2013

It needs to run until it produces a BSOD, 24 hours is usual I've seen it take up to 48.
It's a background process so if it does not catch a driver acting badly on boot it needs to monitor the system while you use it normally until a rouge driver(if there is one) pokes it's head out to get caught.

Bodies · Aug 3, 2013

Alright I have it running. So now I have to wait for a BSOD and then grab the dump file from c:\windows\minidump and upload it here, right?

Wrench97 · Aug 3, 2013

Yes that's the idea.

Bodies · Aug 4, 2013

Hello.
I just had one bluescreen and then when the computer booted into windows, another one. Today afternoon the lights went out in my house for a couple of minutes, I hope it didn't mess up the driver verifier minidump. Anyway I'll attach it to this post and also paste the 2 bluescreens descriptions from WhoCrashed:
[FONT=Segoe UI, Arial]On Mon 05-08-2013 00:16:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-26800-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC5002EAE8, 0x98100001C9408820, 0xFFFFF67C5002EAE9)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.

[/FONT]
[FONT=Segoe UI, Arial]On Mon 05-08-2013 00:16:43 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC5002EAE8, 0x98100001C9408820, 0xFFFFF67C5002EAE9)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
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.

[/FONT]
[FONT=Segoe UI, Arial]On Mon 05-08-2013 00:14:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-19484-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFFA80C2433180, 0x0, 0xFFFFF80002AB8EA5, 0x5)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 that cannot be identified at this time.

I really thought removing the oc did the trick. Damn.
Any thoughts?[/FONT]

Mihran93 · Aug 4, 2013

Bodies said:
Hello.
I just had one bluescreen and then when the computer booted into windows, another one. Today afternoon the lights went out in my house for a couple of minutes, I hope it didn't mess up the driver verifier minidump. Anyway I'll attach it to this post and also paste the 2 bluescreens descriptions from WhoCrashed:
On Mon 05-08-2013 00:16:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-26800-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC5002EAE8, 0x98100001C9408820, 0xFFFFF67C5002EAE9)
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 Mon 05-08-2013 00:16:43 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: 0x1A (0x411, 0xFFFFF6FC5002EAE8, 0x98100001C9408820, 0xFFFFF67C5002EAE9)
Error: MEMORY_MANAGEMENT
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 Mon 05-08-2013 00:14:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-19484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFFA80C2433180, 0x0, 0xFFFFF80002AB8EA5, 0x5)
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 that cannot be identified at this time.

I really thought removing the oc did the trick. Damn.
Any thoughts?

Hi, I'm new here and I am no good in the use of a PC!!

With that being said - I have some problems and I would really appericiate it if you would care to help me.

I got the BSOD today for the first time so I ran a couple of tests with AVG, scanned the whole thing but everything turned out negative.

The messages I recieved on BSOD was..

C:/Windows/Minidump/080513-79437-01.dmp
C:/Users/ejer-expert/AppData/Local/Temp/WER-122078-0.sysdata.xml
C:/Windows/MEMORY.DMP

If you guys don't mind, can you please put it in a nutshell for me because I'm seriously technically illiterate!
Thanks!! :)

Bodies · Aug 4, 2013

Hum hello. I'm not that into the subject so the best thing I can tell you is start a thread on this forum's sub-section and check this url before posting
https://www.sysnative.com/forums/bs...g-instructions-windows-8-7-windows-vista.html
Other than that, BSOD's are the OS system's response to when either some software (drivers mainly) or hardware hits a wall/critical error.
Hope you solve your problem there :)

Wrench97 · Aug 8, 2013

Sorry it took so long I somehow missed your reply.

Verifier enabled naming a windows process is usually a sure sign it's hardware related, the first dump names audiodg.exe seeing that install this MS hotfix and see if it helps> A memory leak issue occurs in the Audiodg.exe process when you play audio on a computer that is running Windows 7, Windows Server 2008 R2, Windows Vista or Windows Server 2008

Code:

2013 Aug 08 15:36:47 PM     98-dbug   Sysnative  BSOD scripts
              …………………………………………………………………………………………………………………………………………………………………………………………………………………………

                         TOTAL DUMP FILES PROCESSED THIS RUN:  2
                         TOTAL DUMP FILES PROCESSED  TO DATE:  323

              …………………………………………………………………………………………………………………………………………………………………………………………………………………………





Debug session time: Sun Aug  4 20:16:43.216 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\080513-26800-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:01:50.184
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6071 )
BugCheck 1A, {411, fffff6fc5002eae8, 98100001c9408820, fffff67c5002eae9}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffff6fc5002eae8
Arg3: 98100001c9408820
Arg4: fffff67c5002eae9
BUGCHECK_STR:  0x1a_411
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID:  X64_0x1a_411_VRF_nt!_??_::FNODOBFM::_string_+6071
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Aug  4 20:14:19.936 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\080513-19484-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 4:41:50.905
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+c73b4 )
BugCheck 50, {fffffa80c2433180, 0, fffff80002ab8ea5, 5}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Bugcheck code 00000050
Arguments: 
Arg1: fffffa80c2433180, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002ab8ea5, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x50_VRF_win32k+c73b4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``




		***   3rd PARTY DRIVER LIST   *** 
		***   3rd PARTY DRIVER LIST   *** 




ASACPI.sys                  Wed May 13 21:25:17 2009 (4A0B72FD)
IOMap64.sys                 Thu Feb  4 20:55:34 2010 (4B6B7A96)
MpFilter.sys                Fri Jun  7 19:01:11 2013 (51B26637)
Rt64win7.sys                Tue Jun 18 03:52:16 2013 (51C011B0)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
nvhda64v.sys                Mon Feb 25 00:27:35 2013 (512AF647)
nvlddmkm.sys                Fri Jun 21 05:06:16 2013 (51C41788)
nvvad64v.sys                Tue May 14 11:27:24 2013 (519257DC)
viahduaa.sys                Wed Aug  4 03:51:53 2010 (4C591C19)






http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
http://www.carrona.org/drivers/driver.php?id=IOMap64.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
nvvad64v.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=viahduaa.sys


   --- E O J ---   2013 Aug 08 15:36:47 PM    _98-dbug   Copyright 2012 Sysnative Forums
   --- E O J ---   2013 Aug 08 15:36:47 PM    _98-dbug   Copyright 2012 Sysnative Forums
   --- E O J ---   2013 Aug 08 15:36:47 PM    _98-dbug   Copyright 2012 Sysnative Forums

Bodies · Aug 9, 2013

Hello.
Apparently, setting bios to default values solved my problem. I have been using my comp without problems for 5 or 6 days now.
I guess the OC my system had wasn't compatible with the new ram I got. Thank you all for the help!
(Let's hope I won't have to update this topic

)

Wrench97 · Aug 9, 2013

Make sure to turn verifier off.

From a Command prompt type verifier /reset then re-boot.

Bodies · Jan 18, 2014

Hey. I was not sure whether to create a new thread or to update this one, so I guess I'll just post here since you can check older reports of my comp and create a new one if it's needed.
So I thought the BSOD's were gone. Oh well. Nothing new has been put in this computer or no new drivers but the problem persists. I have already tried to: fresh install of windows, memtest of separate dim slots, HDD check, updating gpu drivers/using the ones that come in the graphic's card box and putting all bios settings to default.
I'll attach the reports to this post and hopefully you can give me some light on the issue.

Thank you once again

edit: I better give you the answers you mention in the Posting Instructions while I'm at it.
· OS - Windows 7
· x64
· What was original installed OS on system? - The same
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? - Came pre-installed
· Age of system (hardware) - The computer was bought 4 years ago and since then I've updated GPU and RAM.
· Age of OS installation - have you re-installed the OS? - Yes, I formatted the computer 2 days ago.

· CPU - i5 750 @2.67GHz
· Video Card - Nvidia Geforce GTX650 DCT-1GD5
· MotherBoard - Asus P7P55D-PRO
· Power Supply - Corsair TX650W

· System Manufacturer
· Exact model number (if laptop, check label on bottom)

· Laptop or Desktop? Desktop

Wrench97 · Jan 20, 2014

Have you reinstalled Windows?
The 2005 asacpi driver is either still on your system or back since a reinstall.
ASACPI.sys Sun Mar 27 22:30:36 2005

It's either the ATK0110 or if you have the asus ai suite installed it's part of the AI Suite both can be bound here in the driver D/L section under Utilities> Motherboards - P7P55D PRO

Code:

2014 Jan 20 17:59:41 PM     98-dbug   Sysnative  BSOD scripts
              …………………………………………………………………………………………………………………………………………………………………………………………………………………………

                         TOTAL DUMP FILES PROCESSED THIS RUN:  2
                         TOTAL DUMP FILES PROCESSED  TO DATE:  658

              …………………………………………………………………………………………………………………………………………………………………………………………………………………………





Debug session time: Fri Jan 17 12:06:14.446 2014 (UTC - 5:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\011714-21824-01.dmp]
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
System Uptime: 0 days 3:39:08.788
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BugCheck 4E, {99, 10c3c2, 2, 10c3bf}
BugCheck Info: PFN_LIST_CORRUPT (4e)
Bugcheck code 0000004E
Arguments: 
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000010c3c2, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000010c3bf, 0
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
MaxSpeed:     2670
CurrentSpeed: 2675
BiosVersion = 2003   
BiosReleaseDate = 12/14/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Jan 14 10:21:21.245 2014 (UTC - 5:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\011414-20872-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 0:01:25.572
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BugCheck 1A, {41790, fffffa8004090c80, ffff, 0}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8004090c80
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
MaxSpeed:     2670
CurrentSpeed: 2674
BiosVersion = 2003   
BiosReleaseDate = 12/14/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``




		***   3rd PARTY DRIVER LIST   *** 
		***   3rd PARTY DRIVER LIST   *** 




ASACPI.sys                  Sun Mar 27 22:30:36 2005 (42476C4C)
LGBusEnum.sys               Mon Nov 23 20:36:48 2009 (4B0B38B0)
LGSHidFilt.Sys              Thu May 30 11:16:33 2013 (51A76D51)
LGVirHid.sys                Mon Nov 23 20:36:48 2009 (4B0B38B0)
MpFilter.sys                Fri Sep 13 22:17:40 2013 (5233C744)
Rt64win7.sys                Thu Feb 26 04:04:13 2009 (49A65B0D)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
nvhda64v.sys                Thu Nov 28 08:38:09 2013 (52974741)
nvhda64v.sys                Sun Jun 16 08:38:07 2013 (51BDB1AF)
nvlddmkm.sys                Thu Dec 19 12:02:52 2013 (52B326BC)
nvlddmkm.sys                Thu Sep 12 01:16:00 2013 (52314E10)
nvvad64v.sys                Tue Aug 20 07:29:10 2013 (52135306)
viahduaa.sys                Wed Aug  4 03:51:53 2010 (4C591C19)






http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
http://www.carrona.org/drivers/driver.php?id=LGSHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=viahduaa.sys


   --- E O J ---   2014 Jan 20 17:59:41 PM    _98-dbug   Copyright 2012 Sysnative Forums
   --- E O J ---   2014 Jan 20 17:59:41 PM    _98-dbug   Copyright 2012 Sysnative Forums
   --- E O J ---   2014 Jan 20 17:59:41 PM    _98-dbug   Copyright 2012 Sysnative Forums

Bodies · Jan 21, 2014

Hey.
Yea this is a fresh Windows Ultimate x64 install.
I downloaded Asus AI Suite and installed it in order to update the ASACPI.sys/ATK0110 driver and I think it did update it since in Computer Management, under System devices, it says that the driver date is 16-07-2009 and it's version is 1043.6.0.0 (quite an update considering you found it to be from 2005).
Is this all I needed to do?

Thank you once again Wrench :)

Computer started having BSOD's (Windows Ultimate x64)

Administrator, Hardware Expert

Member

Member

Administrator, Hardware Expert

Member

Member

Administrator, Hardware Expert

Member

Administrator, Hardware Expert

Member

Administrator, Hardware Expert

Member

Attachments

New member

Member

Administrator, Hardware Expert

Member

Administrator, Hardware Expert

Member

Attachments

Administrator, Hardware Expert

Member