Hi.I get an BSOD error, poosibly due to OC'ing. But it used to be stable.

Toggle sidebar Toggle sidebar
A

arimail

Reputable
Aug 28, 2014
2
0
4,510
Hi.
I get an BSOD error, poosibly due to OC'ing. But it used to be stable. The error is as folows:

"Problemsignature:
Navn på problemhendelse: BlueScreen
OS-versjon: 6.1.7601.2.1.0.256.4
ID for nasjonal innstilling: 1044

Tilleggsinformasjon om problemet:
BCCode: 10d
BCP1: 0000000000000008
BCP2: 0000057FFC40FE28
BCP3: 0000000000000004
BCP4: FFFFFA8004B067C0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Filer som bidrar til å beskrive problemet:
C:\Windows\Minidump\082514-12636-01.dmp
C:\Users\Ari\AppData\Local\Temp\WER-138092-0.sysdata.xml

Les vår personvernerklæring på Internett:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0414

Hvis personvernerklæringen på Internett ikke er tilgjengelig, kan du lese personvernerklæringen frakoblet:
C:\windows\system32\nb-NO\erofflps.txt"
The link to the dmp file: https://www.dropbox.com/s/ti7rn9t6utjenj2/082514-12636-01.dmp?dl=0

How can I find out what the problem is
And is there any way to stabilize this? I have a Intel Q6600 Quad on a Asus P5K-E motherboard With 4GB XMS-6400 DDR2 RAM.

Thanks in advance!
-Ari
 
Solution
J
the BIOS reports its current speed of
Current Speed 16925MHz
this is a bizarre number, I would assume that the BIOS is corrupted and update the BIOS if there is a update
or reset the BIOS back to defaults and reconfigure the machine.

Also, power cycle your machine and check your real time clock to see if the settings are correct. You have a old system and the battery backup may have failed (battery on motherboard may last 5 years before it should be replaced)


Bug Check 0x10D: WDF_VIOLATION
The WDF_VIOLATION bug check has a value of 0x0000010D. This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
value of 0x8 = An operation occurred on a DMA...
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
the BIOS reports its current speed of
Current Speed 16925MHz
this is a bizarre number, I would assume that the BIOS is corrupted and update the BIOS if there is a update
or reset the BIOS back to defaults and reconfigure the machine.

Also, power cycle your machine and check your real time clock to see if the settings are correct. You have a old system and the battery backup may have failed (battery on motherboard may last 5 years before it should be replaced)


Bug Check 0x10D: WDF_VIOLATION
The WDF_VIOLATION bug check has a value of 0x0000010D. This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
value of 0x8 = An operation occurred on a DMA transaction object while it was not in the correct state.

sounds like a driver bug. let me look at the dump file and see what I can see
machine info:
BIOS Release Date 08/17/2007
Manufacturer ASUSTeK Computer INC.
Product P5K-E
Socket Designation LGA775
Processor Version Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Processor Voltage 8dh - 1.3V
External Clock 266MHz
Max Speed 3800MHz
Current Speed 16925MHz

 
Upvote 0 Downvote
Solution
A

arimail

Reputable
Aug 28, 2014
2
0
4,510
Thanks for the help!
The BIOS is updated, and the battery should be fine as I changed it2 years ago. But I'll try changing the battery. If you could look into the dmp file and look for a possible driver error I'd appreciate it! I have a feeling it might be connected to that. Is there a simple way to learn how to read into dmp files? I'm really good around (and inside) a computer, but that is something I've never taught myself.

Again thank you for Your help johnbl, I really appreciate it!

-Ari
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
you can download the windows debugger as a standalone kit that you can use to view the memory dump files.
http://msdn.microsoft.com/en-us/windows/hardware/hh852365.aspx

you then run windbg.exe and set the symbol path to microsoft's symbol server and save the configuration
http://msdl.microsoft.com/download/symbols is the location of the symbol server

problem is there are lots of commands but you can use the automatic commands
!analyze -v (does a quick automated check to see what microsoft thinks the problem is)
!for_each_module !chkimg @#ModuleName
This command will check the debug image against the true image stored on the microsoft server. Very useful when modules have been corrupted. But will show a error for all 3rd party modules that microsoft does not have.
!lmiftsm list the device drivers in alpha order with the date and timestamp. good to find out of date drivers

there are books written on how to use the debugger, way too much to tell you here.


when applied to your bugcheck you see these old 3rd party drivers. (microsoft updates their drivers via the windows update, 3rd party drivers require you to look for them and install them)





here is a list of some suspect drivers you have installed:
generally, you want to make sure you want to run them, update them if you can
some are kind of old. you have to google the driver name to find the vendor and find a update.


eubakup.sys Fri Oct 21 07:37:10 2011 (4EA18396)
EUBKMON.sys Fri Oct 21 07:37:32 2011 (4EA183AC)
eudskacs.sys Fri Oct 21 07:37:06 2011 (4EA18392)
EuFdDisk.sys Fri Oct 21 07:37:36 2011 (4EA183B0)
loopbe30.sys Sat Feb 26 11:44:49 2011
nm3.sys Wed Jun 09 17:05:51 2010

nvhda64v.sys Sun Feb 24 21:27:35 2013 (512AF647)
nvlddmkm.sys Fri Jun 21 02:06:16 2013 (51C41788)
NvStreamKms.sys Thu May 22 09:43:14 2014 (537E2922)
nvvad64v.sys Fri Mar 28 06:32:06 2014 (533579D6)
QslFsFltr.sys Thu Jul 01 08:19:53 2010 (4C2CB219)
rtl8187.sys Wed Dec 09 01:16:39 2009 (4B1F6AF7)
SbieDrv.sys Sun Jun 17 00:51:48 2012 (4FDD8C94)
VMNET.SYS Fri Jul 08 00:43:55 2011 (4E16B53B)
vmnetbridge vmnetbridge.sys Fri Jul 08 00:44:44 2011 (4E16B56C)
VMNetSrv VMNetSrv.sys Wed Jan 16 03:52:01 2008 (478DEFE1)
vmnetuserif vmnetuserif.sys Mon Apr 30 18:17:44 2012 (4F9F39B8)
vmstorfl.sys Sat Nov 20 01:57:30 2010 (4CE79B8A)
vmx86.sys Mon Apr 30 20:28:58 2012 (4F9F587A)
vstor2-mntapi10.sys Wed Apr 01 01:49:35 2009 (49D32A9F)
WsAudio_DeviceS_1_ WsAudio_DeviceS(1).sys Thu Jul 23 05:04:10 2009 (4A6851BA)
WsAudio_DeviceS_2_ WsAudio_DeviceS(2).sys Thu Jul 23 05:04:10 2009 (4A6851BA)
WsAudio_DeviceS_3_ WsAudio_DeviceS(3).sys Thu Jul 23 05:04:10 2009 (4A6851BA)
WsAudio_DeviceS_4_ WsAudio_DeviceS(4).sys Thu Jul 23 05:04:10 2009 (4A6851BA)
WsAudio_DeviceS_5_ WsAudio_DeviceS(5).sys Thu Jul 23 05:04:10 2009 (4A6851BA)
yfwaudio.sys Wed Sep 11 18:37:38 2013 (52311AE2)
yfwbus.sys Wed Sep 11 18:37:38 2013 (52311AE2)
yk62x64.sys Mon Sep 28 01:19:31 2009 (4AC07193)
ymidusbx64.sys Wed Apr 03 19:14:33 2013 (515CE209)

 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom