BSOD on brand new computer

BSOD on brand new computer. Attaching the SF_Diagnostic info here...

Things I was probably doing when it happened -
- Adobe InDesign
- Streaming music on Spotify


Thank you!

Have you applied any of the latest security updates recently? I'm asking this, since recently there has been problems with the symbol servers provided by Microsoft, as a result the symbols provided by Microsoft are outdated and old and do not correspond to the recent timestamp and kernel changes made after the security updates were released. We also means the debugger (WinDbg) will report symbol errors which can't be resolved, and the analysis of the dump files won't be able to be completed. I can't enter any commands or extensions at all!

Code:

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Attachment 289764

Could provide a screenshot like the above?

Simply type ntoskrnl.exe into the search box, and then right-click the result and select Properties.

Code:

BugCheck 24, {1904fb, fffff88008e35158, fffff88008e349b0, fffff800034ca045}

Probably caused by : hardware ( nt!ExpReleaseResourceForThreadLite+d5 )

Code:

fffff88008e35158 -- (.exr 0xfffff88008e35158)
ExceptionAddress: fffff800034ca045 (nt!ExpReleaseResourceForThreadLite+0x00000000000000d5)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 000000000293850f
Attempt to write to address 000000000293850f

Okay, there seems to be one dump file which is older than the other dump file with the symbol errors, it was created on the day after the release of Windows Updates or when the Windows Updates may have been scheduled to be installed.

Code:

0: kd> !thread
GetPointerFromAddress: unable to read from fffff8000370c000
THREAD fffffa800cdf1b50  Cid 0ab0.09b0  Teb: 000000007efa7000 Win32Thread: 0000000000000000 RUNNING on processor 0
IRP List:
    Unable to read nt!_IRP @ fffffa800fa7f010
Not impersonating
GetUlongFromAddress: unable to read from fffff8000364bba4
Owning Process            fffffa80101a7b30       Image:         msiexec.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      85428        
Context Switch Count      61             IdealProcessor: 0             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x00000000740a9d91
Stack Init fffff88008e35c70 Current fffff88008e34f70
Base fffff88008e36000 Limit fffff88008e30000 Call 0
Priority 9 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5

Code:

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

The issue seems to have been caused by a misaligned instruction pointer, which is usually caused by drivers.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

Select Individual Settings option, and then enable all the options apart from the Low Resources Simulation.

Thanks a lot, x BlueRobot! Here's the ntoskml screenshot -

I think I'm running Driver Verifier. Will report back after the 24 hours. Thanks again!

Just got first BSOD 17+ hours after enabling Driver Verifier. Should I keep running it?

I ran the driver verifier for over 36 hours. Got 2 BSOD's. Please see attachment.

Thank you!

You may disable Driver Verifier now, and sorry for the slow reply, I've been ill most of this week.

Code:

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`058cd000 fffff880`063c4000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Sep 12 06:16:00 2013 (52314E10)
    CheckSum:         00AC9E83
    ImageSize:        00AF7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Do you have the latest WHQL driver installed for your nVidia graphics card? NVIDIA Driver Downloads - Advanced Search

Version: 327.23
Release Date for Desktops and Notebooks : September 19th 2013
In Device Manager: 9.18.13.2723

Thank you so much x BlueRobot! I hope you're feeling better now.

Does this screenshot mean my graphic card driver is up to date?

Thanks I am :)

I would check the timestamp, they might be comparing it to the nVidia graphics driver, they sometimes provide through Windows Update:

Open up Device Manager, and then post a screenshot like the example below:

Attachment 290464