[SOLVED] BSOD Kernel 41 Error

K

kevinhen16

Member
Joined
Oct 21, 2013
Posts
5
Hello,

For a couple of months now, I have been experiencing frequent BSODs (almost daily). My attempts to fix this myself have become exhausting and I do not seem to be making any progress. I was hoping members of this forum could help.

I have read the posting instructions and have attached the requested files. Below are the answers to the questions listed in the posting instructions:

OS: Windows 8.0 (x64) was pre-installed when I bought the laptop
Age of both the OS and hardware is just a little over a year (purchased laptop from Lenovo December, 2012)
CPU: Intel Core i7 3517U
Video Card: Intel HD Graphics 4000
MotherBoard: LENOVO 3347CTO Win8 Pro DPK TPG
System Manufacturer: LENOVO
Model: LENOVO 3347CTO ThinkPad Twist

Please let me know if any other information is needed. I appreciate anyone's help with this problem.

-Kevin
 
Hi Kevin,

We have various different bug checks from the attached DMP files:

KERNEL_DATA_INPAGE_ERROR (7a)

This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.

BugCheck 7A, {fffff6fc4000a948, ffffffffc0000185, 1666e9860, fffff880015297ec}

The 2nd parameter of the bug check is 0xc0000185 which indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ. This could also indicate hard disk failure.

ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

CRITICAL_PROCESS_DIED (ef)

This indicates that a critical system process died.

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)


This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.


A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high. This bug check is usually caused by drivers that have used improper addresses.

--------------------------------------

Overall, due to the *7a analysis, let's go ahead and start hard disk diagnostics. Start with chkdsk and if it passes, move onto Seatools. If they both pass we are still not in the clear and you'll need to swap the connection cables from the controller to the hard disk to rule out faulty cables as well.


Chkdsk:
There are various ways to run Chkdsk~

Method 1:

Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)

Elevated CMD should now be opened, type the following:

chkdsk x: /r

x implies your drive letter, so if your hard drive in question is letter c, it would be:

chkdsk c: /r

Restart system and let chkdsk run.

Method 2:


Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click <Check Now>.

If you'd like to get a log file that contains the chkdsk results, do the following:

Press Windows Key + R and type powershell.exe in the run box

Paste the following command and press enter afterwards:

get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

This will output a .txt file on your Desktop containing the results of the chkdsk.

If chkdsk turns out okay, run Seatools -

SeaTools | Seagate

You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.

-----------------------------------------------------------------------

As this is a laptop, if you are not comfortable physically going into the laptop, your best bet is to contact Lenovo and tell them of the *7a bugchecks you are getting, the info they are showing, and discuss a repair and or replacement depending on warranty.

Regards,

Patrick
 
Thank you for your response!

I ran the disk check and have attached the log. It didn't seem to find any bad sectors. I was unable to successfully run the Seatools program. When attempting to run it in windows, the program kept crashing. Running in DOS is difficult, because my laptop does not have a CD-ROM drive from which to run the ISO. I tried running it from a USB drive using the ISO to USB program, but no such luck.

Do you have any further recommendations in terms of diagnostic programs for the hard drive?

I do have some experience working on the internals of my laptop, so there may be some procedures that I'm able to do, such as swapping out the cable like you mentioned in the response.

Again, I really appreciate your help. Thank you!
 

Attachments

Chkdsk log looks just fine, it's unfortunate we cannot run Seatools. The program crashing may or may not indicate something.

If it's possible for you to replace the connections to the controller / drive, that would be great.

Regards,

Patrick
 
Seems the connections to this particular hard drive are a bit beyond me. I attempted to find a cable that could be replaced only to find that the hard drive is installed into a slot. I've attached some pictures to better illustrate what I mean.

If it is certain that the problem is a hard drive issue, I would not be against replacing the hard drive; however, I would hate to go through that trouble prematurely if the problem was, say, an issue with an aberrant driver. Of course, if there was a connection fault somewhere, replacing the drive would also do little good.

What would you advise?

-Kevin
 
Oh, hmm, that's interesting. Well, we can sure check to see if any driver(s) are causing conflicts and or corruption for peace of mind:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - Restore Point - Create in Windows 8

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:

- Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users

Regards,

Patrick
 
I ran driver verifier for a couple of days without any BSODs. After turning off driver verifier, I also haven't had any of the previous BSODs either for a couple of days. I'll wait and see if another BSOD happens and check for the 122 BugCheck code. If it comes up again, would you recommend replacing the hard drive?

Thank you for your help.
 
So I just wanted to post a quick update:

Tentatively speaking, it seems my BSOD issues have vanished. It's been over a week since I have experienced any BSODs, which previously would have been enough time for at least one if not two crashes.

The only thing I can think of that resolved the issue was when I took out and then re-inserted the hard drive. Perhaps a poor connection was corrected in this manner.

I just wanted to post this update so that if anyone else is having similar issues, they may try removing and then replacing the hard drive to ensure the connection is secure.
 
Back
Top