Various BSOD, Some Random most involve ntoskrnl.exe

Welcome

Your dumps come with various bug checks:

Analysis:

Code:

STOP 0x0000001A: MEMORY_MANAGEMENT 
Usual causes:  Device driver, memory, kernel
BugCheck 1A, {41284, fffff70440007001, 149287, fffff70001080000}
Probably caused by : win32k.sys ( win32k!SURFACE::Map+175 )
-------------
STOP 0x0000001A: MEMORY_MANAGEMENT 
Usual causes:  Device driver, memory, kernel
BugCheck 1A, {3452, 860000, fffff700010834d8, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35133 )
-------------
STOP 0x00000024: NTFS_FILE_SYSTEM  
Usual causes:  Disk corruption, insufficient physical memory, Device driver, 
Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
BugCheck 24, {1904fb, fffff8800a8a0e38, fffff8800a8a0690, fffff80003408617}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+29f9 )
-------------
STOP 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Usual causes:  Device driver, Memory
BugCheck BE, {fffff88001851190, 45e4121, fffff8800305f680, b}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+44c9e )
-------------
STOP 0x00000019: BAD_POOL_HEADER 
Usual causes:  Device driver
BugCheck 19, {3, fffffa800ccf0870, fffffaa00ccf0870, fffffaa00ccf0870}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
-------------
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION  
Usual causes:  System service, Device driver, graphics driver, memory
BugCheck 3B, {80000003, fffff80003292e38, fffff880037f5920, 0}
Probably caused by : ntkrnlmp.exe ( nt!DebugPrompt+18 )
-------------
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA  
Usual causes:  Defective hardware (particularly memory - but not just RAM), 
Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS.
BugCheck 50, {fffff882016634c4, 0, fffff8800162a3f5, 5}
Probably caused by : Ntfs.sys ( Ntfs!memmove+1e5 )

Problematic software:

Code:

Start Menu\Programs\Norton Security Suite	Public:Start Menu\Programs\Norton Security Suite	Public

Norton alone is known to cause BSoDs. Suggest you to uninstall it (at least to test)
Download and install MSE. It's free, light weight and doesn't trouble the system.
→ Norton Removal Tool
→ Microsoft Security Essentials - Free Antivirus for Windows

Run Disk Check on your hard disk for file system errors and bad sectors on it:
→ Disk Check

Hard drive test both short and long with:
→ SeaTools for Windows

Also the DOS version of:
→ SeaTools for DOS

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

→ RAM - Test with Memtest86+
→ Guide to using Memtest86+ - Geeks to Go Forums

Run the system file checker that scans the integrity of all protected Windows 7 system files and
replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible
→ SFC /SCANNOW Command - System File Checker

Re-install the latest drivers for your graphic card drivers

Do these and let us know the results
We'll do more troubleshooting

The dump is blaming windows system files, which is not a true cause.

From analyzing the dump more, I found that iaStor refers to - Intel Rapid Storage is sort of creating a problem,
uninstall these for now (while we're troubleshooting. You may get the latest version of this tool after see your
computer is stable.

Code:

fffff880`0d6865e0  fffff880`03fa9ab0Unable to load image \SystemRoot\System32\Drivers\dump_iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dump_iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_iaStor.sys
 dump_iaStor+0x12cab0

Take your time. I'll wait for the results :)

Gx557 said:

I am still currently running a Disk Check but i just remembered something. When i originally purchased this laptop the hard drives came in Raid 0. The day after i took it out of raid and have both hard drives running as individual drives would this be causing an issue? Because the Bsods didn't start till much later after I had already took it out of raid. I hope that this additional info is helpful.

Hmm thanks for the info.
Carry out rest of the tests and let us know the results.
We'll see what we can do from there

Thanks for the update, the logs look good to me :)

Coming to the BSoD .dmp file.. It was caused by: Rt64win7 - Older "Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC" that needs to be updated.

Uninstall the older drivers first: Click on the Start ≥ Control Panel ≥ Programs ≥ Uninstall a program

Source for newer drivers: Filehippo -

• Download Realtek High Definition Audio 2.70 Vista 64 - FileHippo.com

OR

Carrona.org

• Driver Reference Table

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa80623bc198, 2, 0, fffff800032404d7}

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

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

0: kd> lmvm Rt64win7
start             end                 module name
fffff880`0ff1d000 fffff880`0ffa2000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Fri Jun 10 12:33:15 2011 (4DF1BAAB)
    CheckSum:         0008B67F
    ImageSize:        00085000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

No problem :)
Now you should just observe for more BSoDs, if they occur, update this thread by uploading the dumps like you did in your other posts. If there's no BSoD for a week or more than a week, you can mark the thread solved.

See you soon, good luck.