BSOD when disc burning and on first start up

ChazzGilbertson · Jan 15, 2014

So recently bought a new PSU, Motherboard and 8GB of more RAM. I thought the BSOD's in the past were caused by a crap PSU however I bought an 80+ Corsair one and upgraded to a Z77 MPOWER motherboard. please can someone point me in the right direction have 4 crash dumps and only turned it on yesterday!

MasterChief · Jan 15, 2014

You must rid of this old WinPcap driver file. While helping others, I was informed that is part of Intel Smart Connect, so go ahead and uninstall that. Reboot. See if the driver is then gone.

Code:

0: kd> lmvm WPRO_41_2001
start             end                 module name
fffff800`03a97000 fffff800`03aa3000   WPRO_41_2001 T (no symbols)           
    Loaded symbol image file: WPRO_41_2001.sys
    Image path: \SystemRoot\system32\drivers\WPRO_41_2001.sys
    Image name: WPRO_41_2001.sys
    Timestamp:        Mon Nov 07 16:04:48 2011 (4EB847F0)
    CheckSum:         00015ADC
    ImageSize:        0000C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Should update these to newest, if available.

Code:

0: kd> lmvm athwnx
start             end                 module name
fffff800`02ac7000 fffff800`02e50000   athwnx   T (no symbols)           
    Loaded symbol image file: athwnx.sys
    Image path: \SystemRoot\system32\DRIVERS\athwnx.sys
    Image name: athwnx.sys
    Timestamp:        Mon Apr 01 01:32:05 2013 (51591BD5)
    CheckSum:         003894D2
    ImageSize:        00389000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

0: kd> lmvm athurx
start             end                 module name
fffff800`03aa5000 fffff800`03c6d000   athurx   T (no symbols)           
    Loaded symbol image file: athurx.sys
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
    Image name: athurx.sys
    Timestamp:        Mon Jan 04 22:23:16 2010 (4B42B0A4)
    CheckSum:         001C7F92
    ImageSize:        001C8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Driver Reference Table - athurx.sys

(Use Device Manager to install.)

ChazzGilbertson · Jan 15, 2014

Sorry about the slow reply, didn't think I'd be out that long!

I've been trying to remove WPRO_41_2001.sys, I've had a look online and seen that a method is to install the latest version however that has failed to work. So i was thinking is there a way to do it manually?

****JUST REMOVED THE WPRO_41_2001.sys FILE*****

Also updated the athurx.sys driver but cant find a newer one for athwnx.sys.

Had another BSOD as well on startup, want me to upload the minidump? Seems to affect me almost definitely on a cold boot!

MasterChief · Jan 15, 2014

Yes, you can remove it manually - but - if you do not uninstall the Intel software that owns it, it will keep re-installing itself at each boot.

So, you can delete the driver, delete the reg key for it, then place a dummy file in its place.

Here's how:

Delete this file -

C:\Windows\System32\drivers\WPRO_41_2001.sys

Then open Regedit and locate its key (might take a little effort, depending on if it is named similarly, as WinPcap, or something else even) - delete the key.

Here is the location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services

Then, make a .txt file with Notepad and save it as WPRO_41_2001.txt. Change the .txt to .sys after saving. Move it to the driver folder location C:\Windows\System32\drivers, then set the Security on it to not allow write access to any account.

Reboot and see if that file is still 0 kb or not. If it is, great then.

Test the machine like this, and if it bsods (probably not) - then you can upload new crash dump(s).

Good luck.

ChazzGilbertson · Jan 16, 2014

So another day, another BSOD! I have uploaded the latest minidump for you guys to have a look at and see if you can shine some light on this very annoying problem. Like I said previously after one BSOD after a cold boot things are usually fine!

MasterChief · Jan 16, 2014

Uninstall Realtek HD Audio normally from the programs list. Delete the driver with Device Manager if still there. Reboot.

If this file still exists, delete it: C:\Windows\System32\drivers\MBfilt64.sys then delete the corresponding subkey in Regedit here:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services

Install latest HD Audio codec driver.

Uninstall whatever CD/DVD drive related software you have that owns this driver:

Code:

0: kd> lmvm pxhlpa64
start             end                 module name
fffff800`007e7000 fffff800`007f31a0   PxHlpa64   (deferred)             
    Image path: \SystemRoot\System32\Drivers\PxHlpa64.sys
    Image name: PxHlpa64.sys
    Timestamp:        Mon Oct 17 10:29:34 2011 (4E9C3BCE)
    CheckSum:         0001C018
    ImageSize:        0000C1A0
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If you don't know which it is, delete the file manually then delete the subkey in Regedit for it, like before. (Your DVD/CD drive will stop working but that is easy to fix and we will do that next, if you did this method.)

Update wireless driver from here:

Code:

0: kd> lmvm athurx
start             end                 module name
fffff800`038fe000 fffff800`03ac6000   athurx     (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
    Image name: athurx.sys
    Timestamp:        Mon Jan 04 22:23:16 2010 (4B42B0A4)
    CheckSum:         001C7F92
    ImageSize:        001C8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Drivers for Atheros AR9271 and Windows 7

If you still have any crashes at all after these things, then check your RAM settings with CPU-Z to make sure that the memory is set well. Compare SPD tab to Memory tab.

ChazzGilbertson · Jan 16, 2014

I will do the above the only problem I have is a BSOD will only happen on a cold boot so will have to turn the computer off for a while before it will happen again. Does this give you any ideas what it might be?

MasterChief · Jan 16, 2014

Let's see how it goes after things have been done, and my final two sentences from my previous post have been checked on.

ChazzGilbertson · Jan 16, 2014

So heres the latest....

I did what you have said and I have print screened the view of CPU-Z so you can check it. I also left my computer for a few hours and yes I got another BSOD so I have attached that as well. I hope we're getting closer to a solution! This problem has gone on long enough!!!!

Memory Tab

View attachment 35304

CPD Tab

View attachment 35305 View attachment 35306 View attachment 35307 View attachment 35308

MasterChief · Jan 17, 2014

CPU-Z looks good.

Athurx.sys has not been updated yet. Use Device Manager. Right click the Atheros wireless. Choose Update driver software. Browse my computer. Let me pick. Have disk. Browse.

Now navigate to where you extracted the new driver and double click on the .inf file. Click ok and continue until done.

After that is complete - if a bsod still happens - it is down to two things.

1) A stick of memory is defective (or motherboard defective) - If this is the scenario, memory is much much more likely. Suggest Memtest86+ to be ran overnight to see what it shows.

2) Some faulty hard drive. The crashes seem to be 0x24 a lot. Suggest some disk diagnostic utility to check on it/them.

If you have removable storage, then remove until issue sorted.

Code:

1: kd> .cxr ffffd000257dae70
rax=ffffc0000005f000 rbx=ffffc000001901b0 rcx=ffffe0000031ce38
rdx=0000000000000032 rsi=0000000000000000 rdi=ffffe0000031ce38
rip=fffff800009197e3 rsp=ffffd000257db8a0 rbp=0000000000000000
 r8=ffffd000257db8f0  r9=ffffd000257db900 r10=0000000000002832
r11=7ffffffffffffffc r12=ffffc00004c84b50 r13=0000000000000000
r14=0000000000000028 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
[B]Ntfs!NtfsReferenceMftView+0x83:[/B]
fffff800`009197e3 0e              ???
1: kd> kb 
  *** Stack trace for last set context - .thread/.cxr resets it
RetAddr           : Args to Child                                                           : Call Site
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsReferenceMftView+0x83

Uninstall MSI Supercharger, until sorted:

Code:

1: kd> lmvm NTIOLib_X64
start             end                 module name
fffff800`041e6000 fffff800`041ed000   NTIOLib_X64   (deferred)             
    Image path: \??\C:\Program Files (x86)\MSI\Super-Charger\NTIOLib_X64.sys
    Image name: NTIOLib_X64.sys
    Timestamp:        Thu Oct 25 06:27:58 2012 (5089142E)
    CheckSum:         00008550
    ImageSize:        00007000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

MasterChief · Jan 17, 2014

For Atheros, it might be easier for you to install as I said above, by using my attachment instead.

ChazzGilbertson · Jan 18, 2014

So I ran Memtest and on a cold boot i got loads of errors, however after that I had none. This has lead me to the conclusion I most likely have a corrupt stick of RAM. Can this be fixed or will it have to be returned. I read once you can up the voltage of the RAM and this can sometimes fix this issue?

***UPDATE***

I also updated that driver! thank you!

MasterChief · Jan 18, 2014

Contact Crucial and asked them to replace your RAM with a matched set and they will do well for ya.

You're welcome and when you get new RAM, enjoy.

(Upping voltage on RAM is really for overclocking. If you are receiving errors at stock speeds and voltage, that's something that needs to be replaced.)

BSOD when disc burning and on first start up

New Member

My Computer

Banned

My Computer

New Member

My Computer

Banned

My Computer

New Member

My Computer

Banned

My Computer

New Member

My Computer

Banned

My Computer

New Member

My Computer

Banned

My Computer

Banned

My Computer

New Member

My Computer

Banned

My Computer