Jump to content



Photo

Dpc_Watchdog_Violation crashing during W8 install...


  • Please log in to reply
8 replies to this topic

#1 Velox

Velox

    Neowinian

  • Joined: 29-September 09

Posted 28 April 2013 - 18:33

I've updated my firmware on my SSDs, burned about 10 different copies of the ISO. Tried the default MS disk that I bought for W8 System Builder. Nothing works. Some times I can make it though the install without a crash or BSOD but I'll get to "Getting Devices Ready" or 10% and it'll just stay there overnight, etc. Sometimes I get to that point and it'll BSOD again with the same dpc_watchdog_violation error.

I've unplugged all my other drives except the SSDs in RAID, I can see the drives in BIOS/UEFI and the Windows Setup. I can select them, clean em, etc and all. I just can't figure out why this keeps happening. Is it my other hardware? I have nothing plugged in except the core hardware it actually needs to run, don't even have a mouse plugged in doing it all with the keyboard.

I'm at a lost and about to throw the system out.


#2 +Livin in a box

Livin in a box

    Oh man. I shot Marvin in the face.

  • Tech Issues Solved: 2
  • Joined: 03-January 09
  • Location: Warrington, UK
  • OS: Windows 8.1
  • Phone: HTC One M8

Posted 28 April 2013 - 18:39

I've had a Google and this post goes through a couple of things you should do. I'll give you a direct link so you can look at the thread as well, better than me just copy and pasting it :)

http://www.tomshardw...lation#10478024

#3 OP Velox

Velox

    Neowinian

  • Joined: 29-September 09

Posted 28 April 2013 - 19:06

It randomly decided to install without a hitch while posting this. I'm still curious as to why it does this every single install though on this computer.

Will be monitoring it over the next few days to see if I actually BSOD now that it's installed.

And yea I've looked at that link from my googling =/.

#4 ahodgey

ahodgey

    Neowinian

  • Joined: 07-February 04
  • Location: Medway, Kent, UK
  • OS: Windows 7, Windows Server 2008 R2

Posted 28 April 2013 - 19:09

I was researching installing windows 8 on my HP Microserver and pretty sure I saw someone else having this error. They thought it was to do with the broadcom network controller. When they disabled the NIC the error stopped occuring. Might be worth a punt

#5 OP Velox

Velox

    Neowinian

  • Joined: 29-September 09

Posted 29 April 2013 - 04:59

Ok so computer just shut down no blue screen, no errors popping up just cut off and rebooted.

Checked event viewer and there's like 15 warnings all at the time frame saying the source is Ntfs. Then there's a critical error from kernel-power, etc.

http://imgur.com/cgZrsVW

#6 DKAngel

DKAngel

    That i cannot own ....I shall destroy

  • Joined: 20-July 03
  • Location: Perth, Australia

Posted 29 April 2013 - 05:12

failing psu? failing ssd's?

#7 OP Velox

Velox

    Neowinian

  • Joined: 29-September 09

Posted 29 April 2013 - 05:16

Just did a test copy to a usb just to see if it was affected as well, well it's slow as **** copying. It's saying about an hour for a 70MB file from a SSD to a USB3.0 flash drive. I know the estimated time isn't that accurate, but about an hour for it o.o

Here's a few of the errors that are listed near the top of event viewer.

kernel-pnp

The driver \Driver\WudfRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_MULTIPLE&PROD_CARD__READER&REV_1.00#058F63666438&0#.

One of the Ntfs errors

A corruption was discovered in the file system structure on volume C:.
The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x2000000025ace.  The name of the file is "\Program Files (x86)\World of Warcraft\Data\expansion2.MPQ".

Here's another one (Application Error)

Faulting application name: chrome.exe, version: 26.0.1410.64, time stamp: 0x5163bfb1
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x158c
Faulting application start time: 0x01ce4497d2839441
Faulting application path: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Faulting module path: unknown
Report Id: 10ed3366-b08b-11e2-be6d-bc5ff40d144f
Faulting package full name:
Faulting package-relative application ID:

User Profile Service error

Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.
DETAIL -
18 user registry handles leaked from \Registry\User\S-1-5-21-3467258201-3299155567-153595421-1001:
Process 724 (\Device\HarddiskVolume4\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001
Process 724 (\Device\HarddiskVolume4\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001
Process 724 (\Device\HarddiskVolume4\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001
Process 724 (\Device\HarddiskVolume4\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001
Process 392 (\Device\HarddiskVolume4\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001
Process 724 (\Device\HarddiskVolume4\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001\Software\Microsoft\SystemCertificates\trust
Process 724 (\Device\HarddiskVolume4\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001\Software\Microsoft\SystemCertificates\Root
Process 724 (\Device\HarddiskVolume4\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001\Software\Policies\Microsoft\SystemCertificates
Process 724 (\Device\HarddiskVolume4\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001\Software\Policies\Microsoft\SystemCertificates
Process 724 (\Device\HarddiskVolume4\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001\Software\Policies\Microsoft\SystemCertificates
Process 724 (\Device\HarddiskVolume4\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001\Software\Policies\Microsoft\SystemCertificates
Process 724 (\Device\HarddiskVolume4\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001\Software\Microsoft\SystemCertificates\MY
Process 724 (\Device\HarddiskVolume4\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001\Software\Microsoft\SystemCertificates\TrustedPeople
Process 392 (\Device\HarddiskVolume4\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections
Process 724 (\Device\HarddiskVolume4\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001\Software\Microsoft\SystemCertificates\CA
Process 724 (\Device\HarddiskVolume4\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001\Software\Microsoft\SystemCertificates\Disallowed
Process 1060 (\Device\HarddiskVolume4\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001\Software\Microsoft\Windows\CurrentVersion\Uninstall
Process 724 (\Device\HarddiskVolume4\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-3467258201-3299155567-153595421-1001\Software\Microsoft\SystemCertificates\SmartCardRoot


#8 Eric

Eric

    Neowinian Senior

  • Tech Issues Solved: 13
  • Joined: 02-August 06
  • Location: Greenville, SC

Posted 29 April 2013 - 13:53

Did you try replacing the drive cable?

#9 OP Velox

Velox

    Neowinian

  • Joined: 29-September 09

Posted 29 April 2013 - 14:28

No, just unplugged it and plugged it back in to make sure it was in good. Could it be as simple as a bad cable, should probably go buy one and just see.