Solved Various BSOD's occouring during normal use

[KasperB]

Dear Sevenforums,

Since december I have started to experience various BSODs (not with same error codes) on my Macbook Pro running Windows 7 (see profile for hardware details). The BSODs have occured randomly during various tasks, e.g. during use of Microsoft Word or Adobe Lightroom:

- PAGE_FAULT_IN_NONPAGED_AREA 0x00000050.
- MEMORY_MANAGEMENT 0x0000001a
- SYSTEM_SERVICE_EXCEPTION 0x0000003b
- PFN_LIST_CORRUPT 0x0000004e

I did suspect my harddrive was starting to fail; a few days ago I was using Lightroom to do some photo editing, and suddenly some files seemed corrupted with weird lines and white squares all over. Furthermore, an image file that I had saved to my desktop a few days later was showing but 'could not be found' when I tried to open it, so I just deleted it. This resulted in a friend doing a harddrive test, however, without results indicating that something was failing (I have attached the test report).

Now, I'm wondering what is happening and why I do get these different BSODs. I am suspecting hardware, but I won't replace anything before it is confirmed - I am, however, surpriced if it IS caused by a hardware failure as I did expect a Macbook Pro to last a little longer than a few years.

By the way; I have replaced the default 4GB ram with 2 x 8GB (see my profile for hardware details). I did try to take one block out, not experiencing a BSOD for a few days (and so far - I have just put it back), but I do not think that it is a safe indication that it is a ram error as I have been able to run the computer for days without a BSOD occurence, and at other times it has happened very fast.

I hope that somebody is willing to help as I am pretty lost. I have attached the minidump files and the Harddrive test report.

If there is anything you want me to do, just holla - I have blueScreenView (but do not know how to interpret the data) as well as AIDA64 trial version installed.

 

[Arc]

Hi KasperB.

Yes, the bugcheck codes a varying widely, and specially with no more hint about the BSODs.

Does it happen the same with the MAC install?

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If memtest does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[KasperB]

Dear Arc,

Thank you for the quick and thorough answer.
I have now finished testing the two ram blocks with memtest86+ (which did take a while to figure out for Mac), but with fruitful results:

- Block 2, socket 2: no errors.
- Block 1, socket 1: Errors.
- Block 2, socket 1: No errors.
- Block 1, socket 2: Errors.

If I am not very wrong, that is a strong indicator that ram block 1 is faulty and that the motherboard is ok - hence, the faulty ram block might be the cause of one or more of the BSOD's that have occured. However, I wondered if it is safe to say that all BSOD's were caused by this, or if drivers would also be a cause? For instance, can one faulty ram block return such a variety of BSOD's?

 

[Arc]

Excellent Job!

With a failing RAM module, all BSODs are possible. And without removing it, no further decisions can be taken.

So remove/replace it and observe the situation. Let us know accordingly.

 

[KasperB]

Dear Arc,

I removed the faulty RAM block and decided to try to run Driver Verifier according to the steps you presented in your first answer to see if it would yield any problems. Upon the required restart to make the program start the verification process, the computer wouldn't let me boot up but returned a new BSOD and automaticly restarted. This happened two times and then I started up in safe-mode to disable Driver Verifier, which enabled me to start up normally again.

I have attached the minidump that was created (only one dump was created even though the BSOD occured two times - but it was probably the same). Do you think you can help?

 

[Arc]

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff88000c5f324, fffff98004b64ee0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\dtsoftbus01.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
[COLOR=Red]Probably caused by : dtsoftbus01.sys [/COLOR]( dtsoftbus01+1324 )

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

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Let us know the results.

 

[KasperB]

Dear Arc,

I followed your guide and uninstalled Daemon Tools. When I downloaded the standalone installer the uninstall-button was grayed out. I re-enabled Driver Verifier according to the aforementioned procedure and restartet. Upon reaching the Windows login screen a new BSOD occured. I booted up in safe-mode, deactivated Driver Verifier and booted normally again without problems.

The new minidump is attached.

One additional question: do you suggest that it is not possible to have Daemon Tools Lite installed without experiencing BSOD's? Or does it require a special install approach to make it work? What is an alternative (i.e. can I re-install Daemon Tools now or should I not do it)?

Thank you so far!

 

[Arc]

This time it catches Apple Mac HAL Driver.

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

Use !analyze -v to get detailed debugging information.

BugCheck D6, {fffff980096c3004, 1, fffff88006db9ed9, 0}

*** WARNING: Unable to verify timestamp for MacHALDriver.sys
*** ERROR: Module load completed but symbols could not be loaded for MacHALDriver.sys

Could not read faulting driver name
Probably caused by : MacHALDriver.sys ( MacHALDriver+2ed9 )

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

I would suggest you to not pay it much attention right now. Disable Driver Verifier. Run the computer normally. Let us know about any further issue.

Not only Daemon Tools, but you cannot run any disc emaluator for a long time without having BSODs. They fails, by nature.

 

[KasperB]

Dear Arc,

What is the Mac HAL driver and why should it be ignored if it creates a BSOD?

Thanks for your advice on the disc emulator software - I've noted that.

 

[Arc]

I am not very much aware about MAC hardware, but it appears to be some driver controlling the Hardware Abstruction Layer of the macbook. You can update it by updating firmware/chipset/BIOS.

Driver Verifier is very useful to point the failing drivers out. But if it catches the system drivers or something similar, we may tend to ignore it for the time being, because Driver Verifier puts a high pressure on the drivers.

Use the computer normally. If it BSODs during normal usage again, we all are here. Just post the issue.

 

[KasperB]

Thank you very much, Arc - that sounds resonable.
You have been an excellent problem-solver in this topic. I really appreciate your help! I would never have solved it had it not been with your guidance.

I encourage you to keep up the good work - that is very kind of you!
Once again, thank you.

I will now mark this topic as solved and return if anything else happens.

See you out there

 

[Arc]

You are most welcome

The fact is, it is all your hard work. I just assisted. The actual job is done by you!