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: Sporadic BSOD on a new build, varying bug check codes

24 Jul 2013   #1
r021

Windows 7 Professional x64
 
 
Sporadic BSOD on a new build, varying bug check codes

Hey everyone,

I'm on a new build and I keep experiencing random BSODs. There doesn't seem to be any single event that triggers them. They've happened playing a game, exiting a game, watching a video, browsing windows, doing nothing, etc.

I've tried re-seating my memory, video card, etc. as well as double-checking all cords and plugs. This didn't seem to help.

Any other information that you need to know I would be happy to provide.

Any help would be very much appreciated. Thank you.


My System SpecsSystem Spec
.
25 Jul 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Out of three crash dump, the earliest one shows Linksys WMP600N Wireless-N PCI Adapter with Dual-Band driver as teh failing element.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffac15164b040, 2, 0, fffff8800581b114}

*** WARNING: Unable to verify timestamp for netr28x.sys
*** ERROR: Module load completed but symbols could not be loaded for netr28x.sys
Probably caused by : netr28x.sys ( netr28x+1b114 )

Followup: MachineOwner
---------
And th driver is very old.
Code:
fffff880`05800000 fffff880`0589f000   netr28x  T (no symbols)           
    Loaded symbol image file: netr28x.sys
    Image path: \SystemRoot\system32\DRIVERS\netr28x.sys
    Image name: netr28x.sys
    Timestamp:        Thu Feb 26 08:32:09 2009 (49A60631)
    CheckSum:         000A3BDB
    ImageSize:        0009F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Search for an update here. If you dont find any latest update, you may need to plan to change the adapter.

Which antivirus do you use?

Let us know the results.
_________________________________________________________________________________
BSOD ANALYSIS:
Code:
BugCheck D1, {fffffac15164b040, 2, 0, fffff8800581b114}

*** WARNING: Unable to verify timestamp for netr28x.sys
*** ERROR: Module load completed but symbols could not be loaded for netr28x.sys
Probably caused by : netr28x.sys ( netr28x+1b114 )

Followup: MachineOwner
------------------------------------------------------------------------------------------
BugCheck 1E, {ffffffffc0000005, fffff800032b053a, 0, ffffffffffffffff}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

Followup: MachineOwner
-------------------------------------------------------------------------------
BugCheck 1A, {3452, 16bce000, fffff700010d32a8, b8700002cf231c66}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35163 )

Followup: MachineOwner
---------
My System SpecsSystem Spec
25 Jul 2013   #3
r021

Windows 7 Professional x64
 
 

Hi Arc, thank you for the reply.

Working on updating my wireless card's drivers right now.

I'm using Microsoft Security Essentials and Malwarebytes for anti-virus at the moment.

I also have a quick question. Although the first crash shows that netr28x.sys was one of the causes, all three crashes were caused by ntoskrnl.exe. What can I do to resolve this issue?

Thank you very much for your help
My System SpecsSystem Spec
.

25 Jul 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by r021 View Post

I also have a quick question. Although the first crash shows that netr28x.sys was one of the causes, all three crashes were caused by ntoskrnl.exe. What can I do to resolve this issue?
ntoskrnl.exe is the system kernel on which it crashed. When the dump recording mechanism cannot find the exact issue, it blames the kernel. It is not any issue itself, but something undetermined.

If after adjusting the driver, there are further BSODs blamingntoskrnl.exe, then we will take further steps to troubleshoot that issue.... will try to find out the causes.

But as far aswe have a known cause, we have to do the needful for it. So after updating the driver let the computer run normally. Let us know how it is running. If there are any more BSODs, post following BSOD posting instructions.
My System SpecsSystem Spec
25 Jul 2013   #5
r021

Windows 7 Professional x64
 
 

I've updated my wireless card to the latest driver and ran a virus scan just to be safe. The driver installed properly and the virus scan turned up nothing. My computer had another blue-screen a little while later after that while just browsing the web.

I have attached an updated set of diagnostic logs. There are 2 new crashes. 072413-15693-01.dmp occurred last night before I updated my wireless drivers. 072513-16380-01.dmp is the most recent BSOD which occured after my wireless driver update.

Thank you for the help.
My System SpecsSystem Spec
25 Jul 2013   #6
r021

Windows 7 Professional x64
 
 

attached
My System SpecsSystem Spec
25 Jul 2013   #7
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by r021 View Post
attached
Your crash dumps are not showing any finite probable cause.

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 memtest comes free from errors, 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. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
____________________________________________________________________
BSOD ANALYSIS:
Code:
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5003, fffff70001080000, a367, a209000147ce}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2984f )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 000000000000a367
Arg4: 0000a209000147ce

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


BUGCHECK_STR:  0x1a_5003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800032eb4dc to fffff80003282c00

STACK_TEXT:  
fffff880`0af21888 fffff800`032eb4dc : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`0000a367 : nt!KeBugCheckEx
fffff880`0af21890 fffff800`0328f3fe : 00000000`00000001 00000000`05cd0000 fffff880`0af21ae0 fffff680`0002e680 : nt! ?? ::FNODOBFM::`string'+0x2984f
fffff880`0af21980 fffff800`03280d2e : 00000000`00000001 00000000`05cd0000 00000000`0efadf01 00000000`05c7b8d0 : nt!MmAccessFault+0x5de
fffff880`0af21ae0 000007fe`ff5e5907 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0efae498 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`ff5e5907


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+2984f
fffff800`032eb4dc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2984f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2984f

BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2984f

Followup: MachineOwner
---------
My System SpecsSystem Spec
25 Jul 2013   #8
r021

Windows 7 Professional x64
 
 

I will go through these steps and get back to you with the results. Thank you for the help, Arc.
My System SpecsSystem Spec
26 Jul 2013   #9
r021

Windows 7 Professional x64
 
 

I ran Memtest for 8 passes and got zero errors.

I the ran the Driver Verifier and got 2 BSOD crashes. The logs are attached.
My System SpecsSystem Spec
26 Jul 2013   #10
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Verifier is properly enabled. But still, the dump is not pointing the failing module rightly. It just says that wifi is the problem.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C1, {fffff9801c41af30, fffff9801c41acd0, 5d40d8, 32}

Probably caused by : nwifi.sys ( nwifi!WPP_SF_dll+40e )

Followup: MachineOwner
---------
Your wifi adapter is Linksys WMP600N Wireless-N PCI Adapter with Dual-Band, which I suggested to update earlier. You have done, too. But the update is not an advancement in true sense.
Code:
fffff880`06835000 fffff880`069f5000   netr28x    (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\netr28x.sys
    Image name: netr28x.sys
    Timestamp:        Mon Nov 14 21:22:43 2011 (4EC1394B)
    CheckSum:         001BC9A4
    ImageSize:        001C0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
If you cannot have updates those are updates in true sense, you may need to opt for changing the wifi adapter.

Another one ... that is also DV enabled .... is not saying anything in particular, but gives a hint of display failure.
Code:
fffff880`0391d158  fffff880`05ada1e8Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xb91e8
The display driver is of the latest version.
Code:
fffff880`05a21000 fffff880`06506000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Jun 21 14:36:16 2013 (51C41788)
    CheckSum:         00AB87FF
    ImageSize:        00AE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
And it is not very widely reported as failing. So for display troubleshooting, we we will pay attention to the driver at last. Do those checks now .....

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
At least 30% free is safe. Also let us know about the wattage of the PSU.

BTW, on a serious note .... Steam, online games ... cause both network and display related BSODs, extensively. Those are inherent in the process. If windows based troubleshooting cannot lead to a real direction (as most of the crashes are while using steam; PROCESS_NAME: Steam.exe) you may ask for some right settings and patches for steam from the developers of the program. It worked for many of them having similar issues. Steam is problematic, and in cases it is beyond troubleshooting in normal course.
My System SpecsSystem Spec
Reply

 Sporadic BSOD on a new build, varying bug check codes




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD, multiple bug check codes
I bought a new motherboard and processor yesterday and the guys at the shop installed it, but it blue screens a lot after I got it back, sometimes it doesn't even load into windows and I have to restart it a couple of times before it goes into windows, the guys at the shop thought the solid state...
BSOD Help and Support
BSODs, varying codes
Last week I received new mem for my computer, going from 4 (2x2) to 12 (2x2 + 2x4) GB. After installing the new memory, I started receiving BSOD's and my computer crashed frequently or just failed to boot (stuck at windows loading). Turns out the new memory was DOA (memtest confirmed this). ...
BSOD Help and Support
Constant BSOD over the past two week, varying error codes
Hello, About every other boot, I get a BSOD for one reason or another. Sometimes, no BSOD will show up, but the comp. will loop through the welcome screen, meaning the welcome screen will show but will not displays user accounts and then it will turn black and back to the welcome screen again. ...
BSOD Help and Support
BSOD with varying stop codes daily
Hi I've been having random BSODs for over a month now. Ive run various diagnostics: memtest86 scannowsfc driver verifier no errors. I ran chkdsk on my HDD's no errors but the BSOD's won't stop. I have noticed recently that if a play any video in my web browser, either flash player crashes,...
BSOD Help and Support
BSOD Randomly. Varying error codes.
I get BSODs randomly throughout the day around 4-5 times in a span of 12 hours. The error codes vary from stop errors and error 0x000003b, etc. Thanks in advance for your help!
BSOD Help and Support
BSOD Error check codes 0xa and 0x7f
Hi I'm hoping someone can with a BSOD problem that only seems to occur when using Serif MoviePlusX3. So far it has happened twice today and once last week. The first twice appear to have different causes to one this afternoon. I WAS hoping to find a solution from other peoples experiences but...
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 17:30.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App