BSOD when shutting down

#1
Hi,

I have a Gateway lx6810 (desktop), right now I'm having a problem of BSOD when the pc is shutting down.

Model: Gateway lx6810
Ram: 8gb
CPU: Intel Core Core 2 Quad Q8200 2.33GHz
Display: Nvidia GeForce GT 120

Im uploading my dump files to see if you can help me with this problem...

Thanks in advance
Blackjosbi
 


Attachments

#2
Hey...welcome.

Wow, alright. 0x124 stops which mean hardware is to blame. I see lots wrong with the machine, so to save you the trouble of possibly troubleshooting hardware, let's get the software part in order first and take things from there.

1) Your USB Camera driver must be updated from manufacturer's website or uninstalled completely:

Code:
snpstd3  snpstd3.sys  Tue Mar 27 06:18:55 2007
2) Uninstall Avast in safe mode using the tool found here:

AV Uninstallers - Windows 7 Forums

Then boot to normal mode and install MSE.

3) Update your AverMedia driver from the manufacturer's website:

Code:
AVer88xHD64 AVer88xHD64.sys Thu Jun 25 06:09:54 2009
4) Update your old modem driver from Gateway's site:
Code:
agrsm64  agrsm64.sys  Mon Nov 10 10:01:35 2008
5) Update your NVIDIA chipset driver package to latest. Very important.

6) Very important also to update PowerISO to latest:

Code:
 SCDEmu   SCDEmu.SYS   Tue Aug 07 11:19:48 2007
PowerISO - Create, Edit, Compress, Encrypt, Split, Mount, Extract ISO file, ISO/BIN converter, Virtual Drive

7) If stop errors continue after you are absolutely sure you've done all the above, then see this 0x124 thread on how to troubleshoot the hardware:

Stop 0x124 - what it means and what to try - Windows 7 Forums
 


zigzag3143

Honorable Member
Microsoft MVP
#3
Hi,

I have a Gateway lx6810 (desktop), right now I'm having a problem of BSOD when the pc is shutting down.

Model: Gateway lx6810
Ram: 8gb
CPU: Intel Core Core 2 Quad Q8200 2.33GHz
Display: Nvidia GeForce GT 120

Im uploading my dump files to see if you can help me with this problem...

Thanks in advance


Hi and welcome


All 13 of these crashes were caused by hardware. Please read here for what it means and what to try.

Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try -

Thanks


Ken




Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Seven Forums\081310-18907-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a19000 PsLoadedModuleList = 0xfffff800`02c56e50
Debug session time: Fri Aug 13 08:05:07.783 2010 (GMT-4)
System Uptime: 0 days 0:00:19.968
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008037028, b2000040, 800}

Probably caused by : hardware

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8008037028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009f2a58 fffff800`03007903 : 00000000`00000124 00000000`00000000 fffffa80`08037028 00000000`b2000040 : nt!KeBugCheckEx
fffff880`009f2a60 fffff800`02b9f593 : 00000000`00000001 fffffa80`075cfde0 00000000`00000000 fffffa80`075cfe30 : hal!HalBugCheckSystem+0x1e3
fffff880`009f2aa0 fffff800`030075c8 : 00000000`00000728 fffffa80`075cfde0 fffff880`009f2e30 fffff880`009f2e00 : nt!WheaReportHwError+0x263
fffff880`009f2b00 fffff800`03006f1a : fffffa80`075cfde0 fffff880`009f2e30 fffffa80`075cfde0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f2c50 fffff800`03006dd5 : 00000000`00000004 00000000`00000001 fffff880`009f2eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f2c90 fffff800`02ffae88 : 00000000`489d9c79 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f2cc0 fffff800`02a87fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f2cf0 fffff800`02a87e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f2e30 fffff800`02a97610 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`05837ab0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x260


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

Followup: MachineOwner
---------
Old drivers needing upgrading
Code:
snpstd3.sys        fffff880`05671000    fffff880`06080c00    0x00a0fc00    0x4608ef8f    3/27/2007 06:18:55                        
SCDEmu.SYS        fffff880`02c2f000    fffff880`02c41000    0x00012000    0x46b88d94    8/7/2007 11:19:48                        
nvm62x64.sys        fffff880`04000000    fffff880`04063d80    0x00063d80    0x48f8fd12    10/17/2008 17:01:06                        
agrsm64.sys        fffff880`040a1000    fffff880`041c3000    0x00122000    0x49184ccf    11/10/2008 11:01:35                        
spldr.sys        fffff880`01600000    fffff880`01608000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
amdxata.sys        fffff880`011c0000    fffff880`011cb000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
dump_nvraid.sys        fffff880`04b8e000    fffff880`04bb7000    0x00029000    0x4a13a5ac    5/20/2009 02:39:40                        
nvraid.sys        fffff880`00e6a000    fffff880`00e93000    0x00029000    0x4a13a5ac    5/20/2009 02:39:40                        
nvstor.sys        fffff880`01133000    fffff880`0115e000    0x0002b000    0x4a13a711    5/20/2009 02:45:37                        
AVer88xHD64.sys        fffff880`04226000    fffff880`042a2300    0x0007c300    0x4a434cf2    6/25/2009 06:09:54
Blackjosbi[/QUOTE]
 


#4
Thanks for the fast reply...

I'm going to update the drivers you told me to upgrade to and see what happens..
I'll keep you updated on my pc status!!

Thanks
 


#6
Hi,

I don't have much to add, most of your crash dumps point to the 0x124 stop WHEA_UNCORRECTABLE_ERROR caused by hardware. Please see this link again:

Stop 0x124 - what it means and what to try - Windows 7 Forums


One of your dumps points to the Avermedia driver fault, so update it, your current version is obsolete enough - 2009.


Another dump points to VIDEO_TDR_ERROR, which is a more concrete but actually the same kind 0x124 stop - hardware:

Bug Check 0x116: VIDEO_TDR_ERROR


Also, update the drivers. As for Avast, the idea is to have everything in your system as stable and native as possible, and MSE is a wonderful option. After updating everything, write back and attach your latest crash dumps if any.
 


#7
I was checking my drivers...
But I don't find any program that use AverMedia driver neither the AverMedia driver itself...
What can I do to download the AverMedia that I need? (the correct one)

Thanks
 


#8
I was checking my drivers...
But I don't find any program that use AverMedia driver neither the AverMedia driver itself...
What can I do to download the AverMedia that I need? (the correct one)

Thanks

You can download the right driver from Avermedia site. If you don't have any Avermedia hardware (see your device manager), then this driver (AVer88xHD64 AVer88xHD64.sys Thu Jun 25 06:09:54 2009) is a remnant which you should uninstall. Use Control Panel > Programs and components.


AVerMedia M790 PCIe Combo NTSC/ATSC, if I am correct.
 


#9
This dump 090310-14476-01.dmp for example shows that you do have this driver:


fffff880`04485000 fffff880`04501300 AVer88xHD64 AVer88xHD64.sys Thu Jun 25 13:09:54 2009 (4A434CF2)


You have many others already listed in this thread that you should definitely update, as some of them are literally obsolete, e.g.

nvm62x64 nvm62x64.sys Sat Oct 18 00:01:06 2008
NVIDIA Networking Driver

agrsm64.sys Mon Nov 10 17:01:35 2008
SoftModem Device Driver
LSI SoftModem Driver


You need to update all those drivers to be sure it's not their issue. Attach any latest dumps if they occur.
 


#10
Why do I have to uninstall my anti virus?
If you can tell me from the info I gave you?

Thanks
Because you have 0x124 errors. You'll be lucky to fix it at all with attention to drivers.

I'm putting you in the best position possible.

Follow it as closely as possible if you want best results. You still will likely have a hardware issue but you'll never know until you do all I said.

(Don't worry about spldr.sys - That's a MS driver installed with the OS.)
 


#11
aswTdi.SYS Wed Nov 25 01:49:09 2009
aswRdr.SYS Wed Nov 25 01:48:59 2009
aswMonFlt.sys Wed Nov 25 01:49:55 2009
Avast


SCDEmu.SYS Tue Aug 07 18:19:48 2007
Power ISO virtual drive, too old, uninstall your version and install the latest
PowerISO - Create, Edit, Compress, Encrypt, Split, Mount, Extract ISO file, ISO/BIN converter, Virtual Drive


nvm62x64 nvm62x64.sys Sat Oct 18 00:01:06 2008
NVIDIA Networking Driver
Drivers - Download NVIDIA Drivers


dump_nvraid.sys Wed May 20 09:39:40 2009
Drivers - Download NVIDIA Drivers


nvstor.sys Wed May 20 09:45:37 2009
NVIDIA nForce(TM) SATA Driver
Drivers - Download NVIDIA Drivers


agrsm64.sys Mon Nov 10 17:01:35 2008
SoftModem Device Driver
LSI SoftModem
http://www.lsi.com/lookup/Downloads.aspxDriver


snpstd3.sys Tue Mar 27 13:18:55 2007
Sonix USB PC Camera
Sonix Technology Co., Ltd.


AVer88xHD64.sys Thu Jun 25 13:09:54 2009
AVerMedia AVerTV Global - TV Tuners, Media Player, IPTV and Multimedia Products
 


#12
Hi,

I don't have much to add, most of your crash dumps point to the 0x124 stop WHEA_UNCORRECTABLE_ERROR caused by hardware. Please see this link again:

Stop 0x124 - what it means and what to try - Windows 7 Forums


One of your dumps points to the Avermedia driver fault, so update it, your current version is obsolete enough - 2009.


Another dump points to VIDEO_TDR_ERROR, which is a more concrete but actually the same kind 0x124 stop - hardware:

Bug Check 0x116: VIDEO_TDR_ERROR


Also, update the drivers. As for Avast, the idea is to have everything in your system as stable and native as possible, and MSE is a wonderful option. After updating everything, write back and attach your latest crash dumps if any.


Because you have 0x124 errors. You'll be lucky to fix it at all with attention to drivers.

I'm putting you in the best position possible.

Follow it as closely as possible if you want best results. You still will likely have a hardware issue but you'll never know until you do all I said.

(Don't worry about spldr.sys - That's a MS driver installed with the OS.)


~~~~~~~~

TorrentG is right, I would do a clean vanilla install just to check the hardware. Possibly try updating bios. Remove hardware parts to see what's likely causing it. All well outlined in TorrentG's link :

Stop 0x124 - what it means and what to try - Windows 7 Forums
 


#13
Well.. I think I did everything in the list you told me to do...
Here is the dump file when my crash the last time...

Note: The computer when is on... it works perfectly, everything runs smoothly and so on... Seems to be working well... It only BSOD when is shutting down, restart, etc..

Thanks
 


Attachments

#14
NVIDIA chipset drivers not updated yet.

AVer88xHD64.sys not updated yet.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.