Multiple BSOD errors, Unknown Cause

jeffpkamp · Aug 1, 2013

Had BSODs about every hour a month ago, then nothing for a month and now three in a day. The error messages are different this time...

I disabled all my CPU features in bios, and that appears to have slowed the problem, but I would like a more precise approach to finding the root problem. Thanks for help in advance.

Attached is all the diagnostic files you could want, let me know if there is anything else needed.

YoYo155 · Aug 1, 2013

Bugcheck:

Code:

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000000000004, A NULL parameter was passed to a function that required a non-
    NULL value.
Arg2: 0000000000000000, Reserved.
Arg3: [COLOR=RoyalBlue][B]fffff880061be6a0[/B][/COLOR], The caller's address.
Arg4: fffffa8003f08c10, Reserved.

Driver at fault:

Code:

Probably caused by : [U][B][COLOR=Red]ser2pl64.sys[/COLOR][/B][/U] ( ser2pl64+86a0 )

Confirmation:

Code:

ln /D [B][COLOR=RoyalBlue]fffff880061be6a0[/COLOR][/B]
Browse module
Set bu breakpoint

1: kd> lmDva 0xfffff880`061be6a0
Browse full module list
start             end                 module name
fffff880`061b6000 fffff880`061d5000   ser2pl64 T (no symbols)           
    Loaded symbol image file: ser2pl64.sys
    Image path: \SystemRoot\system32\DRIVERS\[COLOR=Red][U][B]ser2pl64.sys[/B][/U][/COLOR]
    Image name: ser2pl64.sys

Time Stamp:

Code:

lmvm ser2pl64
start             end                 module name
fffff880`061b6000 fffff880`061d5000   ser2pl64 T (no symbols)           
    Loaded symbol image file: ser2pl64.sys
    Image path: \SystemRoot\system32\DRIVERS\ser2pl64.sys
    Image name: ser2pl64.sys
    Timestamp:        [COLOR=Red][U][B]Tue Jul 31 14:04:46 2007[/B][/U][/COLOR] (46AF174E)
    CheckSum:         0001A676
    ImageSize:        0001F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Driver Description: USB-to-Serial Cable Driver/GembirdUAS112 - Driver Reference Table - ser2pl64.sys

Removing the driver is preferable, updating the driver is mandatory.

Update These drivers (remove where possible):

Once all of that is done I strongly recommend testing the RAM using - http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Code:

BugCheck A, {10, 2, 1, fffff800030b0150}

Probably caused by :[B] memory_corruption[/B] ( nt!MiReplenishPageSlist+c0 )

Followup: MachineOwner

Code:

BugCheck C0000221, {fffff8e40022ede0, 0, 0, 400000000000000}

DbsSplayTreeRangeMap::Add: Conflicting region fffff880`018f1000 - fffff880`018f13ff
Unable to map rdyboost.sys region at fffff880`018f1000, NTSTATUS 0xC0000018
Probably caused by : [B]memory_corruption[/B]

Followup: memory_corruption

Code:

BugCheck 50, {fffff6a0001fd588, 0, fffff8000309f903, 5}


Could not read faulting driver name
Probably caused by :[B] memory_corruption[/B] ( nt!MiDeleteAddressesInWorkingSet+468 )

What is your current power savings setting in regards to your HDD?

Code:

[COLOR=Sienna][U][B]BugCheck 9F[/B][/U][/COLOR], {3, fffffa800dca3060, fffff80000b9c518, fffffa8010790010}

Probably caused by : atapi.sys



!irp fffffa8010790010
    Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa800deb2790 00000000 fffff88000fc4f50-00000000 Success Error Cancel pending
           \Driver\Disk    [COLOR=SeaGreen][U][B]partmgr!PmPowerCompletion[/B][/U][/COLOR]
            Args: 00000000 00000001 00000004 00000000
 [ 16, 2]   0 e1 fffffa800deb22c0 00000000 00000000-00000000    pending
           \Driver\partmgr

Be sure to post back with results

!

jeffpkamp · Aug 4, 2013

I already updated the serial driver.

Any suggestions on easier updates for toshiba drivers? I am having trouble finding them and windows updates cannot find them for some reason.

as for the memory... this is from an older post that I did.

I then switched to some old ram which I never had trouble with (2x2GB dell ram). Got another BSOD, no longer reading one of the ram slots.

Ran memtest 10 times without errors...

Is there anything else I should post?

YoYo155 · Aug 4, 2013

Can you give me some more information?

Look at the bottom of your PC:
View attachment 279745

-----------

Can you please upload the MSINFO32 file?

Start> RUN> "MSINFO32" without the quotes then hit [Enter].
In "MSINFO32" go to, File> Save> name it your user-name and upload.

jeffpkamp · Aug 4, 2013

Serial number 4a156502W
Part Number PQ33U-01H00H

also I am noticing again that it is only recognizing one of the two sticks of ram I have in the computer. I have 2x8GB, it is only listing 8GB... I am guessing that this is a symptom of the problem...

Thanks.

YoYo155 · Aug 4, 2013

You will find your drivers HERE, Just click on the links I've posted above and filter by:

Windows 7 x64 (On the left)
Date (On the top right)
the type of device you're looking for (one at a time), also on the left

jeffpkamp · Aug 5, 2013

updated the drivers I could find...

Started having BSOD on start up. I took the ram out and re-installed it to make the computer redetect it. No BSOD since then.

I have attached the minidmp files for these crashes.

YoYo155 · Aug 5, 2013

jeffpkamp said:
Serial number 4a156502W
Part Number PQ33U-01H00H

also I am noticing again that it is only recognizing one of the two sticks of ram I have in the computer. I have 2x8GB, it is only listing 8GB... I am guessing that this is a symptom of the problem...

Thanks.

jeffpkamp said:
I already updated the serial driver.

Any suggestions on easier updates for toshiba drivers? I am having trouble finding them and windows updates cannot find them for some reason.

as for the memory... this is from an older post that I did.

I then switched to some old ram which I never had trouble with (2x2GB dell ram). Got another BSOD, no longer reading one of the ram slots.

Ran memtest 10 times without errors...

Is there anything else I should post?

jeffpkamp said:
updated the drivers I could find...

Started having BSOD on start up. I took the ram out and re-installed it to make the computer redetect it. No BSOD since then.

I have attached the minidmp files for these crashes.

You might have a faulty slot.
Remove the RAM from that particular slot and continue a normal operation as you would everyday.

---------------

Code:

fffff880`0f083000 fffff880`0fd77000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [U][B]Tue Oct 02 20:21:13 [COLOR=Red]2012[/COLOR][/B][/U][COLOR=Red] [/COLOR](506B3099)
    CheckSum:         00CD4613
    ImageSize:        00CF4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Driver Reference Table - nvlddmkm.sys

Update | GeForce 314.22

jeffpkamp · Aug 5, 2013

okay, so major problem... I updated the bios for the computer and now it won't make it past the windows loading screen without a bsod.

I reflashed the old bios back, but it still won't let me boot up... I am trying to get the mini dmp files becuase I can boot up with an ubuntu disk I have. I'll post those shortly.

YoYo155 · Aug 5, 2013

Make sure your SATA Mode settings are properly configured.
AHCI or IDE

jeffpkamp · Aug 5, 2013

so I don't know if these contain the newest minidmp files. I just went into the folder through ubuntu and copied them over.

As for the bad slot theory, I tried running on a single stick but kept getting errors, no matter which stick I used or what slot I used...

If I can get back into windows I will update the GeForce Driver.

Again, thanks for the help.

jeffpkamp · Aug 5, 2013

okay, I got windows to boot again. In bios I have the options of AHCI or compatability mode for the sata controller. I swear its always been the AHCI setting, but changing it to compatability mode allowed windows to start.

Would you suggest staying away from the newer bios, or should I reflash it and try with the new sata settings?

YoYo155 · Aug 5, 2013

Flashing the BIOS is like heart surgery and its best to avoid when possible.
I am away from my computer at the moment so I will look more into it when I can.

jeffpkamp · Aug 5, 2013

I am down to a single stick of RAM that I know is good in a single slot. Just had a crash in which the MOBO stopped recognizing that slot. I have now switched the ram over to the other slot and am waiting to see what will happen. The crash data went to the full memory dump, which I am not sure how to upload due to its size (66mb compressed).

Let me know how, and I will attach it.

YoYo155 · Aug 5, 2013

jeffpkamp said:
I am down to a single stick of RAM that I know is good in a single slot. Just had a crash in which the MOBO stopped recognizing that slot. I have now switched the ram over to the other slot and am waiting to see what will happen. The crash data went to the full memory dump, which I am not sure how to upload due to its size (66mb compressed).

Let me know how, and I will attach it.

How did you determine that RAM module is good?

How many passes did you run it?
When was the last time you've checked it?

You can attach it to your skydrive or something similar

jeffpkamp · Aug 5, 2013

This is a stick from a laptop that has never given me trouble in 2+ years. I also tested it 10+ cycles with Memtest86+, no errors were found.

here is the link for the memory dump. So far no crash using slot #2.

https://skydrive.live.com/redir?resid=6FF10ADC28A47E02!250&authkey=!AHJqkOa5qCE3zjs

YoYo155 · Aug 5, 2013

The MEMORY.DMP:

Code:

**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Unable to read PsLoadedModuleList
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase < SystemRangeStart
Windows 7 Kernel Version 7601 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x00000000`00000000 PsLoadedModuleList = 0xfffff800`032a5670
Debug session time: Mon Aug  5 23:16:56.499 2013 (UTC + 3:00)
System Uptime: 0 days 0:53:48.919
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Unable to read PsLoadedModuleList
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase < SystemRangeStart
Loading Kernel Symbols
Unable to read PsLoadedModuleList
GetContextState failed, 0xD0000147
CS descriptor lookup failed
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counter
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS [COLOR=Blue]0xC0000147[/COLOR]
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147

Code:

 !error [COLOR=Blue]0xC0000147[/COLOR]
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counter
Error code: (NTSTATUS) 0xc0000147 (3221225799) - [COLOR=Blue]{No Paging File Specified}  No paging file was specified in the system configuration.[/COLOR]

Make sure of this | http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Reset your Page File:

1.

rb:Start Menu> Run >type control.exe system
and press the Enter key.
A windows will open and on the Left hand side you will see Advanced system settings, click it.

279921d1375743550-multiple-bsod-errors-unknown-cause-1.png

2. Next click on the Advanced tab and Settings which correspond to the Performance section;

3. Then the Advanced tab once more and click on the Change button;

4. Untick the checkbox next to Automatically manage paging file size for all drives;

279924d1375743550-multiple-bsod-errors-unknown-cause-4.png

5. Select No paging file and Click on the Set button;

279925d1375743550-multiple-bsod-errors-unknown-cause-5.png

6. Confirm all the windows.

7. Restart the PC.

8. Reverse the procedure, by following steps 1-3, only this time select System managed size
and click the Set button;

9. Recheck the box next to Automatically manage paging file size for all drives
and exit the windows by clicking the OK button;

10. Confirm all of the remaining windows by click the OK button
and restart once again to take affect.

jeffpkamp · Aug 6, 2013

okay, I reset the page file. Also have a symptom that might suggest that this is actually a mother board issue. Sometmes when I start up the computer, it will get past bios and post "No Operating System Detected". If I reset it, it goes away, but that makes me think that it's more than memory or drivers causing this problem.

YoYo155 · Aug 6, 2013

jeffpkamp said:
okay, I reset the page file. Also have a symptom that might suggest that this is actually a mother board issue. Sometmes when I start up the computer, it will get past bios and post "No Operating System Detected". If I reset it, it goes away, but that makes me think that it's more than memory or drivers causing this problem.

Have you had any issues since switching to one RAM slot?

P.S. after resetting the page file, activating it the 2nd time don't forget to restart the PC again to take affect!

jeffpkamp · Aug 6, 2013

i might have... I started my computer this morning after turning off the paging, and when I came back it was off (or at least the power was on, but the computer was not, much like it does after a BSOD sometimes), but Paging was off, so if it did, it left no record of it, and since I didn't catch it in the act, I can't say for sure .

I"ll let you know if it does it again now that I turned paging on and reset the computer.

Multiple BSOD errors, Unknown Cause

New member

My Computer

Up The Thread

My Computer

New member

My Computer

Up The Thread

My Computer

New member

My Computer

Up The Thread

My Computer

New member

My Computer

Up The Thread

My Computer

New member

My Computer

Up The Thread

My Computer

New member

My Computer

New member

My Computer

Up The Thread

My Computer

New member

My Computer

Up The Thread

My Computer

New member

My Computer

Up The Thread

My Computer

New member

My Computer

Up The Thread

My Computer

New member

My Computer