Irregular BSOD

[Contour]

I've been trying to fix this error myself for around 2 weeks and have covered no ground. I'm far from an Expert but Google has very much been my friend in the past and I can't seem to find out about this error code:

0x0000003b.

From what I can tell this might be a driver issue, from what I've debugged I've got "probably caused by" ntkrnlmp.exe and with the multiple dumps all caused by a variety of processes.

I've had other stop code Errors however this one Is most persistent when using Driver Verifier.
(I hope the others appear in the dump i'm uploading also.)

Any help would be greatly appreciated and future advice would be even better since I've already got my foot in the industry but with hardware.

Thanks,

Contour.

PS. I used the seven forums diagnostics tool to upload all the information. To me it looks like it hasn't uploaded anything bar the setup file -.-

 

[Boozad]

Please follow Blue Screen of Death (BSOD) Posting Instructions, let the tool run until it has completely finished and then upload the new logs.

 

[Contour]

Okay. I'm not sure it works however i'll give it a try.
will a mini dump off of windbg suffice?

 

[Boozad]

Download the tool provided in the tutorial, run it as instructed and upload the resulting .zip file it creates on your desktop to your next post.

 

[Contour]

I'm having problems. The log collector and method 2's log collector are not zipping the results to my desktop or file path I've saved the app?

* When the log collection completes it just says its saved a file on my desktop but there is no file nor updates in any file region. just, press anything to continue and nothing...

 

[Contour]

Oh lord... it was on my other hard disk.. Sorry. here's the attached info

 

[Boozad]

OK mate, here we go.

1: This driver has been flagged and it looks to be Norton Ghost.

fffff880`076d54e0  fffff880`01199b26Unable to load image \SystemRoot\system32\DRIVERS\symsnap.sys, Win32 error 0n2
[COLOR=Red][B]*** WARNING: Unable to verify timestamp for symsnap.sys
*** ERROR: Module load completed but symbols could not be loaded for symsnap.sys[/B][/COLOR]
 symsnap+0xeb26

1: kd> lmvm symsnap
start             end                 module name
fffff880`0118b000 fffff880`011b9000   symsnap  T (no symbols)           
    Loaded symbol image file: symsnap.sys
    Image path: \SystemRoot\system32\DRIVERS\symsnap.sys
    Image name: symsnap.sys
    Timestamp:        [COLOR=Red][B]Tue Sep 15 22:02:11 2009[/B][/COLOR] (4AB000D3)
    CheckSum:         00034921
    ImageSize:        0002E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

:ar: It's very old, check for any updates for the program or uninstall completely.

2: AVG is causing multiple issues.

fffff880`076d5630  fffff880`01b52100Unable to load image \SystemRoot\system32\DRIVERS\avgmfx64.sys, Win32 error 0n2
[COLOR=Red][B]*** WARNING: Unable to verify timestamp for avgmfx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgmfx64.sys[/B][/COLOR]
 avgmfx64+0x4100

:ar: Uninstall AVG and install MS Security Essentials and MalwareBytes.

   Note

Make sure you uncheck the 'Enable Free Trial' box when installing.

3: Sonic CD/DVD driver has been flagged.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {228, fffff880011a9f74, fffffa8006823dc0, 0}

[COLOR=Red][B]*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys[/B][/COLOR]
Probably caused by : PxHlpa64.sys ( PxHlpa64+2f74 )

Followup: MachineOwner

1: kd> lmvm PxHlpa64
start             end                 module name
fffff880`011a7000 fffff880`011b3040   PxHlpa64 T (no symbols)           
    Loaded symbol image file: PxHlpa64.sys
    Image path: \SystemRoot\System32\Drivers\PxHlpa64.sys
    Image name: PxHlpa64.sys
    Timestamp:        [COLOR=Red][B]Tue Oct 20 19:08:42 2009[/B][/COLOR] (4ADDFCAA)
    CheckSum:         0001CF75
    ImageSize:        0000C040
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

:ar: This driver is used in several programs, but appears to be Roxio Creator in your case. Check for any updates for the program or uninstall completely.

 

[Contour]

Sorry Mate, fell asleep on your last post. I'll start resolving those now. Run a drive verifier after and get back to you. won't be long.

 

[Contour]

2 stop errors since I followed your last steps here's the dump.

Also, can I ask what program your using to debug these?

 

[Boozad]

Are you running Driver Verifier? If so please disable it. Your latest bugcheck is showing the Roxio Creator driver again with a STOP 0xC9, that indicates that DV has flagged that driver but we'd already ascertained that. DV isn't going to accomplish anything here. Having said that, the Roxio driver is still dated the same as in the original dumps so your update couldn't have been successful. Please uninstall Roxio Creator and test stability.

The debugging program we use is WinDBG.

 

[Contour]

I uninstalled Roxio through programs and features. From what your saying the driver has remained, could you explain how I can get rid of it or recommend any tools?

Also, when I'm past that, what program should I use for this stability test.

 

[Contour]

bump

 

[Boozad]

Sorry I've been late to reply, work has been extremely busy lately. If I can just clear a few things up we'll proceed from there.

1: Had you uninstalled Roxio prior to the last you posted?

2: Were you running Driver Verifier?

3: Have you had any more BSODs in the last few days?

4: The stability I mentioned was the general stability of your system (as in no BSODs) after uninstalling Roxio. No specific program or test is needed.

 

[Contour]

No problem, I feel bad not being on here sometimes when you reply don't worry.

Furthermore, I have uninstalled Roxio however you said after reviewing my latest dump, its still there. The driver?

It's been pretty good recently but if I run verifier I'll get the BSOD.

For the dump file I did run Verifier prior to it yes.

 

[Boozad]

OK, if the Roxio program was uninstalled prior to that dump I'm not sure why it's still showing. It may have left remnants that DV picked up but I can't confirm that 100%. I'd suggest running the system with Driver Verifier disabled and see how it goes, if you get any BSODs with DV disabled upload new logs and we'll get them looked at.

 

[Contour]

I see. Okay I'll let it run normal for the next couple of weeks and let you know how it goes. Hopefully case closed.