Solved Totally Random BSOD with windows 7 64 and RIVE

[yannickhk]

So I'm back and thank you for the help given so far, it's really appreciated.

So I am running with one RAM stick now, one graphic card and everything at stock except for the RAM timing which I relaxed as instructed.

These are the voltages that you asked:
- VTT CPU 1.256V
- DRAM Voltage 1.650V

Something weird happen though, with the first RAM stick that I've tried I couldn't get passed the windows login without a BSOD or instant reboot. Now I've changed that, the PC boots up just fine. Could all of these pbs be caused by one RAM?

If need be, I can run verifier again. But last time I tried it wouldn't pass the windows logo at all and ended up with an immediate BSOD.

Edit: BTW I tried the first stick in different slots, same result.

Edit 2: Had a BSOD again, MEMORY_MANAGEMENT, so now I am running with one RAM stick from my HTPC. Those are good, I am certain of it. Been using them for a year with no problem.

 

[yannickhk]

Ok, had a couple of BSODs again so it's definitely not the RAM. I received a warning from AIDA64 b4 the latest BSOD though, saying Warning: RAM 0.050V, whatever that means.

It's got to be the MB. I mean I've tested everything else, RAM, CPU (in safe mode, PRIME95 for 5 hours).

I'm ordering a new one see if the pb persists. If it does I'm gonna throw the damn thing out the window lol

 

[zigzag3143]

Ok, had a couple of BSODs again so it's definitely not the RAM. I received a warning from AIDA64 b4 the latest BSOD though, saying Warning: RAM 0.050V, whatever that means.

It's got to be the MB. I mean I've tested everything else, RAM, CPU (in safe mode, PRIME95 for 5 hours).

I'm ordering a new one see if the pb persists. If it does I'm gonna throw the damn thing out the window lol

JMH (in post 2 ), Dave76 (in his most recent post) and I suggest you run driver verifier. Since you are convinced your ram is ok (and your not overclocking) chances are it is a driver. We wont know which till you run it.

 

[yannickhk]

Ok, but when I run verifier it doesn't get past the logon. So what should i do? The audio drivers make it crash.

Btw I've redownloaded memtest86 and it's working now. Running the 4th pass as i'm posting. No errors so far.

 

[zigzag3143]

Ok, but when I run verifier it doesn't get past the logon. So what should i do? The audio drivers make it crash.

Btw I've redownloaded memtest86 and it's working now. Running the 4th pass as i'm posting. No errors so far.

Highly likely its not memory. It doesnt need to get past logon. Upload the dmps you have.

We cant do much for you with out data. JMH, Dave76, and I have asked you to run it and until you do we cant have a definitive answer.

We have asked before.

 

[yannickhk]

Ah ok, I didn't know that I could get dmp files like that. Running verifier as instructed in the previous post right now. How long should i let it run?

 

[JMH]

Refer Posts 23 & 25.

We ARE trying to help you get you this problem corrected...
Can you help us to help you?

 

[JMH]

Ah ok, I didn't know that I could get dmp files like that. Running verifier as instructed in the previous post right now. How long should i let it run?

Refer my Post 2.
All of the necessary instructions are there.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

 

[yannickhk]

Ok, it's crashed and the bsod indicated something about a driver being verified. I'll let it crash a few times so that you'll have more than 1 dmp file.

Edit: Apparently only one dmp got created. I am attaching the corresponding file.

Should I keep trying to get into normal mode? It crashes before login.

 

[Dave76]

So I'm back and thank you for the help given so far, it's really appreciated.

So I am running with one RAM stick now, one graphic card and everything at stock except for the RAM timing which I relaxed as instructed.

These are the voltages that you asked:
- VTT CPU 1.256V
- DRAM Voltage 1.650V

Something weird happen though, with the first RAM stick that I've tried I couldn't get passed the windows login without a BSOD or instant reboot. Now I've changed that, the PC boots up just fine. Could all of these pbs be caused by one RAM?

If need be, I can run verifier again. But last time I tried it wouldn't pass the windows logo at all and ended up with an immediate BSOD.

Edit: BTW I tried the first stick in different slots, same result.

Edit 2: Had a BSOD again, MEMORY_MANAGEMENT, so now I am running with one RAM stick from my HTPC. Those are good, I am certain of it. Been using them for a year with no problem.

As already mentioned, I recommend running Driver Verifier to look for troublesome drivers.

Post the crash dump files and full BSOD Posting instruction files when you get a crash.
Blue Screen of Death (BSOD) Posting Instructions

Remove your audio drivers, check for new drivers at the Asus site. If they are the same drivers you have now, you will need to find an older driver.

When you ran the RAM test was it memtest86+?
RAM - Test with Memtest86+

After you get some Driver Verifier crash dumps, let's bring the DRAM and VTT CPU voltages down.
They are high, your CPUZ SPD tab doesn't agree with those voltages.
They might be reasonable for 16GB RAM, but for 1X4GB RAM you should lower them to see if it has any affect.
Although I haven't seen high DRAM and VTT CPU voltages cause a crash, it is worth a try.

 

[yannickhk]

As already mentioned, I recommend running Driver Verifier to look for troublesome drivers.

Post the crash dump files and full BSOD Posting instruction files when you get a crash.

Done, in my previous post

Remove your audio drivers, check for new drivers at the Asus site. If they are the same drivers you have now, you will need to find an older driver.

ok, uninstalling now.

When you ran the RAM test was it memtest86+?
RAM - Test with Memtest86+

yep, for five whole pass on 16GB, no errors found

After you get some Driver Verifier crash dumps, let's bring the DRAM and VTT CPU voltages down.
They are high, your CPUZ SPD tab doesn't agree with those voltages.
They might be reasonable for 16GB RAM, but for 1X4GB RAM you should lower them to see if it has any affect.
Although I haven't seen high DRAM and VTT CPU voltages cause a crash, it is worth a try.

Ok, on it

 

[Dave76]

STOP 0x000000C9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
Usual causes: Driver verifier
This is the bug check code for all Driver Verifier I/O Verification violations.
The driver blamed is dtsoftbus01.sys - Daemon Tools driver
Uninstall Daemon Tools, it is a known cause of BSoDs in Windows 7.

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff8801501a324, The address in the driver's code where the error was detected.
Arg3: fffffa8014eec660, IRP address.
Arg4: 0000000000000000, Status code.

Debugging Details:
------------------


BUGCHECK_STR:  0xc9_23e

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e

[COLOR="Red"]FAULTING_IP: 
dtsoftbus01+1324[/COLOR]
fffff880`1501a324 4053            push    rbx

FOLLOWUP_IP: 
dtsoftbus01+1324
fffff880`1501a324 4053            push    rbx

IRP_ADDRESS:  fffffa8014eec660

DEVICE_OBJECT: fffffa801488f730

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  fffff8000388ab80 -- (!locks fffff8000388ab80)

Resource @ nt!PiEngineLock (0xfffff8000388ab80)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
	Lock address  : 0xfffff8000388ab80
	Thread Count  : 0
	Thread address: 0x0000000000000000
	Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff80003b153dc to fffff8000368bc40

STACK_TEXT:  
fffff880`0653f868 fffff800`03b153dc : 00000000`000000c9 00000000`0000023e fffff880`1501a324 fffffa80`14eec660 : nt!KeBugCheckEx
fffff880`0653f870 fffff800`03b1f47a : fffff800`03b139f0 fffff880`1501a324 fffffa80`14eec660 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0653f8b0 fffff800`03b2034e : 00000000`0000023e 00000000`00000000 fffffa80`14eec660 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`0653f900 fffff800`03b2b71f : fffffa80`1481ea50 fffffa80`14e7fe70 fffffa80`14e7ff28 fffff880`1501e228 : nt!VfErrorReport6+0x6e
fffff880`0653f9d0 fffff800`03b2bb63 : fffffa80`14e7fe70 00000000`00000002 fffffa80`1488f730 fffff880`1501a3f4 : nt!IovpCallDriver2+0x13f
fffff880`0653fa30 fffff800`03b31c2e : fffffa80`14eec660 fffffa80`14eec660 00000000`00000002 fffffa80`1488f730 : nt!VfAfterCallDriver+0x353
fffff880`0653fa80 fffff880`00e830c2 : fffff880`00efc7c0 fffffa80`14dc3b80 00000000`00000025 fffffa80`14e7fe70 : nt!IovCallDriver+0x57e
fffff880`0653fae0 fffff880`00e9859f : fffffa80`14ee5520 00000000`00000000 fffff880`00000000 fffff880`150675d5 : Wdf01000!FxIoTarget::SubmitSync+0x24a
fffff880`0653fb90 fffff880`1507be95 : fffffa80`00000020 fffffa80`14ee5520 fffffa80`14dc3b80 00000000`00000001 : Wdf01000!imp_WdfRequestSend+0x24b
fffff880`0653fbe0 fffff880`1507c2f4 : 00000000`00000000 00000000`00000024 00000000`00000001 fffff880`0653fda0 : cdrom!DeviceSendRequestSynchronously+0xc9
fffff880`0653fc40 fffff880`1507af04 : 0000057f`eb23dfd8 fffff880`0653fda0 fffffa80`14ee3480 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x3ec
fffff880`0653fd70 fffff880`15079825 : fffffa80`00000002 fffffa80`14dc2390 fffff880`150713b8 0000057f`eb23dfd8 : cdrom!DeviceCacheDeviceInquiryData+0xbc
fffff880`0653fe40 fffff880`00eed9d4 : 00000000`00000000 fffff880`00000010 00000000`0000000c fffff880`00ef6620 : cdrom!DeviceEvtSelfManagedIoInit+0x105
fffff880`0653fe80 fffff880`00eed94e : fffffa80`14dc1c40 00000000`0000000c fffff880`00ef6620 fffff880`00ef6600 : Wdf01000!FxSelfManagedIoMachine::Init+0x34
fffff880`0653feb0 fffff880`00ee1b9b : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00ef6620 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x14a
fffff880`0653ff20 fffff880`00ee16eb : 00000000`00000312 00000000`00000000 fffff880`00ef6600 fffffa80`14f4c680 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x2f
fffff880`0653ff50 fffff880`00ee138e : fffffa80`14dc2b60 00000000`00000040 fffff880`00ef63e0 00000000`00000040 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1db
fffff880`06540080 fffff880`00ee106c : 00000000`00000000 00000000`00000040 00000000`00000501 fffffa80`14dc2b60 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`065400f0 fffff880`00eeeb5e : 00000000`00000000 00000000`00000501 00000000`00000000 00000000`00000501 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1d4
fffff880`06540180 fffff880`00eeeabb : 00000000`00000501 00000000`00000000 00000000`00000500 fffff800`03b305ec : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
fffff880`065401b0 fffff880`00eea950 : fffffa80`14dc2b60 00000000`00000001 00000000`00000000 fffff880`00ef2ff0 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x1c7
fffff880`06540230 fffff880`00eea372 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`14dc3060 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x3f8
fffff880`065402a0 fffff880`00ee6a45 : 00000000`00000000 fffffa80`14dc3060 00000000`00000108 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1e2
fffff880`06540330 fffff880`00ee6841 : 00000000`00000101 00000000`00000108 00000000`00000108 fffff800`03983556 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x111
fffff880`06540370 fffff880`00ee64fe : fffffa80`14dc2b60 fffff880`065404a0 00000000`00000004 fffff880`00ef5390 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5
fffff880`065403e0 fffff880`00ee6201 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`14dc2b60 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff880`06540450 fffff880`00eddd9c : 00000000`00000000 fffffa80`14dc2b60 00000000`00000002 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1
fffff880`065404e0 fffff880`00edcdd6 : fffffa80`13adb960 00000000`00000002 00000000`00000000 fffffa80`14dc2b60 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x20
fffff880`06540510 fffff880`00eac245 : fffffa80`14bdfc80 fffffa80`14bdfc80 fffffa80`14dc3060 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`06540580 fffff880`00eac14b : fffff880`06540668 fffffa80`14bdfc80 00000000`00000002 fffffa80`14dc3060 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`065405b0 fffff800`03b31c16 : fffffa80`14bdfc80 00000000`00000002 fffffa80`14dc3060 fffffa80`14dc3060 : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`065405f0 fffff800`03a44d6e : fffffa80`14bdfc80 fffffa80`157614a0 fffffa80`14dc3060 fffffa80`14e7e280 : nt!IovCallDriver+0x566
fffff880`06540650 fffff800`0377c87d : fffffa80`1488f730 fffffa80`157614a0 fffff800`03785fa0 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`06540690 fffff800`03a540b6 : fffff800`0388a940 fffffa80`14dbd9b0 fffffa80`157614a0 fffffa80`14dbdb58 : nt!PnpStartDevice+0x11d
fffff880`06540750 fffff800`03a54354 : fffffa80`14dbd9b0 fffffa80`0c7e002b fffffa80`0c7e2d90 00000000`00000001 : nt!PnpStartDeviceNode+0x156
fffff880`065407e0 fffff800`03a77a86 : fffffa80`14dbd9b0 fffffa80`0c7e2d90 00000000`00000002 00000000`00000000 : nt!PipProcessStartPhase1+0x74
fffff880`06540810 fffff800`03a77f3c : fffff800`03888500 00000000`00000000 00000000`00000001 fffff800`038f5814 : nt!PipProcessDevNodeTree+0x296
fffff880`06540a80 fffff800`037888c2 : 00000001`00000003 fffff800`0382c2b8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c
fffff880`06540ad0 fffff800`03696001 : fffff800`037885c0 fffff8a0`0136e901 fffff800`0382c200 fffffa80`0000055a : nt!PnpDeviceActionWorker+0x302
fffff880`06540b70 fffff800`03926fee : 00000000`00000000 fffffa80`0c7bd680 00000000`00000080 fffffa80`0c799040 : nt!ExpWorkerThread+0x111
fffff880`06540c00 fffff800`0367d5e6 : fffff880`0633b180 fffffa80`0c7bd680 fffff880`063461c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`06540c40 00000000`00000000 : fffff880`06541000 fffff880`0653b000 fffff880`0653f3b0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  dtsoftbus01+1324

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dtsoftbus01

[COLOR="Red"]IMAGE_NAME:  dtsoftbus01.sys[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  4f10358a

FAILURE_BUCKET_ID:  X64_0xc9_23e_dtsoftbus01+1324

BUCKET_ID:  X64_0xc9_23e_dtsoftbus01+1324

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

Also uninstall any ASUS utilities, for testing purposes, these are also known to cause BSoDs in Windows 7.

There are a lot listed on your motherboard site, for testing I would un-install all of them, once the system is stable you can re-install them, if you want, one at a time, testing for stability after each install.
This is the best way to find the utility that is causing problems.

 

[yannickhk]

I did everything that you said and tried to boot into normal mode and had a BSOD again (verifier running).

I'm attaching the dump file.

BTW thank you all for your patience, I'm usually not that obtuse when it gets to computers but this random bsods pb is really beyond my skills.

Edit: Oops, posted at the same time. Removing DT and asus utilities right now

 

[yannickhk]

Ok, everything has been uninstalled. Running verifier again.

 

[Dave76]

The crash is the same as the last one STOP 0x000000C9: DRIVER_VERIFIER_IOMANAGER_VIOLATION

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff880152d3324, The address in the driver's code where the error was detected.
Arg3: fffffa8014fdac60, IRP address.
Arg4: 0000000000000000, Status code.

Debugging Details:
------------------
[COLOR="Red"]MODULE_NAME: dtsoftbus01

IMAGE_NAME:  dtsoftbus01.sys[/COLOR]

Post the crash files after you finish removing Daemon Tools and Asus utilities.

 

[yannickhk]

Ok, I uninstalled everything that you told me to and had another BSOD.

dmp attached

Edit: on another note, Dave did you make your banner yourself? It rocks

 

[Dave76]

This crash is STOP 0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
Usual causes: Device driver - see parameters for more information
The crash is blamed on the bdfm.sys driver - Bit Defender
Uninstall Bit Defender, follow the steps in this link.
Download and save the BitDefender Uninstall Tool

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 000000000000072c, Handle value being referenced.
Arg3: fffffa8014456b30, Address of the current process.
Arg4: fffff88012794651, Address inside the driver that is performing the incorrect reference.

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

[COLOR="red"]PROCESS_NAME:  userinit.exe[/COLOR]

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003b143dc to fffff8000368ac40

STACK_TEXT:  
fffff880`0da2b658 fffff800`03b143dc : 00000000`000000c4 00000000`000000f6 00000000`0000072c fffffa80`14456b30 : nt!KeBugCheckEx
fffff880`0da2b660 fffff800`03b29ae4 : 00000000`0000072c fffffa80`14456b30 00000000`00000004 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0da2b6a0 fffff800`038e2210 : 00000000`00000000 fffff880`0da2b910 fffff880`0da2ba00 00000000`00002000 : nt!VfCheckUserHandle+0x1b4
fffff880`0da2b780 fffff800`03983118 : fffff880`0da2bd00 00000000`00000008 fffffa80`0c738860 fffffa80`0c738800 : nt! ?? ::NNGAKEGL::`string'+0x212ce
fffff880`0da2b850 fffff800`03689ed3 : 00000000`0000072c fffff880`0da2bd30 00000000`00000000 fffff880`0da2bc78 : nt!NtAllocateVirtualMemory+0x9c8
fffff880`0da2b9f0 fffff800`03686470 : fffff800`03b1b05a fffff880`0da2bcb0 fffff800`03686470 00000000`00000010 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0da2bbf8 fffff800`03b1b05a : fffff880`0da2bcb0 fffff800`03686470 00000000`00000010 00000000`00000086 : nt!KiServiceLinkage
fffff880`0da2bc00 fffff880`12794651 : fffffa80`15a08010 00000000`00000d44 fffffa80`162e23b0 00000000`c0000001 : nt!VfZwAllocateVirtualMemory+0x6a
fffff880`0da2bc40 fffffa80`15a08010 : 00000000`00000d44 fffffa80`162e23b0 00000000`c0000001 fffff880`00002000 : bdfm+0xe651
fffff880`0da2bc48 00000000`00000d44 : fffffa80`162e23b0 00000000`c0000001 fffff880`00002000 fffff880`00000040 : 0xfffffa80`15a08010
fffff880`0da2bc50 fffffa80`162e23b0 : 00000000`c0000001 fffff880`00002000 fffff880`00000040 fffff880`00000000 : 0xd44
fffff880`0da2bc58 00000000`c0000001 : fffff880`00002000 fffff880`00000040 fffff880`00000000 00000000`00000800 : 0xfffffa80`162e23b0
fffff880`0da2bc60 fffff880`00002000 : fffff880`00000040 fffff880`00000000 00000000`00000800 00000000`00000000 : 0xc0000001
fffff880`0da2bc68 fffff880`00000040 : fffff880`00000000 00000000`00000800 00000000`00000000 fffffa80`15a08010 : 0xfffff880`00002000
fffff880`0da2bc70 fffff880`00000000 : 00000000`00000800 00000000`00000000 fffffa80`15a08010 fffffa80`162e23b0 : 0xfffff880`00000040
fffff880`0da2bc78 00000000`00000800 : 00000000`00000000 fffffa80`15a08010 fffffa80`162e23b0 00000000`00000000 : 0xfffff880`00000000
fffff880`0da2bc80 00000000`00000000 : fffffa80`15a08010 fffffa80`162e23b0 00000000`00000000 00000000`00000e7c : 0x800


STACK_COMMAND:  kb

FOLLOWUP_IP: 
bdfm+e651
fffff880`12794651 8bf8            mov     edi,eax

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  bdfm+e651

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: bdfm

[COLOR="Red"]IMAGE_NAME:  bdfm.sys[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  4bd04d31

FAILURE_BUCKET_ID:  X64_0xc4_f6_bdfm+e651

BUCKET_ID:  X64_0xc4_f6_bdfm+e651

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

Yes I made the sig, thanks for the compliment.


Keep posting the crash dumps, we'll get the suspect drivers removed.

 

[yannickhk]

So should I uninstall bitdefender too? Darn, I just bought it

Edit: I should really take more time to read your posts, sorry about that. Uninstalling now.

 

[Dave76]

Un-install it for testing purposes.
See my last post, updated, run the Bit Defender uninstaller.

You can re-install later if you want.

All programs that we un-install now may or may not be responsible for your crashes. Some of them will be causing issues.
When your system is stable, you can install them one at a time and check for stability. Then you will know who the culprit is.

Edit:
That's ok, I usually edit posts with more/other information as I find it, if there isn't a reply yet.

 

[yannickhk]

Ok, I was able to boot into normal mode. When I type verifier /query a cmd window opens for a couple of secs, goes through a lot of lines and shuts off. That normal?