BSOD randomly occuring

[Xavion]

Ok so I recently got 2 BSOD's one of them was when i was on skype and my friend ended the call the 2nd one happened while i was in a group skype call and i was watching a gif the gif paused and then I got the BSOD. First time It said system service exception i think and the 2nd one was non paged area.

 

[axe0]

Hi Xavion,

Welcome to the 7forums.

Please remove the ASUS software, it is known for causing BSOD's.
Please check AMD for driver updates for the chipset, CPU, GPU and every other AMD component you have.

The Realtek PCIe GBE Family Controller driver has been flagged.
Please check Realtek for driver updates.

*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys

0: kd> lmvm Rt64win7
start             end                 module name
fffff880`044ff000 fffff880`045c6000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: [U]Rt64win7.sys[/U]
    Timestamp:        [COLOR="Red"][U]Wed Dec 26 18:17:50 2012[/U][/COLOR] (50DB313E)
    CheckSum:         000CDEEE
    ImageSize:        000C7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Xavion]

what things would be classified as asus software basically all the ai suite? and anything that came on the disc?

 

[axe0]

Unless you use some software and they don't give any problem it is recommended to remove every other ASUS software.

 

[Xavion]

welp i updated everything and removed all the asus stuff so far no BSOD so i think its fixed for now

 

[Xavion]

so it didnt fix it this time i was browsing reddit looking at pictures while listening to youtube when it randomly blue screened heres the dump

 

[axe0]

Please remove ASUS software AI Suite II.

The NTFS activity is increased over the days.
NTFS = file system (hard drive)
I recommend to test the hard drive.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk http://www.sevenforums.com/tutorials/433-disk-check.html

STACK_TEXT:  
fffff880`08f37af8 fffff800`02e303cf : 00000000`00000050 fffff8a2`0ffd3d41 00000000`00000000 fffff880`08f37c60 : nt!KeBugCheckEx
fffff880`08f37b00 fffff800`02e83e2e : 00000000`00000000 fffff8a2`0ffd3d41 00000000`00000000 fffffa80`0af429e0 : nt! ?? ::FNODOBFM::`string'+0x44891
fffff880`08f37c60 fffff880`010aa039 : fffffa80`0af429e0 fffffa80`07ecf350 fffff8a0`00280640 fffff880`08f38301 : nt!KiPageFault+0x16e
fffff880`08f37df0 fffff880`010a7911 : fffffa80`0af429e0 fffffa80`06fe6010 fffff880`08f37fc0 fffff880`08f38010 : [COLOR="red"]Ntfs[/COLOR]!NtfsFindStartingNode+0x4b9
fffff880`08f37ec0 fffff880`01010a3d : fffffa80`0af429e0 fffffa80`06fe6010 fffff880`08f38270 00000000`00000000 : [COLOR="red"]Ntfs[/COLOR]!NtfsCommonCreate+0x3e1
fffff880`08f380a0 fffff800`02e92668 : fffff880`08f381e0 fffff880`08f38370 fffff8a0`06e83140 fffffa80`07ece180 : [COLOR="red"]Ntfs[/COLOR]!NtfsCommonCreateCallout+0x1d
fffff880`08f380d0 fffff880`010111bf : fffff880`01010a20 fffff880`01010020 fffff880`08f38200 fffff880`010b1f00 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`08f381b0 fffff880`010aa99c : 00000000`00000000 00000000`00000000 fffff880`08f38400 fffffa80`06fe6010 : [COLOR="red"]Ntfs[/COLOR]!NtfsCommonCreateOnNewStack+0x4f
fffff880`08f38210 fffff880`00c02bcf : fffffa80`07ece030 fffffa80`06fe6010 00000000`00000000 fffffa80`07c898e0 : [COLOR="Red"]Ntfs[/COLOR]!NtfsFsdCreate+0x1ac
fffff880`08f383c0 fffff880`00c222b9 : fffffa80`06fe6010 fffffa80`07e45010 fffffa80`06fe6000 fffffa80`07c898e0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`08f38450 fffff800`03183625 : 00000000`00000045 fffffa80`0b520cc8 fffff880`08f388a0 00000000`00000000 : fltmgr!FltpCreate+0x2a9
fffff880`08f38500 fffff800`0317fec8 : fffffa80`07c21cd0 fffff800`00000000 fffffa80`0b520b10 00000000`00000101 : nt!IopParseDevice+0x5a5
fffff880`08f38690 fffff800`031810e6 : 00000000`00000000 fffffa80`0b520b10 fffff8a0`06ef1a90 fffffa80`06ce6850 : nt!ObpLookupObjectName+0x588
fffff880`08f38780 fffff800`03116874 : fffff8a0`0f1f4ce0 00000000`00000007 fffff8a0`03310001 fffffa80`0772d010 : nt!ObOpenObjectByName+0x306
fffff880`08f38850 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtQueryFullAttributesFile+0x14f

 

[Xavion]

so i uninstalled ai suite and i ran chkdsk and the other check disk i also ran smart check, short drive, and short generic test for seagate and nothing popped up should i run the long generic?

 

[axe0]

Yes please, usually the short generic test passes always.
The long generic test should then determine how your hard drive is doing.

 

[Xavion]

so the long generic test passed so now i guess i wait to see if anything pops up again

 

[axe0]

That is right

 

[Xavion]

ok so i got another blue screen this time all i was doing was browsing a reddit post and had 1 other tab open on Firefox heres the log. i'm kinda surprised it happened considering it hasn't happened since i removed the Ai suite but i guess problem still persists

 

[axe0]

As this is a read error, it has 2 sides.

• The memory gave corrupted data
• A driver accessed the wrong address in the memory

Please run MemTest86+

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: [COLOR="Red"]fffffa80646774cb, memory referenced.[/COLOR]
Arg2: [COLOR="red"]0000000000000000[/COLOR], value [COLOR="red"]0 = read operation[/COLOR], 1 = write operation.
Arg3: fffff80002ebf56f, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

 

[Xavion]

ok so i ran it for 8 passes and it has 0 errors so what should i do next

 

[axe0]

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

[Xavion]

so what happens if nothing shows up after testing with the drive verifer? could it be cause of a missing windows update?

 

[axe0]

If verifier finds nothing, there are quite a few methods to find out what is the cause

 

[Xavion]

thats good to know cause i wanna make sure it isn't a physical part that's defective so i can return it if needed within the refund window

 

[Xavion]

ok so before i had chance to run the driver verifier i got another bsod and this one said memory management

 

[axe0]

As the Memtest86+ test has passed, this is most likely due to a driver.
You could however check in the BIOS for the voltage and the frequency of the RAM to make sure these values are supported by the motherboard as these could also cause such crashes.