SuperFetch has been stopped and Disabled from automatically starting.
You can find the dump file in post #43.
I could repost it, but I don't want any sort of automatic detection system to think I'm spamming the forums with my uploads. (as a teen, I've once had a 1-day ban from the Newgrounds forums due to an accident like that)
Hi,
Just scrutinised your logs again and found AVG is causing issues, perhaps with
your network also as TCPIP errors also show:
I would suggest removing AVG, even for testing purposes:Code:Driver: avgmfx64.sys Refers to: AVG Mini-Filter Resident Anti-Virus Shield Driver: avgtdia.sys Refers to: AVG TDI Driver Driver: avgidsdrivera.sys Refers to: AVG IDS Application Activity Monitor DriverDownload tools and utilities | AVG UK
and as an alternative download and install:
Microsoft Security Essentials.
Recommended from a strict BSOD perspective, compatibility & stability
compared to other antiviruses/internet security software.
TipOnce installed, update and run full system scan
TCPIP error:
Ensure all networking/wireless adapter drivers are updated.Code:1 error : !tcpip (fffff88001663fe7) fffff88001663fe0 24 01 08 47 10 49 8b *05 00 4c 8b a8 88 02 00 00 $..G.I...L......
cheers
Dave
Hunh...
AVG is removed.MSE has long taken it's place. For said driver-related reasons, actually.
What process would you suggest into removing the drivers? The same "rename and reboot, remove if that brings no issues" ? Or use the AVG Removers regardless?
I'll take a gander at my Network drivers. Funny how my memory reminds me now how most of my BSOD's in the past have been happening in online games. Including Rusty Hearts and Gotham City Imposters FTP.
EDIT: Will searching for updates through Device Manager suffice? Or do you recommend any sort of program to update drivers? I know how hated many of those "driver checkers" are.
Ahh..sorry I was looking at your previous dump files, my mistake.
Did not realise it was now uninstalled.
Best run the SF Tool again and post up a fresh log as Tom suggested and we can check.
Yes, just double checked, those drivers are long gone. I've had a hunch AVG had been less and less effective. But that's a matter of taste and whatnot so I'll not clutter this topic with it.
What did you mean again with the SF Tool? I flipped back a few pages and the closest thing I can recall Tom mentioning is the SFC scan. Would you happen to mean that?
Sorry if I am mistaken. Sometimes my mind might fail me.
Sorry, i meant post your logs up, but run the SF Tool so we can see
how your computer looks at present:
cheers
Dave
Oh right, that one.
It should be uploaded below, though you may have to deal with one problem...
See, I took a quick gander through some of the .txt files, and some things seem to be in Dutch...
So, if you have no translation expert on staff, you can freely ask me what something means in Dutch. I'll gladly translate for you.
You'll also see some old dumps in there. I've received help from a friend before with some BSOD's, and the Laptop ran properly for long enough for me to personally assume that the BSOD's these are related to can be considered solved. I simply keep them for future reference. I hope that such a thing doesn't affect the computer itself in any way? I assumed it didn't.
Ive asked another member to look at your logs.
In the meantime, can you run memtest please:
Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
TipRun these tests overnight
I also think that Memtest is the first one to do here.
Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.Code:STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -db !rdyboost 8 errors : !rdyboost (fffff88001b64d84-fffff88001b64dbc) fffff88001b64d80 00 4c 8b ac *c8 70 01 00 00 4c 8b b4 *36 98 00 00 .L...p...L..6... fffff88001b64d90 00 41 b8 02 *ec 00 00 48 83 3d a9 c3 *13 00 ff 74 .A.....H.=.....t fffff88001b64da0 1a 4c 3b fe *0c 15 45 84 45 20 75 0f *ab c9 ff 15 .L;...E.E u..... fffff88001b64db0 4c 72 01 00 *31 89 05 35 c4 01 00 41 *20 01 00 00 Lr..1..5...A ... MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: STRIDE FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE Followup: memory_corruption ---------
- Click on the Start button
- Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
- Select the “Startup” tab.
- Deselect all items other than the antivirus and the touchpad driver, SynTPEnh.
- Apply > OK
- Accept then restart.
Update your Ricoh drivers, Ricoh SD/MMC Host Controller and Ricoh xD-Picture Card Controller .... those are seeming to be very old ....
Search for updates in Home | Ricoh GlobalCode:fffff880`05a17000 fffff880`05a6e000 rixdpx64 (deferred) Image path: \SystemRoot\system32\DRIVERS\rixdpx64.sys Image name: rixdpx64.sys Timestamp: Thu Jun 25 13:08:50 2009 (4A43298A) CheckSum: 00019F7D ImageSize: 00057000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Next step, if the memtest comes clean, enable Driver Verifier.
What Dave suggested you earlier, that your BIOS version is A08. Plan to upgrade it to A09, the latest one.
BTW< another thing you should consider. It's running on the factory install over a long time. I'd recommend you to Clean Up Factory Bloatware, with a special reference to Point #13
__________________________________________________________________________13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.
BSOD ANALYSIS:
Code:BugCheck 1A, {41201, fffff68000014140, 7760000203a42847, fffffa800d20f460} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13702 ) Followup: MachineOwner --------------------------------------------------------------------------------------- BugCheck 50, {ffffd400b64999ef, 0, fffff88001b64d81, 7} Could not read faulting driver name *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption Followup: memory_corruption ---------
Alright, once I get home I'll get started on that as soon as possible.
When talking about Bloatware, what pieces of software that are installed would you consider as such? I can imagine a few of the Alienware programs being Bloatware, but the one in particular that controls my keyboard lighting is something I've come to very much rely on. Especially since I tend to be in the dark.
Quote