BSOD While surfing on the net (playing POE,FB Minigames) Or multi-task

[Voisard]

Hello Windows 7 Forums !

Well it seems i have some BSOD errors , unfortunately for me .

I did some searching before posting, and did a Memory Test ,
and came with results which i can't understand ..

Log Name: System
Source: Microsoft-Windows-MemoryDiagnostics-Results
Date: 12/28/2013 5:27:15 PM
Event ID: 1102
Task Category: None
Level: Error
Keywords:
User: Système
Computer: serveurfilm
Description:
The Windows Memory Diagnostic tested the computer's memory and detected hardware errors. To identify and repair these problems, contact the computer manufacturer
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-MemoryDiagnostics-Results" Guid="{5F92BC59-248F-4111-86A9-E393E12C6139}" />
<EventID>1102</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-12-28T22:27:15.387800000Z" />
<EventRecordID>122173</EventRecordID>
<Correlation />
<Execution ProcessID="3604" ThreadID="3608" />
<Channel>System</Channel>
<Computer>serveurfilm</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<Results xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2005/08/windows/Reliability/Postboot/Events">
<LaunchType>Manual</LaunchType>
<CompletionType>Fail</CompletionType>
<MemorySize>4095</MemorySize>
<TestType>10</TestType>
<TestDuration>1085</TestDuration>
<TestCount>12</TestCount>
<NumPagesTested>1047273</NumPagesTested>
<NumPagesUnTested>1121</NumPagesUnTested>
<NumBadPages>10</NumBadPages>
<T1NumBadPages>0</T1NumBadPages>
<T2NumBadPages>0</T2NumBadPages>
<T3NumBadPages>8</T3NumBadPages>
<T4NumBadPages>0</T4NumBadPages>
<T5NumBadPages>0</T5NumBadPages>
<T6NumBadPages>0</T6NumBadPages>
<T7NumBadPages>0</T7NumBadPages>
<T8NumBadPages>0</T8NumBadPages>
<T9NumBadPages>2</T9NumBadPages>
<T10NumBadPages>0</T10NumBadPages>
<T11NumBadPages>0</T11NumBadPages>
<T12NumBadPages>0</T12NumBadPages>
<T13NumBadPages>0</T13NumBadPages>
<T14NumBadPages>0</T14NumBadPages>
<T15NumBadPages>0</T15NumBadPages>
<T16NumBadPages>0</T16NumBadPages>
</Results>
</UserData>
</Event>

I've also attached a screenshot of my current pc specs .

To come back on the topic,
These crashes (BSOD's) occur mainly when i multi-task (no games) , Frequently when i play "client games" ex: (Path of Exile , Tera Rising , etc.. ) And often when i play browser games while multi-tasking , (Facebook games) . And as always my bsod's indicate memory failures, so since i was not 100% sure, i did the Windows Vista Memory test, and to my surprise that too , read memory failures ..

My question to you , what would be causing this, how to remove those bsod's , and with the specs i've attached , is it worth the trouble to buy new hardware for the pc, or i would be better off buying a new one?

Thanks alot

Steve.V

 

[Voisard]

Bump, Sorry for this, was in a rush, and didn't realize i had to post a SF attachment ,

Now it's attached !

Thanks for , rereading !

 

[Arc]

The zip you uploaded does not contain any crash dump.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup program before you upload another zip.

 

[Voisard]

Alright , another BSOD just occured ,

I was browsing while playing Path of Exile , and the crash occured, Memory crash if i read correctly.

I also grabbed the Blue Screen Viewer software , and it seems interesting,.. it managed to give me the driver that "would" be in fault .

But anyhow , i'd still love to have an opinion of someone qualified, to tell me whats going wrong, with my pc.

Thanks !

 

[Arc]

The crash dump itself is not showing much more info about the BSOD, but the stop 0x1A BSOD is caused either by memory malfunction or by some driver passing bad information to the memory.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
______________________________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 5ffd001, 25ff, fffff70001080000}

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 0000000005ffd001
Arg3: 00000000000025ff
Arg4: fffff70001080000

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


BUGCHECK_STR:  0x1a_41284

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800030da727 to fffff80003083bc0

STACK_TEXT:  
fffff880`02a96208 fffff800`030da727 : 00000000`0000001a 00000000`00041284 00000000`05ffd001 00000000`000025ff : nt!KeBugCheckEx
fffff880`02a96210 fffff800`0309d1f9 : fffffa80`0629a3f8 ffffffff`ffffffff fffffa80`06dbfb50 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x4ad3
fffff880`02a96250 fffff800`030789eb : dff00000`a53a3847 fffff680`0002ffe8 ffffffff`ffffffff 000fffff`ffffffff : nt!MiTerminateWsle+0x29
fffff880`02a96290 fffff800`03070142 : fffffa80`06274900 fffff880`00000000 fffffa80`0629a060 fffffa80`0629a3f8 : nt!MiDecommitPages+0x20b
fffff880`02a96b20 fffff800`03082e53 : ffffffff`ffffffff 00000000`001ce1d0 00000000`001ce1c8 00000000`00004000 : nt!NtFreeVirtualMemory+0x382
fffff880`02a96c20 00000000`76e2149a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001ce198 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e2149a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4ad3
fffff800`030da727 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4ad3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ad3

BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ad3

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

 

[Voisard]

Hello Arc,

I've did the memtest86 , not sure how to post the results , but in 1hr of testing i came up with around 10 errors , so i stopped it . Like mentioned ..

I've also came across more Bsod's , so i've attached another zipped folder with mini dumps inside .. (i think the memtest will be in there aswell ?!

(if not let me know how do i get the results , thanks !

 

[Arc]

I've did the memtest86 , not sure how to post the results , but in 1hr of testing i came up with around 10 errors , so i stopped it . Like mentioned ..

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[Voisard]

Alright , so i will do the other tests like mentioned ,
But for the minidump files , and all the other BSOD titles such as ,: irql less or not equal , system service exception , kmode exception not handled , and the numerous memory management errors ... Would all those be related to that ram that may be "bad" or that slot..?

In other words , my pc would be in good shape apart from that bad ram/slot ? No other things to update,mention to change/fix ?

EDIT : I've also noticed you didn't check my SF folder which i included into my post (Which has numerous dump files) ... Why's that ?

 

[Voisard]

test Slot1 Slot2
RAM1 Error Error
RAM2 Error Error


Are the results i ran into when i worked with memtest again this morning ... Hopefully it isn't as bad as i look at it.

I'm no expert , but to me it looks like the motherboard would be the issue , hence both ram sticks aren't passing the test in both slots . ( And both my Ram Sticks are 1 year old, bought them as a pair, so the sticks do match)

Hopefully we will figure this out !

Thanks again Archie! I believe in you!

 

[Arc]

test Slot1 Slot2
RAM1 Error Error
RAM2 Error Error


Are the results i ran into when i worked with memtest again this morning ... Hopefully it isn't as bad as i look at it.

I'm no expert , but to me it looks like the motherboard would be the issue , hence both ram sticks aren't passing the test in both slots . ( And both my Ram Sticks are 1 year old, bought them as a pair, so the sticks do match)

Hopefully we will figure this out !

Thanks again Archie! I believe in you!

That's an odd result. No minimization can be done based on it. It may be that the kit is damaged. Can you manage some spare RAM to test the situation? From the family members or friends? And, is it still within warranty, get replacement RAM from the vendor.

Otherwise, apply those RAMs in another computer and see what happens there.

If still the same situation continues, then we may consider it as a motherboard issue.

About dumps checking, RAM issue may cause anything compel to fail, and BSOD with any name may occur. And when the RAM issue is detected, no need to check more dumps ... but it is needed to determine the origin of the issue.

 

[Voisard]

I highly doubt my ram sticks are damaged , bought them new 1year ago .. I'm pretty sure the solution to my problem lays elsewhere , but definitely not the rams ... By the way, why not read the dumps ?! Maybe they would narrow the problem down a little bit , (looking at previous posters, everyone seem to read the dumps, and have "other" solutions than the memtest) .. Memtest afterall is only a software, and not a fix or a narrowed solution . To me, what can cause BSOD's are memory (Checked in my case) , Drivers (not sure which ones, since no dumps where read) and not sure how to check them , hardware, i know my fans are functioning,i did the dskchk on both hard drives (error free) , correct me if im wrong, but if my mobo would be the problem, i wouldn't be writing this to you right now ..

If you or someone else could help me at least check other solutions to my problem apart from the memtest , i would be graceful !

Thanks !

attached some more minidumps.

 

[Arc]

Troubleshooting will not go with your doubts. Just unpacked RAMs may be corrupted.

As far as the memory issue is not fixed, dump check is worthless.

Please stop uploading dumps and concentrate on rectify the memory issue.

 

[Voisard]

I did another test , this time with Driver Verifier ,

i uploaded the results ...

Why just not look at the Dumps, i don't see any harm in looking at them, maybe it would help narrow down the problem,
Cause right now , its going no where , even you, said my results are odd enough ... 2 Rams out of 2 faulty, common now ... My pc wouldn't be running what so ever .
I am still able to load into games such as Path of Exile, still able to look through social networks , and all that while having Driver Verifier running simultaneously...

Please , look for some other options .

 

[Arc]

You are doing wrong. Driver Verifier is not needed now.

THIS IS THE TIME TO ISOLATE BETWEEN THE RAM AND MOTHERBOARD AND SWAP THE CULPRIT.

Concentrate on this part only.

 

[Voisard]

Sorry sir,
But you are not explaining to me why would 2 ram sticks would be damaged at the same time.. or why would my mobo be damaged , if im still able to access my pc, (even though i experience a few bsod's every ~4 hours) .

Or when i look under Speccy or CPU-Z , it indicates both sticks are in use ..
Im definitely not an expert when it comes to pc's , but i'm no beginner either , and when a hardware piece is damaged, the pc wouldn't be running right now. Or it would point out 2.00GB are read, instead of 4.00GB .

I would love to be able to read my dumps .. or understand which drivers aren't loaded and what it means ..

No need to panic , i am simply asking someone to read my dumps, and explain to me why certain drivers aren't loading ..
If you do not feel the need to read them, maybe someone else could . Cause i am definitely not buying another new set of rams to "test" .. Im at a stage, that if my problems persist , i will simply throw the damn thing in the bin, and buy a new rig.
When i posted in this forum, it was to find solutions , i did run memtest , i searched the net for errors like mine , and didn't find anything similar. Oddly enough , even you said .

Why not pass at another stage , and try to run something other then memtest .. you sir, are only repeating the same thing over and over again .. Without explaining why would both my ram sticks would be damaged all of a sudden. Or what would happen if my mobo would be the the problem , (i would like to think, that since everything relies on it, my pc wouldn't be booting).

EDIT** -- I Just verified to see if my Motherboard supports my CPU , and it doesn't , maybe this is why .. And not my RAM <-- like you stated .

http://support.asus.com/cpusupport/list.aspx?SLanguage=en&p=1&s=24&m=M2N68-AM%20SE2&os=&hashedid=rzWjxRHTivB96wPd

My Cpu being a : AMD Phenom X4 9950 Black Edition


EDIT 2** -- I also checked if my motherboards support my Rams, and it also looks like it doesn't ..
Crucial BL12864AA804.8FE5 = Supported


Mine : Crucial CT25664AA800.K16F = No mention of support .

(Maybe it has nothing to with it, and any 2 same sticks would work, i dunno)

I also checked if my BIOS was up to date, and it isn't ...

But im afraid of updating it, if my Mobo and CPU aren't compatible , i may not ever be able to get it to boot.. It would probably burn the mobo in my opinion .

I have version

0704 Bios

and the newest installment version is : 1801 Bios. That's about roughly ~3/4 years behind...

What should i do next...?

(By the way, i think it doesn't hurt to check other possibilities , and not only rely on a software that gives no "reliable information" )

 

[Arc]

OK, do as you want.

I explained why it is not possible to determine which one may be fauty, and why; and what else may be needed to do for further results.

I also told that dump reading will be TOTALLY MEANINGLESS till the RAM issue is fixed.

Still, if you want to proceed at your will, do it.

 

[nommy the first]

Hello Viosard,

As Arc has already said, you can't start fixing another problem before fixing the first one. Doing this would be meaningless since all dumps you upload will point to the RAM failing. Because it is indeed failing.

The issue you first need to resolve in order for us to start working through the other issues is to replace the faulty RAM. If this isn't done then there's very little we can do to assist you further.

I highly doubt my ram sticks are damaged , bought them new 1year ago

While you may have doubt, the test we have done definitely prove it.
One error in Memtest is enough to pinpoint failing RAM, and you had ten on less than an hour.

Your best course of action now is to borrow some RAM from friends or family members in order to rule out faulty DIMM slots.

If after testing with other RAM the errors are the same as before there is a good chance that your motherboards DIMM slots are faulty, and not your RAM, as you claim.

Until those steps are taken, there is very little we can do to assist you.


Nommy

 

[Voisard]

Please look at my Edited post ...
You will see my Ram's aren't the one making the trouble ...

Thank-you

I checked further into my rams compatibility with my Mobo, and they are compatible according to Crucial Technology's website .

 

[nommy the first]

Okay then. I shall do as you wish and put the RAM aside and look at your dumps, starting with the latest one.

----------

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red][B]BugCheck 116[/B][/COLOR], {fffffa8004512010, fffff880061b1f1c, ffffffffc000000d, 3}

Unable to load image [COLOR=Red][B]nvlddmkm.sys[/B][/COLOR], Win32 error 0n2
*** [COLOR=Red][B]WARNING: Unable to verify timestamp for nvlddmkm.sys[/B][/COLOR]
*** [COLOR=Red][B]ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys [/B][/COLOR]( nvlddmkm+931f1c )

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

Usual cause: Failing GPU driver.
Driver Reference Table: nvlddmkm.sys.
More info :ar: Bug Check 0x116.

----------

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05880000 fffff880`06327000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    [COLOR=Red][B]Timestamp:        Fri Jan 18 14:22:15 2013[/B][/COLOR] (50F94C87)
    CheckSum:         00A92B69
    ImageSize:        00AA7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please follow this and install the most stable 314.22 WHQL driver;

Lately we have experienced some issues with the latest driver. Install the 314.22 WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

----------

After changing the driver, please stress test the graphics card using Furmark GPU Stress Test.

   Information

During the test please check the screen for artifacts.
The purpose of this test is to make your machine crash and create dump files so that we can pinpoint the cause of your problem.

   Tip

Please run Furmark once when your machine has just started, and once again when your machine has been active for several hours.

----------

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red][B]BugCheck 1E,[/B][/COLOR] {0, 0, 0, 0}

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

Usual cause: Incompatible hardware, faulty drivers.
More info :ar: Bug Check 0x1E.
We see that this dump is pointing to ntkrnlmp.exe as probable cause, but since that is a Windows driver, it shouldn't crash on it's own and is most likely not the cause. Let's see what the dps command gives us.

----------

2: kd> dps fffff88003186000 fffff8800318c000
fffff880`0318aa38  00000000`00000000
fffff880`0318aa40  00000000`00000021
fffff880`0318aa48  fffff880`03c37c9f[COLOR=Red][B]Unable to load image nvmf6264.sys[/B][/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
 nvmf6264+0xcc9f
.
.
.
fffff880`0318ac30  00001f80`0010001f
fffff880`0318ac38  0053002b`002b0010
fffff880`0318ac40  00210286`0018002b
fffff880`0318ac48  fffff880`05a8ce13[COLOR=Red][B]Unable to load image nvlddmkm.sys[/B][/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x1d6e13

Driver Reference Table: nvmf6264.sys, nvlddmkm.sys.
Your nvidia video driver and your nvidia nForce network driver appear to be failing. This will be solved by following my suggestions from the previous dump file.

----------

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red][B]BugCheck 116[/B][/COLOR], {fffffa8007b33010, fffff88006202f1c, ffffffffc000000d, 3}
[COLOR=Red][B]
Unable to load image nvlddmkm.sys[/B][/COLOR], Win32 error 0n2
*** [COLOR=Red][B]WARNING: Unable to verify timestamp for nvlddmkm.sys[/B][/COLOR]
*** [COLOR=Red][B]ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys[/B][/COLOR] ( nvlddmkm+931f1c )

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

And there you have it. Three consecutive BSoD's all blaming your GPU driver.

----------

0: kd> !sysinfo machineid
BiosVendor = American Megatrends Inc.
BiosVersion = [COLOR=Red][B]0704   [/B][/COLOR]
BiosReleaseDate = [COLOR=Red][B]05/19/2009[/B][/COLOR]

As you previously stated, your BIOS version is indeed very old. I would recommend on updating it, but if you're afraid to do it, then you shouldn't.

But, since you stated this;

...if my problems persist , i will simply throw the damn thing in the bin, and buy a new rig...

I see no harm in trying. If it works, it works, and if it doesn't, do as you stated above.
Whatever option you choose, do note that it's a very good idea to make regular backups in case that something happens.


Good luck and keep us posted,
Nommy

 

[Voisard]

Hello,
Thanks Nommy,
I've removed the NVidia Drivers from my pc (Clean installed) Re-installed the 314.22 WHQL driver , Unticked the options you mentioned ,

Then started a Furmak stress test as mentionned ,
It went fine , up until it reached 105 degrees Celcius , closed the program (since it stated that if it overuns the 100 degrees, to close it) As soon as i closed it, i received a Bsod , IRQL_NOT_LESS_OR_EQUAL .

I will redo a stress test when my machine will have 3-4hours of continuous activity, like suggested aswell.
Thanks alot, for reading the dumps, and trying to figure out a way.

As for the BIOS , what "could" happen if i installed the newer version, could my Mobo flank out , (Since it isn't compatible with my Cpu) What are the possibilities ?

I added a copy of the recent minidumps due to the Furmak test.
I would also like to know if , theres some other way to read the results of the test ?! (Like saying if it passed it, or if it failed , (i assumed mine failed since when i closed it, it bsod's right after, lol )

Thanks again !!

(Let me know if i should do the Furmak , and leave it run until it bsod's or if i should do like i did earlier close it when reaching 100degree's + )

EDIT *I also went and attached a copy of my temps using Speccy, thought that 108degrees on my gpu wasnt normal.. I was multi-tasking when it occured.