Locale id 4105 after new parts installed.

SmithyTix · 03 Dec 2013

I recently built a custom computer with essentially all new parts however I also started getting BSOD with the 4105 id.
The new parts were the motherboard, the CPU, and the RAM.

I just moved my 120GB SSD with my Win7 OS on it to the new case with my 1TB hard drive being just data and programs.

I know it is a driver that is causing the problem because I've used Driver Verifier and got the exact same BSOD with every non-Microsoft driver on my computer, I just don't know which driver is the problem.

I've tried updating my BIOS, my Chipset, and re-installing my Graphics Drivers/CPU Drivers, nothing seems to stop this BSOD from happening.

Also to quickly mention, the BSOD happens at random times and never in the same way twice it seems, I can be trying to open Steam and everything freezes then it goes to a crash dump and another time it is in the middle of playing a game and another is when I am just trying to open a browser window to view a file or get to the internet.

Any help is kindly appreciated and I hope I uploaded the zip file correctly, this is my first post.

SmithyTix · 04 Dec 2013

So has anyone looked at this problem? I keep getting it and I'm just burnt out from trying to figure this out on my own.

Arc · 05 Dec 2013

The Driver Verifier enabled bugcheck indicates the display driver and Daemon tools are failing, stop 0xC4; whereas teh non-DV enabled crashdumps are pointing to stop 0xF4 (so it is the main issue here), storage system related error, which is obvious as per your statement above:

I just moved my 120GB SSD with my Windows 7 OS on it to the new case with my 1TB hard drive being just data and programs.

Probably the storage controllers are missed during this operation. It is most probable, somehow obvious. You should have followed this methods: Windows 7 Installation - Transfer to a New Computer

Also make it sure that the Kingston SSD is running with the up-to-date firmware.

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. If the display related BSODs are continuing still, without DV enabled, we will concentrate on that.

_____________________________________________________________________________________

Code:

BugCheck C4, {f6, ac, fffffa800a2547f0, fffff8800f2ea879} DV Enabled

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

Followup: MachineOwner
------------------------------------------------------------------------------------------
BugCheck F4, {3, fffffa8007fb2500, fffffa8007fb27e0, fffff800031cd7b0}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

Followup: MachineOwner
-------------------------------------------------------------------------------------------
BugCheck C9, {23e, fffff88001aeb360, fffff9802e070ee0, 0} DV enabled

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

Followup: MachineOwner
---------------------------------------------------------------------------------------------
BugCheck F4, {3, fffffa8008fe48c0, fffffa8008fe4ba0, fffff80002fe17b0}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

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