Windows 7 BSOD's and bad startups

Jakee

New Member
Really tired and stressed from this computer.

I feel it is nearly just time to take it to my local computer shop and get them to deal with it, Wipe, Fix - Whatever it takes.
View attachment minidump.zip

I have tried, System Restore, Chkdsk's and Repairs.

irql_not_less_or_equal is the main BSOD showing up now.

Also my startups take forever, No not loading times - The fact that it just doesn't startup.

I get to the first screen and it either freezes or restarts itself or the second screen where all the writing goes really fast down, It just blinks at the top left hand corner.


If i end up getting a reply i appreciate if all this is looked into because it is as much info as i can give, Nothing else has been aware to me.

Cheers again.
 
Welcome to the forums, Jakee. : )

Your dumps point to problems in memory management (with lots of references to ntfs) and ntfs file system.

1. Check the hard disk for errors:

chkdks /r /f
HDDScan



2. Update:

GEARAspiWDM.sys Mon May 18 15:16:53 2009
CD-ROM Class Filter Driver by Gear Software
GEAR Software - DVD Mastering Software & CD Burning Software & GEAR PRO Mastering


athr.sys Mon Oct 05 19:31:48 2009
Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
Atheros, wireless local area networking, wireless, WLAN, 802.11n, 11n, 802.11g, 11g, 802.11ag, 11ag, 802.11, Radio-on-Chip, Ethernet, Mobile, Bluetooth, GPS, Semiconductor, System Solutions


TPkd.sys Wed Dec 23 21:32:25 2009
InterLok system
PACE Anti-Piracy, Inc.
Link Removed due to 404 Error



091710-16656-01.dmp
MEMORY_MANAGEMENT (1a)

PROCESS_NAME: wmpnetwk.exe (wmp network service)
FAILURE_BUCKET_ID: 0x1a_8887_ZEROED_PAGE_CORRUPTED
STACK_TEXT:
a594961c 82cef026 0000001a 00008887 855dd0e4 nt!KeBugCheckEx+0x1e
a594965c 82cf0bd5 00000000 82d894c0 84f48cf8 nt!MiUnlinkPageFromLockedList+0x51
a59496ac 82cfce29 00000000 ac4e6800 8d945530 nt!MiResolveTransitionFault+0x550
a59496f8 82ce5916 00000000 ac4e6800 c0562730 nt!MiResolveProtoPteFault+0x3d8
a5949780 82cdbd76 ac4e6800 00000000 82d894c0 nt!MiDispatchFault+0x5d6
a594980c 82c9b638 00000000 ac4e6800 00000000 nt!MmAccessFault+0x157c
a594980c 82e9c688 00000000 ac4e6800 00000000 nt!KiTrap0E+0xdc
a59498d8 83aada06 86808288 a5949910 00000400 nt!CcMapData+0xae
a5949900 83aacf57 85ed2950 87304008 0b2a6800 Ntfs!NtfsMapStream+0x4a
a594997c 83aad949 85ed2950 873080d8 bbba4010 Ntfs!NtfsReadMftRecord+0x7d
a59499a8 83aad77d 85ed2950 873080d8 bbba4010 Ntfs!NtfsReadFileRecord+0x31
a59499d8 83ad6104 85ed2950 bbba4008 bbba4010 Ntfs!NtfsLookupInFileRecord+0x11f
a5949ac4 83aa75f9 85ed2950 00000001 00000000 Ntfs!NtfsUpdateFcbInfoFromDisk+0x6f
a5949bf4 83abb381 85ed2950 86150a60 b0754510 Ntfs!NtfsOpenFile+0x4c4
a5949cdc 83a41210 85ed2950 86150a60 a711a944 Ntfs!NtfsCommonCreate+0xd84
a5949d1c 82cc511e a711a8dc 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20
a5949d1c 82cc5215 a711a8dc 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x15a
a711a840 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31



092010-17671-01.dmp
IRQL_NOT_LESS_OR_EQUAL (a)

READ_ADDRESS: GetPointerFromAddress: unable to read from 82da6718
Unable to read MiSystemVaType memory at 82d86160
0000000c
FAILURE_BUCKET_ID: 0xA_nt!MiIdentifyPfn+24f
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+24f )



092110-16578-01.dmp
NTFS_FILE_SYSTEM (24)

FAILURE_BUCKET_ID: 0x24_Ntfs!NtfsDeleteScb+e4



092210-19468-01.dmp
FLTMGR_FILE_SYSTEM (f5)

An unrecoverable failure occured inside the filter manager
FAILURE_BUCKET_ID: 0xF5_fileinfo!FIStreamCleanup+94
STACK_TEXT:
807ffa5c 833b8ed1 000000f5 00000068 c5d97570 nt!KeBugCheckEx+0x1e
807ffa78 839e4d58 c5d9759c bda27390 85dc6a0f fltmgr!FltReleaseFileNameInformation+0x43
807ffa9c 8339e5f4 bda273c0 00000008 00000000 fileinfo!FIStreamCleanup+0x94
807ffab8 8339e7c0 bda27390 bda27390 807ffadc fltmgr!DoFreeContext+0x66
807ffac8 833af722 bda27390 85dc6a08 85dc69e0 fltmgr!DoReleaseContext+0x42
807ffadc 833bc793 85dc6a0c 85dc6a08 ffffffff fltmgr!FltpDeleteContextList+0x15c
807ffafc 833bc9b4 85dc69e0 c5d69d08 00000000 fltmgr!CleanupStreamListCtrl+0x1b
807ffb10 82e1e818 85dc69e4 afc81a58 00000000 fltmgr!DeleteStreamListCtrlCallback+0x5a
807ffb50 83adefb2 c5d69d08 c5d69c18 c5d69d08 nt!FsRtlTeardownPerStreamContexts+0x13a
807ffb6c 83ad5b3b 00000703 c5d69c40 c5d69c18 Ntfs!NtfsDeleteScb+0x214
807ffb84 83a4571e 85b6b4a0 c5d69d08 00000000 Ntfs!NtfsRemoveScb+0xc5
807ffba0 83ac60d2 85b6b4a0 c5d69c18 00000000 Ntfs!NtfsPrepareFcbForRemoval+0x62
807ffbe4 83a42bec 85b6b4a0 c5d69d08 00000000 Ntfs!NtfsTeardownStructures+0x68
807ffc0c 83ac255b 85b6b4a0 c5d69d08 00000000 Ntfs!NtfsDecrementCloseCounts+0xaf
807ffc6c 83ae14c3 85b6b4a0 c5d69d08 c5d69c18 Ntfs!NtfsCommonClose+0x4f2
807ffd00 82c6df3b 00000000 00000000 85a01d48 Ntfs!NtfsFspClose+0x118
807ffd50 82e0e6d3 00000000 afc81c98 00000000 nt!ExpWorkerThread+0x10d
807ffd90 82cc00f9 82c6de2e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
 
Thankyou for the reply cybercore, As i will do what you say i have one question; Any chance that it could be hardware related? Cheers

Edit: I've updated my drivers except the Atheros one I have no idea which driver to download, How can I found out what driver number I need to download for it?
 
Last edited:
1. Yes, it can be hardware related, check both hdd and ram
2. Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
3. If more bsod's, attach them
 
I will be running the Memtest when I go to bed and how would i go about checking the hdd and ram?

Also it says that: Windows has determined the driver software for your device is up to date: ATHEROS AR5005GS Wireless Network Adapter

And when i search anywhere for CB42/CB43/MB42/MB43 it just comes up with other peoples threads with BSODS but when i search the AR5005GS it comes up with a driver website but no WIN7 just Xp/Vista and the dates on those drivers are older then the one i have.

I still think personally it is this driver that is causing it though but it's all so strange to me.

Any more BSOD's and i will post. Thankyou.
 
Update from manufacturer's sites of the hardware and never use Windows Update or Device Manager to get drivers.
 
Back
Top