Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD random activities, ntoskrnl.exe+253d0

02 Feb 2013   #1
aztekk

Windows 7 Ultimate x64
 
 
BSOD random activities, ntoskrnl.exe+253d0

Hi

I've started getting random BSOD's on one of out computers at home.
Windows is up to date and as far as I know, so are the drivers for everything.

I've run a quick memtest with no result and after this is posted, I'll start another one that will run for a few hours.

BlueScreenView shows nothing more to me, than an error with "ntoskrnl.exe+253d0", which tells me nothing much, so I'm hoping for you guys to find more info on this matter.

Thanks in advance!


My System SpecsSystem Spec
.
02 Feb 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Hello aztekk.

You are using a beta version of display driver.
Code:
fffff880`04a49000 fffff880`0556a000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Dec 01 08:54:02 2012 (50B97852)
    CheckSum:         00B0A675
    ImageSize:        00B21000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Unfortunately I cannot suggest you to update it to the latest WHQL, as it is known to be unstable and sometimes buggy. Better you roll it back to an earlier known stable version.
Then watch the situation. If crashes continue to occur, test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.


If it comes problem free, but still there are crashes, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

information   Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

warning   Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip   Tip


Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
02 Feb 2013   #3
aztekk

Windows 7 Ultimate x64
 
 

Thanks for a detailed reply.

I've followed all the instructions, but if Driver Verifier were active, I never got to the desktop. It gave me BSOD during windows load every time.

The computer crashed into BSOD once again now during playback of video in the browser (flash I think).

Attached is a new collection from the SF_Diagnostic_tool.
My System SpecsSystem Spec
.

02 Feb 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Code:
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
 Arguments:
Arg1: a3a039d896cc5579, Reserved
Arg2: b3b7465ee94a2463, Reserved
Arg3: fffff80002c0b510, Failure type dependent information
Arg4: 0000000000000000, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

Debugging Details:
------------------


FAULTING_IP: 
nt!_imp_NtOpenSymbolicLinkObject+8
fffff800`02c0b510 010401          add     dword ptr [rcx+rax],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x109

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02fe75d8 00000000`00000000 : 00000000`00000109 a3a039d8`96cc5579 b3b7465e`e94a2463 fffff800`02c0b510 : nt!KeBugCheckEx


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!_imp_NtOpenSymbolicLinkObject+8
fffff800`02c0b510 010401          add     dword ptr [rcx+rax],eax

SYMBOL_NAME:  nt!_imp_NtOpenSymbolicLinkObject+8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x109_0_nt!_imp_NtOpenSymbolicLinkObject+8

BUCKET_ID:  X64_0x109_0_nt!_imp_NtOpenSymbolicLinkObject+8

Followup: MachineOwner
---------
See the point 1 and point 3. It is either a device driver that is unidentified till now; or RAM.

For testing the RAM, you need to run memtest. I dont know if you have done it or not. But if you have done it, 4 hours is not enough time. You have to do it at least overnight, for 7 - 8 passes.

For driver verifier, dont select any driver provided by "microsoft" and "unknown", and let it run. Hopefully it will run, and will be able to find any cause.

Go for memtest first. It it comes clear, then and only then go for Driver Verifier.
My System SpecsSystem Spec
03 Feb 2013   #5
aztekk

Windows 7 Ultimate x64
 
 

I'm currently running memtest86 again, this time it's been running for aprox 9 hours.
Yesterday it ran for 4 hours straight ...

I'm not conviced in running much more memtesting, as I'm thinking the system wont heat up as much, compared to something GPU intensive.

Are there any good ways to stress the system and still beeing capable in producing good enought logs on eventual ellerors and crashes?

Reason is that as far as I know, flash has been running most often when the crashes occurred before.
Video and gameplay using flash and yes of course, it's Candy Crush Saga ... GF's favourite .. =/
My System SpecsSystem Spec
03 Feb 2013   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

If 9+ hours of memtest haven't showed any red lines, stop it for now, and go for driver verifier. With DV enabled, do the crash prone jobs, try to replicate the crashes.

Sometimes, there is no other way than putting the stress to determine the source of the problem. It is the most widely followed method. We stress the drivers, so that they can be recorded as the failing modules in the crash dumps, and may be identified.
My System SpecsSystem Spec
03 Feb 2013   #7
aztekk

Windows 7 Ultimate x64
 
 

Ok I'll try DV again.
Never got it to boot into desktop with it enabled, but I'll give it another go.
My System SpecsSystem Spec
03 Feb 2013   #8
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Make it sure that you are not selecting any driver provided by "microsoft" or "unknown".
My System SpecsSystem Spec
Reply

 BSOD random activities, ntoskrnl.exe+253d0




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD at random times while doing random activities
Hi, I use my computer mostly for office work and have never experienced BSOD until about a month ago when I updated my drivers. One of the drivers I updated was the audio driver that immediately began causing problems including BSOD. I rolled back the driver update and reinstalled the driver...
BSOD Help and Support
Windows 7: BSOD after win7 updates, ntoskrnl.exe+253d0
System Started getting BSOD's after a windows update with reference to the ntoskrnl.exe in every crash. I just replaced the RAM today thinking it was possibly a memory issue, but to no avail, I'm still getting frequent BSOD's. I ran an /FS SCANNOW and there were no integrity problems, as well as a...
BSOD Help and Support
BSOD during random activities on new desktop
Hello, I recently bought a new Alienware and I've had three blue screens of death since I bought it. BSOD on June 25: Bug check code 0X000000D1 Bug Check parameters 0X0000000000000000 0X0000000000000002 0x0000000000000000 0XFFFFF880018990D2 Driver iastora.sys BSOD on June 30: Bug check code...
BSOD Help and Support
BSOD + Sonar X2 + Creative Drivers + ntoskrnl.exe+253d0
Hi. I've had this BSOD occurring for quite some time now. I've contacted Cakewalk to try and nut out the problem but to no avail. It occurred on my older system and the latter initially suggested hardware. Well I built a new computer and they continue. I'd really like to find the cause of the...
BSOD Help and Support
BSOD ntoskrnl.exe+253d0 , storportsys+10d2
I've been having BSOD issues over the past week or so They Seem to happen in the early hours of the morning when im in bed. Any help would be much appreciated. LegenDSlayeR
BSOD Help and Support
BSOD after win7 updates, ntoskrnl.exe+253d0
hello, i'm new here so i hope i get this right. yesterday i get the october win7 updates, i turn off my pc and updates install, turn pc back on all good using it all last night, turn it on this aft and i get a i think a bsod, ( i wasnt in room during boot ) think it was on windows repair screen or...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 16:01.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App