A few crashes with Windows 8

DCeric · Sep 22, 2013

I've had the M4N98TD EVO board for quite sometime and had some minor issues related to Windows 8 and of course some ram issues which I believe was caused by not being setup properly but have since been resolve I believe. But after switching to a new board the Sabertooth 990fx I had tons of issues. I wanted to confirm it wasn't cause of the Sabertooth 990fx so I went back to the M4N98TD EVO and I am still receiving issues. Not quite sure what they are related to but tons of people have stated ram, hard drive or drivers issues.

On the Sabertooth 990fx I was running Windows 8.1 Pro Preview x64 on the M4N98TD EVO I am running Windows 8 Pro x64. I've had quite a few crashes and I don't understand what could be causing them but I'm hoping you can help me.

I have done tons of tests using Prime 95, Western Digital Hard Drive diagnostics, GPU Stress Testing, and Memory Testing. All in which have passed and I receive no crashes at all the crashes actually happen at a non expected time after running with no problems.

I am running:
Motherboard: ASUS M4N98TD EVO
Operating System: Windows 8 Pro 64-bit
Processor: AMD Phenom(tm) II X6 1090T Processor
Memory: Corsair Vengeance 16384MB RAM 1600mhz
Video Card: NVIDIA GeForce GTX 480 x2 SLI Geforce Drivers 327.23

usasma · Sep 23, 2013

Your BIOS dates from 2011. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.

You have 3 hard drives. What is the make/model/wattage and age of your Power Supply?

This device has issues in Device Manager:

USB2.0 VIDBOX NW03 USB\VID_EB1A&PID_5006&MI_00\6&1C095BE3&1&0000 52

Please uninstall the software for this device and physically remove the device from your system.

Out of 5 memory dumps there were 3 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

You can get a head start on the hardware diagnostics if you'd like - they are located here: Hardware Diagnostics

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

nvmf6264.sys Thu Mar 4 20:04:39 2010 (4B9058A7)
nVidia nForce network driver
http://www.carrona.org/drivers/driver.php?id=nvmf6264.sys

nvsmu.sys Mon Mar 22 21:29:19 2010 (4BA8196F)
nVidia nForce System Management Controller (nVidia nForce chipset driver)
http://www.carrona.org/drivers/driver.php?id=nvsmu.sys

lvrs64.sys Fri Aug 19 05:25:38 2011 (4E4E2C12)
Logitech Camera driver
http://www.carrona.org/drivers/driver.php?id=lvrs64.sys

lvuvc64.sys Fri Aug 19 05:26:11 2011 (4E4E2C33)
Logitech USB Video Class Driver (WebCam)
http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys

If all of this doesn't stop the BSOD's, please run these free hardware diagnostics: Hardware Diagnostics. Let us know the results and we can move on from there.

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Sun Sep 22 15:26:10.751 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\092213-41390-01.dmp]
Windows 8 Kernel Version 9200 MP (6 procs) Free x64
Built by: [B]9200[/B].16628.amd64fre.win8_gdr.130531-1504
System Uptime:[B]0 days 15:52:01.827[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+8e08d1 )[/B]
BugCheck [B]50, {ffffcc801076a488, 1, fffff88004f4c8d1, 2}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000050]PAGE_FAULT_IN_NONPAGED_AREA (50)[/url]
Arguments: 
Arg1: ffffcc801076a488, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88004f4c8d1, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID: [B]AV_nvlddmkm+8e08d1[/B]
  BIOS Version                  1301   
  BIOS Release Date             04/14/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Sep 16 10:01:23.387 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\091613-24687-01.dmp]
Windows 8 Kernel Version 9200 MP (6 procs) Free x64
Built by: [B]9200[/B].16581.amd64fre.win8_gdr.130410-1505
System Uptime:[B]1 days 8:05:30.242[/B]
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]109, {a3a039d8aa48b6d5, b3b7465efcc79ce5, fffff88001763b88, 1}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000109]CRITICAL_STRUCTURE_CORRUPTION (109)[/url]
Arguments: 
Arg1: a3a039d8aa48b6d5, Reserved
Arg2: b3b7465efcc79ce5, Reserved
Arg3: fffff88001763b88, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]MEMORY_CORRUPTION_ONE_BIT[/B]
  BIOS Version                  1301   
  BIOS Release Date             04/14/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Sep 14 23:53:36.157 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\091413-18408-01.dmp]
Windows 8 Kernel Version 9200 MP (6 procs) Free x64
Built by: [B]9200[/B].16384.amd64fre.win8_rtm.120725-1247
System Uptime:[B]0 days 0:00:07.889[/B]
Probably caused by :[B]AuthenticAMD[/B]
BugCheck [B]124, {0, fffffa800edd8798, 0, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000124]WHEA_UNCORRECTABLE_ERROR (124)[/url]
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800edd8798, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x124_AuthenticAMD__UNKNOWN_PRV[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Sep 14 23:13:07.586 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\091413-20233-01.dmp]
Windows 8 Kernel Version 9200 MP (6 procs) Free x64
Built by: [B]9200[/B].16384.amd64fre.win8_rtm.120725-1247
System Uptime:[B]0 days 0:00:08.294[/B]
Probably caused by :[B]AuthenticAMD[/B]
BugCheck [B]124, {0, fffffa800f09c038, 0, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000124]WHEA_UNCORRECTABLE_ERROR (124)[/url]
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800f09c038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x124_AuthenticAMD__UNKNOWN_PRV[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Sep 14 18:20:14.562 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\091413-28828-01.dmp]
Windows 8 Kernel Version 9200 MP (6 procs) Free x64
Built by: [B]9200[/B].16384.amd64fre.win8_rtm.120725-1247
System Uptime:[B]0 days 6:18:18.968[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]win32k.sys ( win32k+327524 )[/B]
BugCheck [B]109, {a3a039d8a4ecc563, b3b7465ef76c8170, fffff9600042b524, c}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000109]CRITICAL_STRUCTURE_CORRUPTION (109)[/url]
Arguments: 
Arg1: a3a039d8a4ecc563, Reserved
Arg2: b3b7465ef76c8170, Reserved
Arg3: fffff9600042b524, Failure type dependent information
Arg4: 000000000000000c, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: [B]0x109_c_win32k+327524[/B]
  BIOS Version                  1301   
  BIOS Release Date             04/14/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Sun Sep 22 15:26:10.751 2013 (UTC - 4:00)**************************
[COLOR=RED][B]nvmf6264.sys                Thu Mar  4 20:04:39 2010 (4B9058A7)[/B][/COLOR]
[COLOR=RED][B]nvsmu.sys                   Mon Mar 22 21:29:19 2010 (4BA8196F)[/B][/COLOR]
[COLOR=RED][B]lvrs64.sys                  Fri Aug 19 05:25:38 2011 (4E4E2C12)[/B][/COLOR]
[COLOR=RED][B]lvuvc64.sys                 Fri Aug 19 05:26:11 2011 (4E4E2C33)[/B][/COLOR]
xusb22.sys                  Wed Jul 25 22:26:57 2012 (5010AAF1)
viahduaa.sys                Mon Oct 22 04:11:15 2012 (5084FFA3)
ASACPI.sys                  Thu Nov  1 21:54:34 2012 (509327DA)
nvhda64v.sys                Sun Jun 16 08:38:07 2013 (51BDB1AF)
nvvad64v.sys                Tue Aug 20 07:29:10 2013 (52135306)
nvlddmkm.sys                Thu Sep 12 01:16:00 2013 (52314E10)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Sep 16 10:01:23.387 2013 (UTC - 4:00)**************************
nvhda64v.sys                Mon Feb 25 00:27:35 2013 (512AF647)
hcw72ADFilter.sys           Fri Mar 29 13:02:50 2013 (5155C93A)
hcw72ATV.sys                Fri Mar 29 13:04:11 2013 (5155C98B)
hcw72DTV.sys                Fri Mar 29 13:06:03 2013 (5155C9FB)
nvlddmkm.sys                Fri Jun 21 05:06:16 2013 (51C41788)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Sep 14 18:20:14.562 2013 (UTC - 4:00)**************************
nvmf6264.sys                Wed Apr 20 18:49:36 2011 (4DAF6300)
[/font]

DCeric · Sep 23, 2013

Thanks for your help yeah the issues actually might be do to a failing hard drive however I'm still working on figuring that out and will be updating drivers as well.

The power supply is a Cooler Master Silent Pro M 1000w its from 2010 it was given to me as a gift.

I believe the reason why you are seeing errors for the USB2.0 VIDBOX is cause I haven't installed a driver for that yet.

These issue I guess could be do to malware or that all mighty rootkits which I deeply hate.

DCeric · Sep 23, 2013

I'm also having issues with the web browser and some software crashing.

usasma · Sep 24, 2013

Remove the USB 2.0 VidBox from the system for now. Feel free to reinstall it using the latest, Win8 compatible drivers once the system has been stabilized.

I would strongly suspect that the outdated chipset drivers (the drivers starting with nv.... and date from 2010) aren't fully compatible with Win8. Asus doesn't offer Win8 drivers, so that contributes to my suspicion that the board doesn't support Win8

There's no harm in trying the diagnostics (to include malware scans) - and I've made a list of free one's here: Hardware Diagnostics

Good Luck!

DCeric · Sep 24, 2013

Thanks yeah it could be related to the chipset drivers things are running pretty stabled right now. This is a full reinstall of Windows 8 I'm using now. Only had one issue and that was cause Skype crashed that could be related to some Netframework updates that needed to get installed. Will try the hardware diagnostics next.

DCeric · Sep 25, 2013

I've done those hardware diagnostics already and still can't seem to find the issue. However I got this in my events log:

LiveComm (3340) C:\Users\Eric\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\cff1cc1d7e3d57fe\120712-0049\: A request to read from the file "C:\Users\Eric\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\cff1cc1d7e3d57fe\120712-0049\DBStore\livecomm.edb" at offset 1802240 (0x00000000001b8000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

I have nothing connected to the USB other then my mouse what could be faulty my video cards I freakin hope not.

usasma · Sep 25, 2013

If you have finished ALL of the hardware diagnostics, then the next step is this: Hardware Stripdown Troubleshooting

DCeric · Sep 26, 2013

Well something is telling me its the video card seen as how I had no crash up to installing Direct X and the Nvidia Drivers.

usasma · Sep 27, 2013

The the solution is to try another video card. If you don't have one to test with, I'd suggest purchasing one from a store that will let you return it if it's not needed.

DCeric · Sep 27, 2013

Yeah now i know where the problem is and I believe it is chipset. Funny thing is I never ran into any problems using Windows 8 on this board. All my problems happened when moving my hardware to the Sabertooth 990fx. The only reason why I ran back to this board well cause it was stable and actually running without any problems. I have done memory tests and tested my video cards and none show any issues. Hard Drives tested as well and no issues I'm actually thinking about going back to the Sabertooth 990fx to see if the errors actually on this board (M4N98TD EVO).

Anyways I received another crash I wasn't around to see what and how this crash happened but I looked in the event logs to see what exactly happened around that time.

Event log error 1:

A fatal hardware error has occurred.

Component: AMD Northbridge
Error Source: Machine Check Exception
Error Type: HyperTransport Watchdog Timeout Error
Processor APIC ID: 0

The details view of this entry contains further information.

Event log error 2: (this happened about 7 times)

LiveComm (1084) C:\Users\Eric\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\cff1cc1d7e3d57fe\120712-0049\: A request to read from the file "C:\Users\Eric\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\cff1cc1d7e3d57fe\120712-0049\DBStore\livecomm.edb" at offset 7421952 (0x0000000000714000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (44 seconds) to be serviced by the OS. In addition, 11 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 98 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Event log error 3: (this happens off and on)

Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.

DETAIL -
1 user registry handles leaked from \Registry\User\S-1-5-21-376105738-41304089-3885646014-1002:
Process 1284 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-376105738-41304089-3885646014-1002\Software\Microsoft\Windows\CurrentVersion\Uninstall

usasma · Sep 28, 2013

The Machine Check Exception error is an error that the CPU finds. It doesn't mean that the CPU is bad, but most times it means that there's either a low-level driver or a hardware problem (which includes compatibility).

The LiveComm error points at hardware (could be compatibility) also.
The registry error may or may not be significant here. I don't think that we'll gain anything by hunting down the faulting program(s) - and even that could be due to problems with compatibility.

Unfortunately, diagnosing compatibility issues is (IME) a matter of frustration level. By this I mean the random-seeming errors keep increasing your frustration level as does your repeated attempts to fix each and every one of the problems. Finally, after a lot of hard work and sweat you end up replacing the suspect parts out of desperation - and then, miraculously, your problems go away (not always - but that's been my experience)! It's probably a function of both your tolerance for frustration, and your troubleshooting of the assorted problems.

Good luck!

A few crashes with Windows 8

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer