Solved all good in safe mode, freezing in normal mode w/ occasional BSOD

[BPoi523433]

Hello,

My laptop is slow to boot and will run for 5-10 minutes in normal mode before it freezes and the mouse cursor disappears. At this point it will be completely frozen and I must hold the power button. In safe mode, it seems to run fine without any issues. I have gotten the BSOD twice with this problem, but never long enough for me to actually read what it said. If it makes a difference, my battery is nearly dead and I have to leave the laptop plugged in almost always.

The following symptoms could be entirely in my head...but I figured I would just give all of the information. I think I hear a slight ticking noise on startup and it seems like the fan is working overtime.

The requested .zip file is attached.

Thank you very much for any help. I'm willing to upload any more information you need if you'll tell me how to do it, I'm not overly computer-savvy.

Thanks,
Bob

 

[UsernameIssues]

Welcome to the Seven Forums.

While we await a BSOD expert to take on your thread, maybe you can work thru these steps...
http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html
...since you mentioned that thing work in the safe mode.

 

[BPoi523433]

No help from the above suggestion. Thank you for trying.

 

[UsernameIssues]

That is curious.

I thought it was something that was starting in the normal mode that was causing your issue.

:::back to lurking:::

 

[BPoi523433]

I tried to do a system restore and got the BSOD again. Here's the mini dump file.

Thanks if anyone can help.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 1000008E[/COLOR], {[COLOR="SeaGreen"]c0000005[/COLOR], 833cf487, b3a99754, 0}

*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
Probably caused by : ataport.SYS ( ataport!IdePortDispatchDeviceControl+b )

Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory

ataport.sys being referenced is usually either due to virus infection, corrupted hard-drive, poor SATA cabling or drivers which are blocking any further I/O requests.

0: kd> [COLOR="seagreen"]!error c0000005[/COLOR]
Error code: (NTSTATUS) 0xc0000005 (3221225477) - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

There seems to be some memory access errors, this is usually caused by drivers referencing invalid memory addresses.

Scan for any malware:

• http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html
• Anti-rootkit utility TDSSKiller

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

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

Use this command with Disk Check:

chkdsk C: /f /r

 

[BPoi523433]

Solved! Thank you so much, you're my hero, buddy. The anti-rootkit tool did the trick.

Donations accepted here?

-Bob

 

[x BlueRobot]

Very welcome, glad to help, and I'm not sure, I think they did at one point.