BSOD's and my ntbtlog.txt  

Well for over this past year, I've received bsods, so I upgraded to win 7 and then nothing stirred......until I got another bsod a month after.

So soon after I did some research on rootkits,malware and malfunctions. I came to the conclusion that one of my drivers was either corrupted or out of date. Only problem is...I don't know which driver to update or how.

So when I loaded up my ntbtlog.txt, It showed the date of 6-6-2010,
my O/S and then a long list of driver reports which I don't comprehend to the slightest, so I need help interpreting it and if my bsod can be solved.


Heres the first 10lines of the log:

Microsoft (R) Windows (R) Version 6.1 (Build 7600)
6 6 2010 17:28:52.500
Loaded driver \SystemRoot\system32\ntoskrnl.exe
Loaded driver \SystemRoot\system32\halmacpi.dll
Loaded driver \SystemRoot\system32\kdcom.dll
Loaded driver \SystemRoot\system32\mcupdate_GenuineIntel.dll
Loaded driver \SystemRoot\system32\PSHED.dll
Loaded driver \SystemRoot\system32\BOOTVID.dll
Loaded driver \SystemRoot\system32\CLFS.SYS
Loaded driver \SystemRoot\system32\CI.dll

Kalinda said:

Well for over this past year, I've received bsods, so I upgraded to win 7 and then nothing stirred......until I got another bsod a month after.

So soon after I did some research on rootkits,malware and malfunctions. I came to the conclusion that one of my drivers was either corrupted or out of date. Only problem is...I don't know which driver to update or how.

So when I loaded up my ntbtlog.txt, It showed the date of 6-6-2010,
my O/S and then a long list of driver reports which I don't comprehend to the slightest, so I need help interpreting it and if my bsod can be solved.


Heres the first 10lines of the log:

Microsoft (R) Windows (R) Version 6.1 (Build 7600)
6 6 2010 17:28:52.500
Loaded driver \SystemRoot\system32\ntoskrnl.exe
Loaded driver \SystemRoot\system32\halmacpi.dll
Loaded driver \SystemRoot\system32\kdcom.dll
Loaded driver \SystemRoot\system32\mcupdate_GenuineIntel.dll
Loaded driver \SystemRoot\system32\PSHED.dll
Loaded driver \SystemRoot\system32\BOOTVID.dll
Loaded driver \SystemRoot\system32\CLFS.SYS
Loaded driver \SystemRoot\system32\CI.dll

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

OK thanks, here is my minidump and I believe its related to one of my drivers as previously stated.

Thanks for the help :)

Kalinda said:

OK thanks, here is my minidump and I believe its related to one of my drivers as previously stated.

Thanks for the help :)

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try


ALSO THESE DRIVERS NEED TO BE UPDATED AS THEY ARE OVER 10 YEARS OLD

Code:

LNE100V5.sys    10/25/2001 4:16:08 AM        0x945b1000    0x945b9d80    0x00008d80    0x3bd7ca48                        
cmaudio.sys    10/15/2002 2:03:58 AM        0x945ba000    0x94616b80    0x0005cb80    0x3dabafce                        
nvlddmkm.sys    10/10/2006 1:44:34 AM        0x94022000    0x9445b180    0x00439180    0x452b3342

Thanks for the help :P
I'm pretty sure its nvlddmkm.sys since other users had similar problems, I can update my LNE pretty soon and idc about my audio lol.
If these procedures don't succeed I'm going to follow the steps in cleaning my comp of dust and then removing each driver one by one to solve the problem.......urgh >_>
Anyways I really appreciate the help!

I followed the insturctions on how to perform the fix as said by Dwain on nVidia BSOD nvlddmkm.sys - Vista Hardware Devices

When I came to the cmd window stage I typed in "expand nvlddmkm.sy_ c:\windows\system32\drivers\nvlddmkm.sys"
and it told me the destination is not specified and I'm wondering what to enter into cmd so I can expand the .sy file into a .sys in my drivers?