BSOD only started recently after changing DVD Drive Model - am lost...

badler · 10 Jul 2013

Hi, I enabled as you suggested and have had a BSOD today, new updated log files attached, any next suggested changes?

x BlueRobot · 10 Jul 2013

BSOD Analysis:

Code:

BugCheck A, {58, 2, 1, fffff800030930d8}

Probably caused by : ksthunk.sys ( ksthunk!CKernelFilterDevice::DeferIrpCompletion+12 )

Code:

Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Code:

0: kd> k
Child-SP          RetAddr           Call Site
fffff880`054db218 fffff800`030841a9 nt!KeBugCheckEx
fffff880`054db220 fffff800`03082e20 nt!KiBugCheckDispatch+0x69
fffff880`054db360 fffff800`030930d8 nt!KiPageFault+0x260
fffff880`054db4f0 fffff800`03089578 nt!KiTryUnwaitThread+0x28
fffff880`054db550 fffff880`0400062e nt!KeSetEvent+0x446 
fffff880`054db5c0 fffff800`035306e6 ksthunk!CKernelFilterDevice::DeferIrpCompletion+0x12
fffff880`054db5f0 fffff800`030885c1 nt!IovpLocalCompletionRoutine+0x166
fffff880`054db650 fffff800`035282af nt!IopfCompleteRequest+0x341
fffff880`054db740 fffff880`0400094c nt!IovCompleteRequest+0x19f
fffff880`054db810 fffff800`0352ed26 ksthunk!CKernelFilterDevice::DispatchIrp+0x244
fffff880`054db870 fffff800`033a2f37 nt!IovCallDriver+0x566
fffff880`054db8d0 fffff800`033a3796 nt!IopXxxControlFile+0x607
fffff880`054dba00 fffff800`03083e93 nt!NtDeviceIoControlFile+0x56
fffff880`054dba70 00000000`76ff138a nt!KiSystemServiceCopyEnd+0x13
00000000`0088df18 00000000`00000000 0x76ff138a

There's not much I could gather from the crash, apart a little information about what call routine it crashed on, I'm guessing that a thread was placed in a wait state to allow a device driver to complete some I/O operations. The thread is meant to be notified, when the I/O routines have finished with an Event Object. The nt!KeSetEvent is called to set the event object to signaled, which enables the thread to leave the wait thread and continue. I'm guessing that the thread never left the wait state, hence the nt!KiTryUnwaitThread.

---------------------------------------------------------------------------------------

How long has Driver Verifier been running for?

Scan for any missing, modified or corrupted protected Windows files with:

SFC /SCANNOW Command - System File Checker

badler · 21 Jul 2013

Hi,

I had blue screens continuously so I decided to format my C drive and load a fresh version of windows. Was good for a few days but another BSOD. Have enabled driver verifier since the crash. Can you review the attached and see if tells you anything? Am tempted to take my PC back or try a 32 bit version of windows 7 as the constant BSOD is very frustrating. thanks

Arc · 21 Jul 2013

Download and install Samsung Magician. Make it sure that your SAMSUNG SSD 830 is running with the up-to-date firmware version.

Also, try using the AHCI mode of storage controller in the BIOS.

EDIT: Also uninstall SyncBack Pro, at least as a test.

x BlueRobot · 21 Jul 2013

Code:

BugCheck 51, {1, fffff8a00014f010, 140a6000, 465}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+37285 )

Code:

Usual causes:  Hardware failure, File system corruption, Security issues

This bugcheck generally indicates that a issue has occurred with the registry, there seems to be most likely a few I/O errors with the registry.

Code:

0: kd> k
Child-SP          RetAddr           Call Site
fffff880`0560c668 fffff800`031c3785 nt!KeBugCheckEx
fffff880`0560c670 fffff800`031dec13 nt! ?? ::NNGAKEGL::`string'+0x37285
fffff880`0560c6f0 fffff800`030f1326 nt! ?? ::NNGAKEGL::`string'+0x5656b
fffff880`0560c7e0 fffff800`032f841d nt!CmpInitHiveFromFile+0x246
fffff880`0560c930 fffff800`03114ede nt!CmpLoadHiveThread+0x14d
fffff880`0560cc00 fffff800`02e67906 nt!PspSystemThreadStartup+0x5a
fffff880`0560cc40 00000000`00000000 nt!KiStartSystemThread+0x16

In addition, to the others suggestions, what hard-drive diagnostics and other hardware troubleshooting have you completed?

Arc · 21 Jul 2013

Harry, we should concentrate on the SSD first, as it is the C drive itself.
Drive C:
Size 119.14 GB (127,928,365,056 bytes)

And ....
Model SAMSUNG SSD 830
Size 119.24 GB (128,034,708,480 bytes)

SSDs better not to put in hardware troubleshooting, other than the SMART monitoring programs like CrystalDiscInfo or SSDLife.

badler · 21 Jul 2013

Hi, I have run all hardware diagnostics suggested in the thread by Arc, including the video card, memory etc and they all show no errors. I am starting to wonder if the new DVD player which was installed has caused some issue as this only all started happening since the dvd drive was replaced, up until then with the same s/w and h/w I have never had a BSOD.

badler · 21 Jul 2013

Syncbackpro has been uninstalled, BIOS and windows updated to use AHCI mode of storage controller. Samsung SSD is running latest version of the BIOS according to Samsung Magician. Any other suggestions or just give it a while since if it BSOD again?

Arc · 21 Jul 2013

Do one more thing, to make it sure that there is no security issue. Scan the system for possible virus infection with the following programs.

And then wait and observe. If still it BSODs and gives Ntfs.sys as probable cause, the next steps would be to replace the SATA and power cables, using another SATA port on the motherboard.

But if still it goes in the same way, it would be better to decide that the problem is coming from the SSD itself.

BTW, is the power cables got any share between the SSD and the DVD drive? Check it and let us know.

badler · 06 Aug 2013

Hi,

I took the PC back (under warranty) and no hardware issues found. Checked and the drive is not sharing a power cable.

interesting that the PC blue screened when I took it into the store.

I have attached another dump file as now it is complaining about a realtek driver which I have ensured is the latest driver. I am still lost, have tried reloading windows 7 64 bit.

Would I be better off loading the 32 bit version - is this more stable?

Thanks,

Brendon.