Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Need help with blue screen


Best Answer RKinner , 25 January 2016 - 11:28 PM

I didn't bother parsing the dumps.  It's faster just to run Blue Screen View.  BSV shows a variety of causes.  All windows core files so probably not a driver issue.  Normally I... Go to the full post »


  • Please log in to reply

#1
brandonyuen

brandonyuen

    New Member

  • Member
  • Pip
  • 7 posts

Hi everyone,

 

I'm having trouble with blue screens and I can't figure out what the problem is. I chanced upon this forum in a search, and I really hope someone can help me with my BSOD. Thank you so much!

 

Some details:

- Running Win 7 64-bit

- minidumps attached

- speccy URL: http://speccy.pirifo...TrD0QpLOkKvWfmu

- ran memtest: no errors found

- PC has been running fine for about 5 years with the occasional blue screen, usually solved by updating video drivers or storage drivers.

- updated all drivers, but to no avail this time.

- BSODs started happening daily about a week ago... usually when I have Chrome open and I'm doing pretty memory-intensive stuff (e.g. Lightroom with large library, Chrome with >10 tabs open)

- The only change I remember making was attaching and subsequently removing a USB 3.0 extension cable. 

 

Yup, that's all I can think of now. Let me know if I can provide more information.

 

Thank you for reading this. 

 

- Brandon

Attached Files


  • 0

Advertisements


#2
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,596 posts
  • MVP

Let's run BlueScreenView

 

 
Download BlueScreenView
 
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit, Select All.
 
Go File, Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
 
Also your hard drive is reporting an awful lot of read and timeout errors.  Even tho it says Status Good it doesn't look good to me.  Make sure you backup anything you don't want to lose.

  • 0

#3
brandonyuen

brandonyuen

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

Thank you so much for your help!

 

Here's the printout from BlueScreenView:

 

==================================================
Dump File         : 012516-13478-01.dmp
Crash Time        : 25/01/2016 11:24:53 PM
Bug Check String  : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : 00000000`00000000
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : tcpip.sys
Caused By Address : tcpip.sys+56e90
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+73bd0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\012516-13478-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276,016
Dump File Time    : 25/01/2016 11:25:50 PM
==================================================
 
==================================================
Dump File         : 012416-13696-01.dmp
Crash Time        : 24/01/2016 11:46:47 PM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : 00000000`00000028
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000000
Parameter 4       : fffff800`04a339a0
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+73c00
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.19110 (win7sp1_gdr.151230-0600)
Processor         : x64
Crash Address     : ntoskrnl.exe+73c00
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\012416-13696-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276,016
Dump File Time    : 24/01/2016 11:47:44 PM
==================================================
 
==================================================
Dump File         : 012416-12979-01.dmp
Crash Time        : 24/01/2016 4:38:09 AM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : 00000000`00000040
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff800`04acf68f
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+73c00
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.19110 (win7sp1_gdr.151230-0600)
Processor         : x64
Crash Address     : ntoskrnl.exe+73c00
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\012416-12979-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276,016
Dump File Time    : 24/01/2016 8:02:58 AM
==================================================
 
==================================================
Dump File         : 012316-13072-01.dmp
Crash Time        : 23/01/2016 2:31:30 PM
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : 00000000`00000000
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000000
Parameter 4       : fffff880`01c58727
Caused By Driver  : tcpip.sys
Caused By Address : tcpip.sys+57727
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+73c00
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\012316-13072-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276,016
Dump File Time    : 23/01/2016 2:32:30 PM
==================================================
 
==================================================
Dump File         : 012316-13962-01.dmp
Crash Time        : 23/01/2016 1:00:45 PM
Bug Check String  : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x1000007e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff880`00ebd6f3
Parameter 3       : fffff880`037bd718
Parameter 4       : fffff880`037bcf70
Caused By Driver  : Wdf01000.sys
Caused By Address : Wdf01000.sys+a715
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : Wdf01000.sys+86f3
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\012316-13962-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276,016
Dump File Time    : 23/01/2016 1:12:54 PM
==================================================
 
==================================================
Dump File         : 011816-15225-01.dmp
Crash Time        : 18/01/2016 3:08:09 AM
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff800`04a7ccd8
Parameter 3       : fffff880`0c94dc00
Parameter 4       : 00000000`00000000
Caused By Driver  : Ntfs.sys
Caused By Address : Ntfs.sys+fc33
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+73c00
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\011816-15225-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276,016
Dump File Time    : 18/01/2016 3:09:33 AM
==================================================
 
==================================================
Dump File         : 011616-15709-01.dmp
Crash Time        : 16/01/2016 12:50:59 PM
Bug Check String  : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x1000007e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff880`0324ae48
Parameter 3       : fffff880`037a88e8
Parameter 4       : fffff880`037a8140
Caused By Driver  : tdx.sys
Caused By Address : tdx.sys+40fa
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : tdx.sys+3e48
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\011616-15709-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276,016
Dump File Time    : 16/01/2016 5:06:54 PM
==================================================
 
 
Did you have to parse the dumplets to see the hard disk errors? I tried to install the windows debugger but the installer had an error.... so I really really appreciate your help here.
Did it say which hard disk had timeouts? I have a 128GB SSD as my main OS disk and a 2TB HDD for data.
 
Thanks again!
 
- Brandon 

  • 0

#4
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,596 posts
  • MVP
✓  Best Answer

I didn't bother parsing the dumps.  It's faster just to run Blue Screen View.  BSV shows a variety of causes.  All windows core files so probably not a driver issue.  Normally I would say overheating or bad memory but Speccy says it's at a normal temp and you say you've checked out the memory.  I assume your windows files are on the SSD so I'm not sure of the cause.

 

The hard drive info is in the speccy log.

 

It's your 2 TB drive that looks sick.  I removed the ones which don't show errors and just left the bad ones:

 
ST2000DL003-9VT166 ATA Device
Manufacturer: 
Seagate
Heads: 
16
Cylinders: 
243,201
Tracks: 
62,016,255
Sectors: 
3,907,024,065
SATA type: 
SATA-III 6.0Gb/s
Device type: 
Fixed
ATA Standard: 
ATA8-ACS
Serial Number: 
5YD2R9Q7
Firmware Version Number: 
CC32
LBA Size: 
48-bit LBA
Power On Count: 
2731 times
Power On Time: 
510.4 days
Speed: 
5900 RPM
Features: 
S.M.A.R.T., AAM, NCQ
Max. Transfer Mode: 
SATA III 6.0Gb/s
Used Transfer Mode: 
SATA II 3.0Gb/s
Interface: 
SATA
Capacity: 
1863 GB
Real size: 
2,000,398,934,016 bytes
RAID Type: 
None
S.M.A.R.T
Status: 
Good
Temperature: 
37 °C
Temperature Range: 
OK (less than 50 °C)
S.M.A.R.T attributes
 
01
Attribute name: 
Read Error Rate
Real value: 
0
Current: 
117
Worst: 
99
Threshold: 
6
Raw Value: 
0009100900
Status: 
Good
 
0
BC
Attribute name: 
Command Timeout
Real value: 
90,195,690,382
Current: 
100
Worst: 
1
Threshold: 
0
Raw Value: 
000015038E
Status: 
Good
 
BD
Attribute name: 
High Fly Writes (WDC)
Real value: 
4
Current: 
96
Worst: 
96
Threshold: 
0
Raw Value: 
0000000004
Status: 
Good
 
 
C3
Attribute name: 
Hardware ECC Recovered
Real value: 
0
Current: 
23
Worst: 
12
Threshold: 
0
Raw Value: 
0009100900
Status: 
Good
 
 
C7
Attribute name: 
UltraDMA CRC Error Count
Real value: 
7,882
Current: 
200
Worst: 
193
Threshold: 
0
Raw Value: 
0000001ECA
Status: 
Good
 
 
 

 

 

You might want to run the extended drive test on the 2 TB using Seagate's Seatools for Windows which you can get from:

 

http://www.seagate.c...ols-win-master/

 

Normally the test takes several hours.

 

 

In the meantime:
1. Double-click My Computer, and then right-click the hard disk that you want to check. (I'm thinking C:  the first time.  But you come back and do the disk check on the 2 TB afterward.
2. Click Properties, and then click Tools.
3. Under Error-checking, click Check Now. A dialog box that shows the Check disk options is displayed,
4. Check both boxes and then click Start.
You will receive the following message:
The disk check could not be performed because the disk check utility needs exclusive access to some Windows files on the disk. These files can be accessed by restarting Windows. Do you want to schedule the disk check to occur the next time you restart the computer?
Click Yes to schedule the disk check, but don't restart yet.
 
Right click on (My) Computer and select Manage (Continue) Then the Event Viewer. Next select Windows Logs.  Right click on System and Clear Log, Clear. Repeat for Application. Reboot. The disk check will run and will probably take an hour or more to finish.
 
 
Start, All Programs, Accessories then right click on Command Prompt and Run as Administrator.  Then type (with an Enter after each line).
 
sfc /scannow
 
(SPACE after sfc.  This will check your critical system files. Does this finish without complaint?
 
 IF it says it couldn't fix everything then:
 
Copy the next two lines:
 
findstr  /c:"[SR]"  \windows\logs\cbs\cbs.log  >  \windows\logs\cbs\junk.txt 
notepad \windows\logs\cbs\junk.txt 
 
Start, All Programs, Accessories, right click on Command Prompt and Run as Administrator, Continue.  Right click and Paste or Edit then Paste and the copied line should appear.
Hit Enter if notepad does not open.  Copy and paste the text from notepad into a reply.  Close nOtepad.  Close the Command Window.
 
In either case do:
 
1. Please download the Event Viewer Tool by Vino Rosso
and save it to your Desktop:
2. Right-click VEW.exe and Run AS Administrator
3. Under 'Select log to query', select:
 
* System
4. Under 'Select type to list', select:
* Error
* Warning
 
 
Then use the 'Number of events' as follows:
 
 
1. Click the radio button for 'Number of events'
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.
 
 
Please post the Output log in your next reply then repeat but select Application. (Second time you run vew it will overwrite the first log so copy it to a reply or rename it first.)
 
 
Let's get Speedfan:
 
 
Download, save and Install it (Win 7 or Vista right click and Run As Admin.) then run it (Win 7 or Vista right click and Run As Admin)
 
It will tell you your temps in real time. (If you click on Configure then on Core you can check Show in Tray then OK  and even when minimized it will show the Core temp in the system tray (near the clock),  If you don't see it then Windows is hiding it.  Click on the up arrow to the left of the icons near the clock and  Customize.  Find Speedfan and change it to Show Icons and Notifications.  ) Leave it up and run something like a video or a scan or maybe sfc /scannow again and see if the temps climb into the 70s or higher.
 

  • 0

#5
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,596 posts
  • MVP

PS.  Bed time for me.


  • 0

#6
brandonyuen

brandonyuen

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

Thanks a million, RKinner! I didn't notice that there was so much information in BSV. I'll try those things and report back once I get back from work. 

 

Good night!

 

- Brandon


  • 0

#7
brandonyuen

brandonyuen

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

Running Speedfan now. All temps are below 50C except for "Aux", which hovers around 80C. I've read that this could be an unassigned input reporting meaningless figures, but do you know if that's likely?

 

Actually, now that I think about it, I have noticed some increased fan noise recently. Perhaps it is, indeed, overheating, as you mentioned. 

 

I'll keep monitoring the temps. And I'll check the two drives... maybe change the 2TB one soon.

 

Thanks again for your help. I'll be sure to post again once I have anything figured out.

 

- Brandon


  • 0

#8
brandonyuen

brandonyuen

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

I'm not sure I've found the cause of the blue screens yet, but I thought I'd post an update.

 

Chkdsk:

- C: drive:

Adding 454 bad clusters to the Bad Clusters File.
Write failure with status 0xc0000185 at offset 0x1dcf6ffe00 for 0x200 bytes.

The second NTFS boot sector is unwriteable.

- E: drive:

Windows has checked the file system and found no problems

 

- sfc /scannow

Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
 
- Vino's Event Viewer
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 28/01/2016 1:13:53 AM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC-&PROD_COMPACT_FLASH&REV_1.01#8&BC7C096&0&058F63646476&1#.
 
Log: 'System' Date/Time: 28/01/2016 12:56:08 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped. 
 
Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 28/01/2016 9:45:44 PM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
And then I got another couple of bluescreens, one related to HDaudio.sys and another to my sound card (Asus Xonar DG) driver. So I uninstalled the sound card driver and reinstalled it from the CD 2 days ago. No bluescreens so far, but it's still too early to tell.
 
Any idea if the error seen on my C: drive in Chkdsk is critical?
 
Thanks!
 
If I get through a week without bluescreens, I'll come back to mark this as solved. Either way, thank you very much for your time, RKinner.
 
- Brandon
 

  • 0

#9
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,596 posts
  • MVP

Not exactly what you want to see on chkdsk.  That's a lot of bad sectors.  I think if it's under warranty still you could probably get another one.  Is this the Seagate or the Samsung?  Seagate has a program that will check the drive:  Seatools for Windows

 

http://www.seagate.c...ols-win-master/

 

The extended test is what you want but with that many bad sectors it may just tell you that there is no point in running it.

 

I'd run chkdsk again to see if it is now stable or if more sectors have gone bad.


  • 0

#10
brandonyuen

brandonyuen

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

That was on the Samsung. I guess 454 is quite a lot. I don't think I still have this under warranty, so I'll have to think about getting a replacement soon, I guess.

 

Good new is, I re-ran Chkdsk and there were no new bad clusters. I'll check it again in a few days, and start shopping for a new drive at the same time. 

 

Thanks,

Brandon


  • 0

#11
brandonyuen

brandonyuen

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

I'm hesitant to post this... don't want to jinx it. But my system has been running clean with no blue screens for a week now. Looks like it may have been the audio driver. Thanks for all your help, RKinner!


  • 0

#12
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,596 posts
  • MVP

OK.  Good luck.


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP