AMD Asrock 890gx Extreme 3 Issue

[shenlong]

Keep getting BSOD if I shut down the system for the day, switched on the next day. Always get STOP 0x0000000E error and then restart a few times, can go into Windows. Strange. Subsequent reboot does not cause this problem.

Is Windows 7 . . .
- x64 MSDN version
- New hardware and New system

I suspect is the Linksys Wireless G USB network adapter. Need help in verifying.

 

[usasma]

There are between 45 and 60 hotfixes available for Windows 7. Your systeminfo report only shows 10 installed. Please visit Windows Update immediately and get the rest of the updates.

Wireless USB adapters have a lot of issues with Win7, particularly if Vista drivers are used. I recommend a wifi card that installs on your motherboard as they are more powerful and more reliable than the USB devices.

Unfortunately, the Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following (this will not affect the analysis of the current files - but it may help later files that are acquired):
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds (if this is the case we may never find a fix)

Will post back after the dump files finish running....

 

[usasma]

Only one of the memory dumps points directly at the wireless adapter.

The next time that you shut down for the night, please remove the software/drivers for the adapter, then remove the device from the computer.
Then shutdown.
When you reboot in the morning, see if it causes a BSOD. If it does, then there's an issue other than the wireless USB device.

 

[shenlong]

hi usasma,

Thanx for the quick reply. I've done all the recommended updates. Apparently, I'm using sp1 beta, so maybe that's why no debug symbols? This sucks. Thought sp1 may fix lots of things.

Anyways, I'm using this Linksys USB adapter:
Linksys 802.11G Speedbooster USB Wireless Network Adapter

which at the following link stated:
Windows 7 Compatibility for Linksys 802.11G Speedbooster USB Wireless Network Adapter: Linksys. Drivers, Updates, Downloads

to be compatible. And upon Windows Update, the latest driver has been patched. I'll try unplugging this modem to see whether the issue happens.

Any chances there's memory/RAM incompatibility? Cos this is a new rig and if it is can RMA asap. I've run the Windows Memory Diagnostics Tool and no errors so far.

 

[usasma]

Sorry, I forgot to post the BSOD summary. It's included at the end of this post....

I didn't notice the SP1 beta tag in the dump files - that's most likely the cause of the symbol problems (you have one dump without it, and that one can find the symbols. No need to try and fix this as SP1 will probably go gold (be released) before we can find the appropriate symbols.

beta software can cause all sorts of issues - but don't remove it just yet. Let's leave that for the last thing we attempt.

I asked about the Compatibility website on my last trip to Microsoft. I was told that the manufacturer's submit the information for their models and that Microsoft doesn't take responsibility for the accuracy.

Then take a look at the FAQ's (lower right) on this page: Linksys by Cisco - WUSB54GS Support Note all the issues with Windows 7 that are listed - that makes me question it's compatibility. We have seen numerous issues on these forums with Wireless USB adapters and Windows 7 - particularly those that don't have Win7 drivers and use Vista drivers (and that's why I recommend the plug-in cards over the USB device).

Try these free hardware diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Also, run this free stress test in "Blend" mode to see if it spits out errors (do it without the USB device). Blen mode stresses the RAM the most (but still stresses other components):

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.

BSOD BUGCHECK SUMMARY

[font=lucida console]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.16562.amd64fre.win7sp1_beta.100603-1800
Debug session time: Tue Sep 21 08:04:13.665 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:05.241
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+a5a91 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
Bugcheck code 0000000A
Arguments fffffa73`ffffffd8 00000000`00000002 00000000`00000001 fffff800`02af5a91
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.16562.amd64fre.win7sp1_beta.100603-1800
Debug session time: Sun Sep 19 05:09:14.264 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:12.450
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+a9667 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
Bugcheck code 0000000A
Arguments 00000000`00000038 00000000`00000002 00000000`00000000 fffff800`02ab2667
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.16562.amd64fre.win7sp1_beta.100603-1800
Debug session time: Sat Sep 18 22:19:59.098 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:07.425
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+87140 )
BUGCHECK_STR:  0x1a_411
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 0000001A
Arguments 00000000`00000411 fffff6fc`4000a258 00000000`8e300860 fffff6fc`0000a259
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.16562.amd64fre.win7sp1_beta.100603-1800
Debug session time: Fri Sep 17 21:40:58.490 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:07.144
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+87140 )
BUGCHECK_STR:  0x1a_411
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 0000001A
Arguments 00000000`00000411 fffff6fc`4000bf18 00000000`93a00860 fffff6fc`0000bf19
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.16562.amd64fre.win7sp1_beta.100603-1800
Debug session time: Fri Sep 17 10:52:29.102 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:06.304
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+87140 )
BUGCHECK_STR:  0x1a_411
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 0000001A
Arguments 00000000`00000411 fffff6fc`40007b70 00000000`035c8860 fffff6fc`00007b71
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.16562.amd64fre.win7sp1_beta.100603-1800
Debug session time: Thu Sep 16 20:19:56.410 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:17.737
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+9b19b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
Bugcheck code 0000000A
Arguments fffff6fc`0002a9c8 00000000`00000002 00000000`00000000 fffff800`02aa819b
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.16562.amd64fre.win7sp1_beta.100603-1800
Debug session time: Mon Sep 13 08:24:39.478 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:04.804
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+87140 )
BUGCHECK_STR:  0x1a_411
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 0000001A
Arguments 00000000`00000411 fffff6fc`4000be68 00000000`93a00860 fffff6fc`0000be69
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.16562.amd64fre.win7sp1_beta.100603-1800
Debug session time: Sun Sep 12 19:37:14.300 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:08.658
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck FC, {fffff88002eeeca0, 8000000097a85963, fffff88002eee9a0, 2}
Probably caused by : ntoskrnl.exe ( nt+87140 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFC
Bugcheck code 000000FC
Arguments fffff880`02eeeca0 80000000`97a85963 fffff880`02eee9a0 00000000`00000002
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.16562.amd64fre.win7sp1_beta.100603-1800
Debug session time: Sun Sep 12 06:31:37.202 2010 (UTC - 4:00)
System Uptime: 0 days 3:59:24.576
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck D1, {3e40, 2, 0, fffff88009cac6a1}
*** WARNING: Unable to verify timestamp for AGUx64.sys
*** ERROR: Module load completed but symbols could not be loaded for AGUx64.sys
Probably caused by : AGUx64.sys ( AGUx64+a26a1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00003e40 00000000`00000002 00000000`00000000 fffff880`09cac6a1
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Sep 11 20:30:30.880 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:08.222
Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e )
BUGCHECK_STR:  0x1a_1236
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001A
Arguments 00000000`00001236 fffffa80`0424ac50 fffffa80`0424ac88 00000000`0010be02
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/font]

 

[shenlong]

Hi usasma,

FYI, AGUx64.sys is the Dlink DWL-G132 wireless USB adapter that gives me crashes as I installed the Vista drivers. I got crashes if I did a file transfer via server. I've since removed it since 14 September.

There shouldn't be any Vista Driver as it is a vanilla fresh x64 OS with no other additional peripherals. Anyways to find out what Vista Driver is being targeted from the latest log file? Thanks.

Oh...I attached the latest log. Today , it first says Memory Management problem 0x0000001a. Then say the IRQ Driver problem. Saying compromise of Driver. Keeps on BSOD on loading. I relaise if it BSOD, you have to select Repair Option. If it loads successfully and load the system, I juz have to press reset button and it's OK! Never BSOD when in Windows. Only initial launching of OS first time during the day.

Meantime... running the diagnosis... so far no problems!