Solved Constant Random BSOD

[JackRouge]

Hi there

Been having BSOD issues over the last day on a new laptop. It was initially when I went onto the internet, but it seems okay now. But there is still the random one every now and then for no reason. I got rid of my Norton and replaced it with MSE as I read a few times to do.

Another thing that's started happening is constant messages coming up of programs/processes stopping, e.g. 'host process for Windows Services has stopped running' and much more. Plus, earlier today I kept having 'Aw, Snap!' on Chrome very often, which I'm guessing is related to whatever issue I have...

Also, after testing with Memtest86+, there were millions of errors, so clearly there's a RAM issue. Unsure on what to do though.

- Windows 7 Home Prem OA
· x64
· OEM
· Bought 3/4 weeks ago brand new
- AMD Dual Core E450
- 1.65GHz, RAM 4GB
· E2 Vision AMD


Model is Samsung RV515. Cheers for any help, driving me mad.

 

[koolkat77]

Welcome to the forum.

Your dumps come with various issues.

First update your network adapter drivers to the most latest version.

BSOD Analyze

MODULE_NAME: athurx

IMAGE_NAME:  [COLOR="Blue"]athurx.sys[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  4b42b0a4

FAILURE_BUCKET_ID:  X64_0xA_VRF_CODE_AV_BAD_IP_athurx+afe59

BUCKET_ID:  X64_0xA_VRF_CODE_AV_BAD_IP_athurx+afe59

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

0: kd> lmvm athurx
start             end                 module name
fffff880`06002000 fffff880`061ca000   athurx   T (no symbols)           
    Loaded symbol image file: athurx.sys
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
    Image name: athurx.sys
    Timestamp:        [COLOR="Blue"]Tue Jan 05 09:23:16 2010 (4B42B0A4)[/COLOR]
    CheckSum:         001C7F92
    ImageSize:        001C8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Source | athurx.sys | Atheros AR9271 Wireless Network Adapter | ATHEROS drivers for Microsoft Windows (Atheros?????)

Other dumps show memory (Like you mentioned) and hardware issues.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {c0000268, 2, 0, fffff80002e8506e}

Probably caused by : [COLOR="Blue"]hardware[/COLOR] ( nt!KiSwapContext+6e )

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

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88002382860, fffff88001fcea68, fffff88001fce2c0}

Probably caused by : [COLOR="Blue"]memory_corruption[/COLOR]

Followup: memory_corruption

Since you're under warranty, you should go back and get the memory sticks replaced.

For a fresh start follow steps in these tutorials:
:ar: http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html
:ar: http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html
:ar: http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html

Keep us posted of what you've done.

 

[JackRouge]

Thank you very much kk. I've arranged for a pickup & repair with the manufacturers, so that should be sorted within a week or so.

 

[koolkat77]

Hello
Did you get your new ram sticks?

 

[JackRouge]

I did! All working fine now. Had some other problems when I got it back when trying to install MSE and do Windows Updates, but I did a Windows Upgrade/repair and it's all good now.

Cheers again for the help!

 

[koolkat77]

Good news and thanks for posting back.
Feel free to mark this thread as solved.