BSOD's on new build, USB or NVidia suspected

J

jcward

New member
Joined
Feb 17, 2014
Posts
3
Thanks for any help, I'm :banghead:

I've attached the crash logs and info from the jcgriff2 BSOD File Collection app.

This is a recent computer build, Win 7 64-bit. As far as interesting notes:


  • Plugging in a USB peripheral into a front USB port caused the most recent crash (2/16/2014) (perhaps related?)
  • I've always had semi-reliable USB performance, especially on the front ports, but I also have some cheap USB hubs, and maybe static electricity, so I'm not sure what to make of it. I checked, and the outlet and power strip are properly grounded.
  • I've run memtest86 overnight with no problems, cpuburn, as well as video+hdd+cpu benchmarks simultaneously, so I don't think it's bad memory or under-powered.

Here are the main components:



 

Attachments

BTW, it's crashed a few times without a blue screen (so no log), usually the mouse becomes unresponsive and then it goes black. I have to power-cycle it.
 
Hi,

All of the attached DMP files are of the CRITICAL_OBJECT_TERMINATION (f4) bug check.

This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

If we look further into the dump(s), we can see:

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR: 0xF4_IOERR

What's an I/O error you may ask? An I/O error is when any hardware device (hard disk, flash drive, etc) cannot perform its basic input/output actions such as reading or copying data. When this is the case with a hard disk itself, or any storage related media, it's due to the device PHYSICALLY failing. Do note that with hard disks, the connections can be faulty as well (i.e the SATA cables from the controller on the board to the hard disk itself).

-- Also, just for information purposes, it was a process (not a thread) that unexpectedly terminated:

BugCheck F4, {3, fffffa80150d1b30, fffffa80150d1e10, fffff8000318f7b0}

3 = Process.

Code: 
2: kd> !process fffffa80150d1b30
GetPointerFromAddress: unable to read from fffff800030c2000
PROCESS fffffa80150d1b30
    SessionId: none  Cid: 024c    Peb: 7fffffdb000  ParentCid: 01c4
    DirBase: 5bba83000  ObjectTable: fffff8a008f71450  HandleCount: <Data Not Accessible>
[COLOR=#ff0000][I][B]    Image: wininit.exe[/B][/I][/COLOR]
    VadRoot fffffa80150edf70 Vads 64 Clone 0 Private 443. Modified 13. Locked 2.
    DeviceMap fffff8a000008ca0
    Token                             fffff8a000c1a060
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
    ElapsedTime                       00:00:00.000
    UserTime                          00:00:00.000
    KernelTime                        00:00:00.000
    QuotaPoolUsage[PagedPool]         0
    QuotaPoolUsage[NonPagedPool]      0
    Working Set Sizes (now,min,max)  (1312, 50, 345) (5248KB, 200KB, 1380KB)
    PeakWorkingSetSize                1312
    VirtualSize                       48 Mb
    PeakVirtualSize                   52 Mb
    PageFaultCount                    1575
    MemoryPriority                    BACKGROUND
    BasePriority                      13
    CommitCharge                      557

The specific process that terminated was winnit.exe, which is the Service Control Manager (SCM). It is a special system process under the Windows NT family of operating systems, which starts, stops and interacts with Windows service processes.


1. Ensure that SSD's firmware is 100% up to date via the manufacturer.

2. Uninstall AnyDVD.

If you're still crashing after the above (especially after ensuring the firmware is up to date), the SSD is most likely faulty.

Regards,

Patrick
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top