KSOD - black screen after windows logo for a long time - Geeks to Go Forums

Jump to content

Log in Register Register Malware removal guide How it works

KSOD - black screen after windows logo for a long time

#1 z3255859

  • Group: Member
  • Posts: 51
  • Joined: 27-April 12

Posted 12 July 2012 - 08:07 PM

Hi folks

Recently my pc starded giving me a Black screen with interactive mouse pointer after the windows logo. I think the official term for this is KSOD ( blacK screen of Death ).

this black screen stays on for at least 3-4 minutes before i get to the welcome screen.

Not sure why this is happening. I haven't updated anything or changed anything or added anything.

I was going through my NTBTLOG.TXT and found out that my pc keeps trying to load some drivers and fails.

here are the names of a few of them :-

@nettun.inf , @netrasa.inf, @nettun.inf, @cpu.inf, @oem46.inf

I think this continuous attempt to load those drivers is causing the delay. I am attaching my ntbtlog.txt file to this post. Attached File  ntbtlog.txt (379.68K)
Number of downloads: 22

Also i got this BSOD last time logged into my pc :
-----------------------------------------------------------------------------------------------------------------------------------------------------------------

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 3081

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF88003E21E41
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\070912-30248-01.dmp
C:\Users\Sukhvir\AppData\Local\Temp\WER-116267-0.sysdata.xml
---------------------------------------------------------------------------------------------------------------------------------------------------------------

i have both those files if required.



Your help in resolving this will be highly appreciated

thanks
Report Quote Reply

#2 z3255859

  • Group: Member
  • Posts: 51
  • Joined: 27-April 12

Posted 15 July 2012 - 06:22 PM

i think i forgot to attach the ntbtlog.txt .. here it is now Attached File  ntbtlog.txt (379.68K)
Number of downloads: 20

#3 happyrock

  • Group: Moderator
  • Posts: 9,285
  • Joined: 16-May 06

Posted 18 July 2012 - 10:41 AM

have you tried updating your video card driver...

what happens if you boot into safe mode with networking

#4 anzenketh

  • Group: Technician
  • Posts: 2,849
  • Joined: 02-April 07

Posted 18 July 2012 - 11:27 AM

We need to figure out what is causing the blue screen.

Step 1
Analise the Blue Screen.
  • Please download WhoCrashed here.
  • Launch the file it downloaded to start the installation of WhoCrashed.
  • If you agree to the User Agreement please Click Accept.
  • At the finish screen of the installation make sure to Check "launch whocrashed" and click Finish.
  • Click Analyze.(The program may want to download and install a debugger please allow it to do so.)

Step 2
Post the report.
  • Scroll Down to the Section that says Analise.
  • Highlight everything Under Analise.
  • Right Click and Select copy.(Or press CTRL C)
  • Please post the report in your next reply.(Press CTRL V in the add reply window.)

#5 z3255859

  • Group: Member
  • Posts: 51
  • Joined: 27-April 12

Posted 20 July 2012 - 02:36 AM

yes i have updated my vid card driver .. no changes

safe mode with networking works fine ...no KSOD ... but i do get a BSOD after about half an hour to 1 hour of login

#6 z3255859

  • Group: Member
  • Posts: 51
  • Joined: 27-April 12

Posted 20 July 2012 - 02:37 AM

@anzenketh --- can you please send me the link again ... the current link doesn't work

#7 z3255859

  • Group: Member
  • Posts: 51
  • Joined: 27-April 12

Posted 20 July 2012 - 02:51 AM

nevermind @azenkenth ... i found the link. Here is the Analysis report:


System Information (local)
--------------------------------------------------------------------------------

computer name: SUKHVIR-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™2 Duo CPU E8400 @ 3.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4293378048 total
VM: 2147352576, free: 1913307136



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 12/07/2012 5:18:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072012-30076-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xBE (0x4140000, 0xC800000028E17025, 0xFFFFF880057E5550, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 9/07/2012 10:23:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070912-26832-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x8C6A)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF880010CFC6A, 0xFFFFF880086B9E40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 9/07/2012 10:18:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070912-27565-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0xDFECA7, 0x2, 0x0, 0xFFFFF8800FFF57BE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 9/07/2012 10:08:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070912-26535-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032A98C3, 0xFFFFF880088F99B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 9/07/2012 8:57:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070912-25599-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x9, 0x2, 0x1, 0xFFFFFA80049D2014)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 9/07/2012 8:50:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070912-37097-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x7648)
Bugcheck code: 0xD1 (0x1, 0x2, 0x1, 0xFFFFF88003D0E648)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 9/07/2012 8:10:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070912-30248-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF88003E21E41)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

7 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


#8 Shintaro

  • Group: Member
  • Posts: 55
  • Joined: 24-June 12

Posted 20 July 2012 - 04:33 AM

Are you able to upload the .dmp files?

#9 z3255859

  • Group: Member
  • Posts: 51
  • Joined: 27-April 12

Posted 20 July 2012 - 05:20 AM

my pc won't let me attach those files - it says "you don't have permission to open this file"... i tried putting them in a folder and attaching the compressed folder without any success -- it says "access denied"

#10 z3255859

  • Group: Member
  • Posts: 51
  • Joined: 27-April 12

Posted 20 July 2012 - 05:31 AM

Cancel the last post folks. I did it from the safe mode

I have attached the .dmp files in a .rar folder to this post Attached File  New folder (3).rar (357.52K)
Number of downloads: 11

#11 Shintaro

  • Group: Member
  • Posts: 55
  • Joined: 24-June 12

Posted 20 July 2012 - 06:03 AM

OK, a couple of things:
Please update the following:

speed fan

Quote

speedfan.sys Sun Sep 24 23:26:48 2006

http://www.almico.com/sfdownload.php

Razer Diamond Back mouse

Quote

DB3G.sys Mon Nov 07 17:33:11 2005

http://www.razersupp...wnloaditemid=74

Do you have a normal generic USB mouse? Just for testing.

Realtek Network card

Quote

Rt64win7.sys Thu Feb 26 20:04:13 2009

http://www.gigabyte....spx?pid=3013#dl

Is bitDefender up to date? Not just the virus pattern, but the actual software. Could you please check.

That is just a real simple look at the last mini dump.

Sorry but I have to go to bed as my daughter likes to get up at 5 am. So I'll have a more in-depth look in the morning. And look at the other mini dumps.

Hope this helps.

#12 z3255859

  • Group: Member
  • Posts: 51
  • Joined: 27-April 12

Posted 20 July 2012 - 07:39 PM

ok i was updating those drivers that you posted in the previous post and i got another BSOD ... i am attaching the .dmp file Attached File  New folder.rar (44.01K)
Number of downloads: 9

ps - yes my bit defender is up to date .. i updated it anyways just to be safe

#13 z3255859

  • Group: Member
  • Posts: 51
  • Joined: 27-April 12

Posted 20 July 2012 - 07:57 PM

ok as of now i have downloaded and updated all the drivers that you mentioned in your post

All went smoothly apart from one BSOD .. i have uploaded the .dmp file in previous post.

I still have a long black screen with a mouse pointer for about 45 - 60 sec after windows logo disappears

#14 z3255859

  • Group: Member
  • Posts: 51
  • Joined: 27-April 12

Posted 20 July 2012 - 09:19 PM

folks i was looking at the whocrashed report that i posted in one of the earlier posts and i noticed that a lot of those crashed were caused by ntoskrnl.exe

on looking this up on the internet i think this is caused by corrupt or missing boot.ini file .. and it is recommended that this file either be replaced or repaired

Is it something i should do at this stage ??

#15 Shintaro

  • Group: Member
  • Posts: 55
  • Joined: 24-June 12

Posted 20 July 2012 - 10:39 PM

Mate,

If it was ntoskrnl.exe then it is time to buy a lotto ticket.
Honestly, it is just that rare the Windows is at fault. People hang garbage on Windows all the time, but 99% of the time it is poorly written 3rd party drivers.

Since updating the drivers, how has it been? I mean after the last BSOD.
So just to clatify, the last BSOD was when you were updating the drivers? yes?

Share this topic:


  • 3 Pages +
  • 1
  • 2
  • 3