Random bsod

[oidualc123]

Hello, i installed s.o/drivers and some programs, randomly appear some bsod, is a desktop, here are the specs:

intel core i3 3240 cpu
4gb ram kingston
500gb hdd
msi b75ma motherboard

Pretty basic pc, i think its a driver/software issue , i hope you can help me

 

[Arc]

Hi oidualc123.

None of the crash dumps are completely recorded, unfortunately, so it is not being possible to get the needed info.

Can you take a picture of the next BSOD and supply it to us, in the hope that it will at lest let us know the bugcheck code?

 

[oidualc123]

Here is a new dump, please let me know if it works, acoording to whoscrashed:


This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800033BE728, 0xFFFFF8800623EA40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION



This was probably caused by the following module: ntfs.sys (0xFFFFF880012521BE)
Bugcheck code: 0x50 (0xFFFFFA7F89E83C73, 0x1, 0xFFFFF880012521BE, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys


I hope you can help me

 

[Arc]

0: kd> !thread
GetPointerFromAddress: unable to read from fffff800032bd000
THREAD fffffa8004c13b60  Cid 0004.0138  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 0
IRP List:
    Unable to read nt!_IRP @ fffffa8005780010
Not impersonating
GetUlongFromAddress: unable to read from fffff800031faba4
Owning Process            fffffa80036ad040       Image:         System
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      494208       
Context Switch Count      3              IdealProcessor: 1             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
[COLOR=Red]Unable to load image ElbyCDIO.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ElbyCDIO.sys
*** ERROR: Module load completed but symbols could not be loaded for ElbyCDIO.sys
Win32 Start Address ElbyCDIO (0xfffff880013e7d90)[/COLOR]
Stack Init fffff88003f06c70 Current fffff88003f06900
Base fffff88003f07000 Limit fffff88003f01000 Call 0
Priority 8 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0

Can you uninstall the program and report us the resulting situation?

• Start Menu\Programs\Elaborate Bytes\VirtualCloneDrive

 

[oidualc123]

Just when i tried to uninstall Virtual clone drive ... bsod (uninstalling an cleaning with ccleaner), hoping now works fine

 

[oidualc123]

Another bsod, according to whocrashed:

On Tue 04-02-2014 0:34:05 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 04:45:21
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF800030CB610)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
A third party driver was identified as the probable root cause of this system error.
Google query: UNEXPECTED_KERNEL_MODE_TRAP



On Mon 03-02-2014 19:48:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020314-9890-01.dmp
uptime: 03:54:39
This was probably caused by the following module: ntkrnlmp.exe (nt!KeWaitForMultipleObjects+0x278)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000308DEB0, 0xFFFFF8800355C598, 0xFFFFF8800355BDF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

here a new dump, hope you can help me

 

[Arc]

The crash dump says that the BSOD is caused by hardware.

Before checking the physical hardware, why dont we take care of the "fake" hardware at first? It should not be there till now.

ITEM|VALUE
Nombre | Virtual CloneDrive
Fabricante | Elaborate Bytes AG
Estado | Correcto
Id. de dispositivo PNP | ROOT\ SCSIADAPTER\ 0000
Controlador | c:\windows\system32\drivers\vclone.sys (5.4.7.0, 34,00 KB (34.816 bytes), 24-07-2013 11:02)

I hope you understand what I am saying.
__________________________________________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8000308deb0, fffff8800355c598, fffff8800355bdf0}

Probably caused by : hardware ( nt!KeWaitForMultipleObjects+278 )

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