📎 AI Summary:
The thread discusses a user experiencing multiple BSODs on their Windows system, likely caused by driver issues. The responder analyzes dump files, suggests updating or removing specific drivers (such as those related to mouse, network adapters, and DisplayLink), and recommends system scans and disabling problematic drivers like antivirus software. The overall sentiment is troubleshooting-focused, with advice aiming to identify and resolve driver-related causes of the BSODs.
S

Stef Havermans

New Member
Member details
Joined
Feb 4, 2016
Messages
8
Thread Author #1
I've experienced a bsod today

I know it's due to a driver fault, but i'm wondering which driver.
Anyone able to analize this for me ?

Thanks in advance
 

Attachments

Solution
kemical
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6fb40000000, 0, 0, 6}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+11b4a )

Followup: MachineOwner
Hi,
bugcheck 50 can be a nasty dump file to get:
Cause
Bug check 0x50 usually occurs after...
Click to expand...
Sort by date Sort by votes
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#2
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe0007196e060, ffffd000d30d4990, ffffe000709f2670}

Probably caused by : pci.sys

Followup: MachineOwner
Hi,
the above bugcheck means a driver reached an invalid power state. Please check your advanced power options and make sure 'Hybrid sleep' is enabled.
Driver wise nothing is mentioned in the dump although i noted these drivers:

t_mouse.sys Mon Dec 03 06:19:30 2012: iBall Advanced Mouse driver. If possible please update or if no longer required please remove.
http://www.iball.co.in/Download.aspx

tap0901.sys Thu Aug 22 13:40:01 2013: TAP-Win32 Adapter V9 or OpenVPN driver or COMODO. Any ideas as to what this is?

I notice your also running Avira AV. This is known to cause issues on the odd occasion. Try removing and just using the onboard Defender as this is ultra stable.

Please run these scans:
File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.

Post any new dump files.
 
Upvote 0 Downvote
S

Stef Havermans

New Member
Member details
Joined
Feb 4, 2016
Messages
8
Thread Author #3
I've enalbed the Hybrid Sleep option. I've also uninstalled Avira.
Sfc has no errors found. I've deleted the mouse driver and i don't quite know what the other driver does.
 
Upvote 0 Downvote
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#5
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6fb40000000, 0, 0, 6}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+11b4a )

Followup: MachineOwner
Hi,
bugcheck 50 can be a nasty dump file to get:
Cause
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.
Click to expand...
Reference

However looking through the drivers it seems I missed a possible culprit:

rsdrvx64.sys Thu Feb 12 13:01:49 2009: EldoS Corporation RawDisk Driver again please either update or remove:
Link Removed

Run a chkdsk making sure you check for and repair broken sectors:
Link Removed

If the bsod continues we'll go on and run some other tests but for now see how you go with the above.

Post any new dump files.
 
Upvote 1 Downvote
Solution
S

Stef Havermans

New Member
Member details
Joined
Feb 4, 2016
Messages
8
Thread Author #6
Diskcheck found no errors. I've replaced the keyboard of my laptop a few weeks ago could it be due to this ?
And where do i find this driver, i can't seem to find him in the devices
 

Upvote 0 Downvote
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#7
If it's just a run of the mill keyboard then it's what's termed as plug and play and the driver is within the system itself. If you installed a specific driver then it will be found in the same place as any other driver or app you want to remove.
I haven't seen any evidence to say whether it's keyboard related or not. I wanted you to remove the driver specified, or update and if the bsod re-occured then we could try the driver verifier. (depending in the bsod of course) This must be used with caution and you will need to create a recovery disk or USB. This is because sometimes the driver verifier can induce a bsod loop on start up. It doesn't always happen but if it does you can use the recovery disk/usb to boot into the recovery section and then safe mode. You will then be able to turn the verifier off and hopefully have caught our culprit in the dump file. The verifier stresses each driver in turn and if one is going to bsod then it will do so at this point. The offending driver is then captured in a dump file.
Recovery
Creating a recovery drive - Windows Help -

Driver verifier
How do I fix a Blue Screen in Windows using Driver Verifier?

Of course if you really do suspect the keyboard and can swap it for another it's always worth a try?
 
Last edited:
Upvote 0 Downvote
S

Stef Havermans

New Member
Member details
Joined
Feb 4, 2016
Messages
8
Thread Author #8
It's excactly the same keyboard. I bet it would not make a BSOD. I'm quite certain it's something with a driver but i don't know why.
 
Upvote 0 Downvote
S

Stef Havermans

New Member
Member details
Joined
Feb 4, 2016
Messages
8
Thread Author #9
Driver Verifier said a few things about DisplayLink. Deleted it immideatly. Can you find anything about it in the dumpfiles ? I think it's this driver
 
Upvote 0 Downvote
S

Stef Havermans

New Member
Member details
Joined
Feb 4, 2016
Messages
8
Thread Author #11
I didn't get any dump files. It said DRIVER VIOLATION and i got this file saying that driver verifier was unable to run due to the driver corresponding with DisplayLink. I remember certain messages used to pop up a while ago about Display Link errors, so i think this is the trouble maker
 

Attachments

Upvote 0 Downvote
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#12
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {2000, fffff801cbd9815c, 0, 306c4c44}

*** WARNING: Unable to verify timestamp for dlkmd.sys
*** ERROR: Module load completed but symbols could not be loaded for dlkmd.sys
Probably caused by : dlkmd.sys ( dlkmd+5815c )

Followup: MachineOwner
Yup the driver verifier did indeed catch a driver.

dlkmd.sys Thu Dec 10 10:59:34 2015: WDDM KMD Loader - DisplayLink Core Software
 
Upvote 0 Downvote
S

Stef Havermans

New Member
Member details
Joined
Feb 4, 2016
Messages
8
Thread Author #13
Uninstalled the whole program. Waiting for anything to pass by. I will send you anything if anything occurs. Let's hope it doesn't
 
Upvote 0 Downvote
You must log in or register to reply here.