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: Random BSOD's again, this time instantly when I started Skyrim.

27 Mar 2012   #1
Jmvars

Windows 7 Home Premium 64bit
 
 
Random BSOD's again, this time instantly when I started Skyrim.

I've had BSOD's before, they suddenly got fixed, but now I got one again.

I'm not gonna go into much detail as there really isn't much to tell, except that I recently installed the newest Nvidia driver (296.10) the CORRECT way, with safe mode and Driver Sweeper and all.

Minidump attached. I actually analysed it myself with Windows Debugging Tool and it told me it was ntoskrnl.exe that caused it.

EDIT: System specs...

Windows 7 HP 64bit SP1 OEM
MSI GF615M-P33
AMD Athlon II X4 640 @3.0Ghz
Gigabyte GeForce GTX460 768MB @860Mhz
WD Green 1TB HDD
4GB RAM, not sure of brand.
A bit over a year old system I believe.


My System SpecsSystem Spec
.
27 Mar 2012   #2
ePeen

Windows 7 Ultimate x64
 
 

Hello.

The dump provided is a 1A bugcheck, the culprit is ntkrnlmp.exe which is more than unlikely the cause of the crash, Windows just could not find the faulting driver and pointed to this in return.

Enable Driver Verifier:

Quote:
Driver Verifier:

Read the following to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.

Before enabling Driver Verifier, my recommendation is to set a backup / restore point as in severe cases Driver Verifier can break your Windows. If you have difficulty getting into Windows, boot into Safe Mode and disable Driver Verifier there.
Drivers that need to be updated:

Quote:
jswpslwfx.sys - Thu May 15 06:28:50 2008 (Atheros Security NDIS 6.0 Filter Driver (likely a D-Link device). Update here.
Dump for reference:

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\032712-18891-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0300a000 PsLoadedModuleList = 0xfffff800`0324e650
Debug session time: Tue Mar 27 16:02:29.566 2012 (UTC - 4:00)
System Uptime: 0 days 1:25:37.800
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 7a8004022a6a, 0, 0}

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 00007a8004022a6a
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88003516770 -- (.trap 0xfffff88003516770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=f8a00df832700000
rdx=fffff6fcc0136870 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000318775c rsp=fffff88003516900 rbp=0000000000000000
 r8=0000000000000001  r9=fffff800032bbb00 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!MiLogPageAccess+0xdc:
fffff800`0318775c f6462a02        test    byte ptr [rsi+2Ah],2 ds:00000000`0000002a=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000301b0be to fffff80003086d40

STACK_TEXT:  
fffff880`03516608 fffff800`0301b0be : 00000000`0000001a 00000000`00041287 00007a80`04022a6a 00000000`00000000 : nt!KeBugCheckEx
fffff880`03516610 fffff800`03084e6e : 00000000`00000000 00007a80`04022a6a 00000000`00000000 fffffa80`04056000 : nt! ?? ::FNODOBFM::`string'+0x45a35
fffff880`03516770 fffff800`0318775c : 00000000`00000000 fffffa80`04056000 fffff780`c0000000 00000000`0000beb7 : nt!KiPageFault+0x16e
fffff880`03516900 fffff800`030eb24e : 00000003`00000000 0aa00000`90475921 00000000`00000000 00000000`000098aa : nt!MiLogPageAccess+0xdc
fffff880`03516950 fffff800`03101f85 : fffff800`032bbb00 fffff880`00000001 00000000`00000001 fffff880`03516bb0 : nt! ?? ::FNODOBFM::`string'+0x21e92
fffff880`03516b00 fffff800`03070bf6 : 00000000`00001412 00000000`00000000 fffffa80`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4cd36
fffff880`03516b80 fffff800`030710ab : 00000000`00000008 fffff880`03516c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03516bd0 fffff800`03320f7a : fffffa80`03b72040 00000000`00000080 fffffa80`03b4d040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03516d40 fffff800`030779c6 : fffff880`03163180 fffffa80`03b72040 fffff880`0316dfc0 771d7fab`a9fc3efa : nt!PspSystemThreadStartup+0x5a
fffff880`03516d80 00000000`00000000 : fffff880`03517000 fffff880`03511000 fffff880`03516700 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+45a35
fffff800`0301b0be cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+45a35

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+45a35

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+45a35

Followup: MachineOwner
---------
My System SpecsSystem Spec
27 Mar 2012   #3
Jmvars

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by ePeen View Post
Hello.

The dump provided is a 1A bugcheck, the culprit is ntkrnlmp.exe which is more than unlikely the cause of the crash, Windows just could not find the faulting driver and pointed to this in return.

Enable Driver Verifier:

Quote:
Driver Verifier:

Read the following to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.

Before enabling Driver Verifier, my recommendation is to set a backup / restore point as in severe cases Driver Verifier can break your Windows. If you have difficulty getting into Windows, boot into Safe Mode and disable Driver Verifier there.
Drivers that need to be updated:

Quote:
jswpslwfx.sys - Thu May 15 06:28:50 2008 (Atheros Security NDIS 6.0 Filter Driver (likely a D-Link device). Update here.
Dump for reference:

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\032712-18891-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0300a000 PsLoadedModuleList = 0xfffff800`0324e650
Debug session time: Tue Mar 27 16:02:29.566 2012 (UTC - 4:00)
System Uptime: 0 days 1:25:37.800
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 7a8004022a6a, 0, 0}

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 00007a8004022a6a
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88003516770 -- (.trap 0xfffff88003516770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=f8a00df832700000
rdx=fffff6fcc0136870 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000318775c rsp=fffff88003516900 rbp=0000000000000000
 r8=0000000000000001  r9=fffff800032bbb00 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!MiLogPageAccess+0xdc:
fffff800`0318775c f6462a02        test    byte ptr [rsi+2Ah],2 ds:00000000`0000002a=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000301b0be to fffff80003086d40

STACK_TEXT:  
fffff880`03516608 fffff800`0301b0be : 00000000`0000001a 00000000`00041287 00007a80`04022a6a 00000000`00000000 : nt!KeBugCheckEx
fffff880`03516610 fffff800`03084e6e : 00000000`00000000 00007a80`04022a6a 00000000`00000000 fffffa80`04056000 : nt! ?? ::FNODOBFM::`string'+0x45a35
fffff880`03516770 fffff800`0318775c : 00000000`00000000 fffffa80`04056000 fffff780`c0000000 00000000`0000beb7 : nt!KiPageFault+0x16e
fffff880`03516900 fffff800`030eb24e : 00000003`00000000 0aa00000`90475921 00000000`00000000 00000000`000098aa : nt!MiLogPageAccess+0xdc
fffff880`03516950 fffff800`03101f85 : fffff800`032bbb00 fffff880`00000001 00000000`00000001 fffff880`03516bb0 : nt! ?? ::FNODOBFM::`string'+0x21e92
fffff880`03516b00 fffff800`03070bf6 : 00000000`00001412 00000000`00000000 fffffa80`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4cd36
fffff880`03516b80 fffff800`030710ab : 00000000`00000008 fffff880`03516c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03516bd0 fffff800`03320f7a : fffffa80`03b72040 00000000`00000080 fffffa80`03b4d040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03516d40 fffff800`030779c6 : fffff880`03163180 fffffa80`03b72040 fffff880`0316dfc0 771d7fab`a9fc3efa : nt!PspSystemThreadStartup+0x5a
fffff880`03516d80 00000000`00000000 : fffff880`03517000 fffff880`03511000 fffff880`03516700 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+45a35
fffff800`0301b0be cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+45a35

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+45a35

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+45a35

Followup: MachineOwner
---------
Thank you for a detailed reply. But about the D-Link device, the only D-Link device I have, (or had) is a Wireless LAN card that I removed mainly because I now have a cable and have no need for it, but also because it sucked, ALOT. Should I remove all D-Link drivers with Driver Sweeper?
My System SpecsSystem Spec
.

27 Mar 2012   #4
ePeen

Windows 7 Ultimate x64
 
 

yes, go ahead
My System SpecsSystem Spec
27 Mar 2012   #5
Jmvars

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by ePeen View Post
yes, go ahead
And about the Driver Verifier again. I don't have a possibility to backup my Windows, should I take the risk?
My System SpecsSystem Spec
27 Mar 2012   #6
ePeen

Windows 7 Ultimate x64
 
 

It usually never corrupts Windows, but there are those very rare occasions when it does. I just include that as a precaution method for people who care about those things.
My System SpecsSystem Spec
28 Mar 2012   #7
Jmvars

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by ePeen View Post
It usually never corrupts Windows, but there are those very rare occasions when it does. I just include that as a precaution method for people who care about those things.
But is it possible to easily restore Windows if I really am unlucky enough that it corrupts Windows?
My System SpecsSystem Spec
28 Mar 2012   #8
ePeen

Windows 7 Ultimate x64
 
 

With every BSOD, there is a chance of data corruption, because your system is literally going "Nope, stop, look at this driver causing problems". Sometimes, it catches it when it can write to the memory, so you don't lose anything, but sometimes it will not and you will lose everything that wasn't saved.

I really wouldn't lose sleep over it, you will be fine with enabling it.
My System SpecsSystem Spec
29 Mar 2012   #9
Jmvars

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by ePeen View Post
With every BSOD, there is a chance of data corruption, because your system is literally going "Nope, stop, look at this driver causing problems". Sometimes, it catches it when it can write to the memory, so you don't lose anything, but sometimes it will not and you will lose everything that wasn't saved.

I really wouldn't lose sleep over it, you will be fine with enabling it.
Cool I'll do it then! So I will have to expect more BSOD's because we are trying to provoke them, amirite?

Also, recently when I got home from school, I almost got a BSOD a few minutes after login. This has happened before, I just heard a small noise, like a loud electric shock, and everything just froze for half a second. After that PC was extremely slow, until I had enough and pressed the reset button.
My System SpecsSystem Spec
29 Mar 2012   #10
ePeen

Windows 7 Ultimate x64
 
 

Was this BSOD experienced after enabling Driver Verifier? If it was, attach the dump file for that BSOD.

To answer your question, in theory Driver Verifier should cause a system to BSOD much more frequently than it regularly would because regularly the faulting driver is not being stressed or accessed at the time, it's a very random process. For example, if your culprit happens to be a program that runs off of start up on the system tray, like a mounting program, or a mouse driver control panel, etc... when Windows loads, it should in theory right there force the BSOD and show the culprit, which it has done for me and others I have helped diagnose in the past plenty of times.

However, some can go a day or so without Driver Verifier forcing a BSOD as it depends on the driver fault itself.
My System SpecsSystem Spec
Reply

 Random BSOD's again, this time instantly when I started Skyrim.




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD started during Skyrim, now random
Hello forum, This is my first post here, I hope I post it so, that you will be able to help me. My computer started crashing a few days ago, in -what I believe- the same manner as it did a couple of months ago. After a long search i finally found that my SATA hard drive was connected to the 4rd...
BSOD Help and Support
BSOD playing Skyrim, 1000007E this time. New crash code each time
Playing Skyrim runs fine for at least 30 minutes before the bsod. This has happened several times, this is the most recent crash. Zip file attached.
BSOD Help and Support
Playing Skyrim,Now getting random BSOD (Serious crashes)
Hello. So i have my pc for about 7-9 Months now ,it ran fine and didnt really have problems with it.I have been playing a game (Skyrim) for 2 weeks now the 1st week it ran very smoothly and my computer never crashed but this changed the 2nd week,now when i start the game i get BSOD after playing...
BSOD Help and Support
BSOD Playing Skyrim - And During Other Random Events
Hi, Have recently had a few issues with BSOD's, The most recent one playing Skyrim. Other times from simple things as exiting Windows Media Player, Or just browsing the internet, I've tried following instructions for posting here, Hopefully I've got them correct. Hopefully someone here could...
BSOD Help and Support
BSOD Started When Playing Skyrim, now on startup.
I was playing Skyrim when it first blue screened. Soon after, it blue screened when browsing. Now, it is blue screening over and over again on start up. Any help would be awesome, thanks. -------------- Problem signature: Problem Event Name: BlueScreen OS Version: ...
BSOD Help and Support
Random Bugs All started at the same time
Yesterday after my comp was idle for about 3 hrs, I returned to do some more work and noticed a handful of bugs that weren't there before. These bugs aren't limited to Win7, but with other programs as well. 1) I am no longer able to slide the items in my taskbar. 2) In Win Mail 11, I can no...
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 07:28.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App