RE: BSOD Errors With A New ASUS Motherboard?!? Help!

Hello. Replaced my motherboard with the same make and model under a warrranty program with ASUS. The motherboard is the P5Q. I did not have these issues at the last moments of using the original P5Q before sending it to ASUS. I noticed this issue right from the start after connecting the necessary hardware components to get the system running (motherboard, power supply (BFG 800W), processor (Intel Core 2 Quad Q9550), processor heat sink, 1 DVD burner drive (LG brand), and a hard drive (WD Caviar Blue 500GB), graphic card (ATI Radeon 5670), memory (installed 2 sets of Corsair DDR2 XMS2 2 x 2 GB modules or 2 TWIN2X4096-6400C5 for a total of 8 GB), mouse and keyboard). I used the same originally installed Windows 7 SP1 64-bit with the exchanged ASUS P5Q motherboard. I even thought it may be an issue with the Windows 7 64-bit installation with a new motherboard, so I did a clean install with Windows 7 64-bit again -- Still the same issues. The BIOS was flash updated at the ASUS testing to the latest version. I installed the latest motherboard drivers downloaded from the ASUS website.

I notice this issue happens randomly and most of the time when I am "Shutting down..." Windows 7 64-bit. Just after the "Shutting down..." phase ends, the screen for about a split flashes a pixelated screen then the system does completely shut down.

Othertimes and more frequent when I have the system up and running, the system instantly freezes up for approximately 10 seconds. This happens randomly and I would say approximately 1-2 times per every couple of hours. The curser cannot be moved for 10 seconds and then the screen quickly turns black for a few seconds, as it flashes quickly and then the desktop resumes. Following the system freeze, I get a message above the notification area in the bottom right of my screen stating, "Display driver stopped responding and has recovered. Display driver AMD driver stopped responding and has successfully recovered.". Windows 7 Reliability Hardware Error reports it is a "Video hardware error" with the program event name "LiveKernelEvent" with BCCode of 117. I recall for two of the occassions that I was closing a maximized window when the system froze and moving the scroll bar down when it froze. I have used the built in Windows Snipping Tool and have noticed when the screen is being captured, the freezes like above too. I have also noted that response times when clicking on links can take a few seconds that was not mormal before.

Additional notes:

1. No obvious error window messages posted on screen when issues develop except for the graphics card error messages that appear in the noitfication area.

2. I noticed if I enabled Aero in Windows 7, the crashes seemed to happen (randomly a couple of times per hour) more frequent than using Windows 7 Basic visuals.

3. File system issues? Ran sfc /scannow -- no issues at the conclusion of the scan.

4. Possible memory issues? Ran Memtest86+ v.4.20 (latest version, ran for 7 passes for 12 hours 15 minutes) and Windows Memory Diagnostic (from Windows 7 Repair Disc) -- no errors reported.

5. Let me expand on the memory issues. I noticed when I removed 1 of the 2 sets of the memory modules from the motherboard (Having only 4 GB total), after the first system reboot after the partial memory removal I get CHKDSK to run automtically after reboot. I let it run to the conclusion and I see it fixes many errors after finding system files corrupted. However after the fixes, this issue still lingers with 4GB. I restored my memory back to 8 GB.

6. Possible power supply issues? I bought and tested the same hardware with another comparable power supply. I used a A-Power 750 W new power supply thinking the amps and voltages were becoming weaker with my older one ultimately causing power loss. The same issues still presented themselves.

7. Let me expand on the possible power supply issue. I have kept records using the software CPUID HWMonitor. It reports electical and temperatures of key components of the system. I notice with this exchanged ASUS P5Q motherboard that the CPU VCORE voltages and the DRAM voltages are lower than the original ASUS P5Q motherboard when at idle.

Original ASUS P5Q CPU VCORE Range (min./max.): 1.22 V - 1.22 V
Replacement ASUS P5Q CPU VCORE Range (min./max.): 0.94 V - 0.95 V
Original ASUS P5Q DRAM Range (min./max.): 1.46 V- 1.46 V
Replacement ASUS P5Q Range (min./max.): 1.20 V - 1.21 V
Any issues here related to my issue?

8. Possible graphics/video card issue? Uninstalling the latest graphic/video software downloaded from ATI thinking the installed ATI Radeon driver or software could be the issue. When uninstalled, the system used the Microsoft drivers. Same scenarios as above regardless if the ATI drviers and software were installed or not.

9. I ran my Norton Internet Security 2011 and also the popular Maywarebytes' Anti_malware softwares as a full scan. No malware detected.



I included below images of the minidump files from my Windows 7 64-bit using BlueScreenView software to aid in the determination of this issues. I notice that the driver ntoskrnl.exe has caused this issue in most cases. I see the address ntoskrnl.exe+80640 was involved in most cases too.

Please reply with possible solutions to my issue.

Thanks!

 

Can you go to Windows > Minidumps and copy the top (latest) 4 dumps to your Desktop, zip and attach them, please? I'll try to do a quick debug on them.

 

@ satrow:

Hello. Thanks for your reply!!!

I absolutely appreciate your assistance with my serious issue. To help you out and save you time, I have debugged them for you and attached the minidump information for the first 7 from the top of the BlueScreenView list. If you need to still have them sent to the DMP files in zip files because you need to have them debugged for your means, please reply and let me know. I figured I would give you a break from the tedious debugging since you are helping me. I just do not know how to understand them in determining the cause of the problems.

MINIDUMP 1:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\032811-25974-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03019000 PsLoadedModuleList = 0xfffff800`0325ee90
Debug session time: Mon Mar 28 20:46:34.231 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:26.979
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80000b9b020, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\L1E62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : NETIO.SYS ( NETIO!NetioDereferenceNetBufferListChain+132 )

Followup: MachineOwner
---------

MINIDUMP 2:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\032811-29967-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0300d000 PsLoadedModuleList = 0xfffff800`03252e90
Debug session time: Mon Mar 28 17:14:24.204 2011 (UTC - 4:00)
System Uptime: 0 days 0:43:01.952
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8000309d316, fffff880057f1e00, 0}

Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+46 )

Followup: MachineOwner
---------

MINIDUMP 3:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\032811-36067-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03060000 PsLoadedModuleList = 0xfffff800`032a5e90
Debug session time: Mon Mar 28 16:30:09.715 2011 (UTC - 4:00)
System Uptime: 0 days 1:22:07.463
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800030f0316, fffff8800a05ae00, 0}

Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+46 )

Followup: MachineOwner
---------

MINIDUMP 4:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\032811-36192-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0304e000 PsLoadedModuleList = 0xfffff800`03293e90
Debug session time: Mon Mar 28 15:00:27.261 2011 (UTC - 4:00)
System Uptime: 0 days 2:20:00.009
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8000336f9f3, fffff880035cae98, fffff880035ca6f0}

Probably caused by : cng.sys ( cng!GatherRandomKey+22c )

Followup: MachineOwner
---------

MINIDUMP 5:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\032811-26941-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0300e000 PsLoadedModuleList = 0xfffff800`03253e90
Debug session time: Mon Mar 28 01:05:55.202 2011 (UTC - 4:00)
System Uptime: 0 days 0:09:35.560
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8000309e316, fffff88006e71ff0, 0}

Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+46 )

Followup: MachineOwner
---------

MINIDUMP 6:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\032811-28688-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`03299e90
Debug session time: Mon Mar 28 00:43:10.914 2011 (UTC - 4:00)
System Uptime: 0 days 0:17:22.272
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800030e4316, fffff8800b953ff0, 0}

Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+46 )

Followup: MachineOwner
---------

MINIDUMP 7:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\032811-28438-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0300b000 PsLoadedModuleList = 0xfffff800`03250e90
Debug session time: Mon Mar 28 00:25:08.191 2011 (UTC - 4:00)
System Uptime: 0 days 0:21:32.549
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff88003118b90, 0, 0}

Unable to load image \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\Definitions\IPSDefs\20100706.002\IDSVia64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for IDSVia64.sys
*** ERROR: Module load completed but symbols could not be loaded for IDSVia64.sys
Probably caused by : IDSVia64.sys ( IDSVia64+8575 )

Followup: MachineOwner
---------






Please reply at your earliest possible convenience with possible reasons and solutions to this issue.

Thank you!

 

I really do prefer to debug myself, the dumps can tell me a lot about the specific drivers loaded when the BSODs occur.

I'll stick my neck out a little on this one though - uninstall Norton/Symantec fully. Then test for a few hours or until you get a new BSOD - zip and attach it if you do

If it's ok after a few hours, install Avast!.

 

Hello again!

I have been reading and I made it back here. I just read your lastest post. Thanks, satrow. I haven't uninstalled Norton/Symantec yet, but I have read that some users are pointing to the graphics card driver/software as the issue.

So I uninstalled the latest ATI Radeon driver/software in normal mode and was told to go into safe mode for Windows 7 and use Driver Sweeper for the rest to clean up the entire system. When I did and as my sys files were loading, but before the logon screen was able to display, the system crashed again with a BSOD. I have a copy of that one minidump file encased in a zip file ready for your inspection.

Please let me know or tell me what you think? Shed any light on the topic?

Please reply.

Thanks!

 

That one flags up the ReadyBoost driver, a standard Windows driver so very unlikely to be the real cause. Debugging now

 

I'll be AFK for some time now, when you look in next, could you visit this page and run the hard drive and memory diagnostics please? The Memtest 86+, run for 7+ passes if you can - if anything reads for Vista, assume that it'll run the same way for W7.

Oh, attach a few more dumps if you can, 1 of each type will be great, thanks.

Do you use a ReadyBoost drive?