Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


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

02 Jan 2014   #11
Voisard

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

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.


My System SpecsSystem Spec
.
03 Jan 2014   #12
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
My System SpecsSystem Spec
03 Jan 2014   #13
Voisard

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

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 .
My System SpecsSystem Spec
.

03 Jan 2014   #14
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
My System SpecsSystem Spec
03 Jan 2014   #15
Voisard

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

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/l...WjxRHTivB96wPd

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" )
My System SpecsSystem Spec
03 Jan 2014   #16
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
My System SpecsSystem Spec
03 Jan 2014   #17
nommy the first

Microsoft Windows 8.1 64-bit Professional
 
 

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.

Quote:
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
My System SpecsSystem Spec
03 Jan 2014   #18
Voisard

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

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 .
My System SpecsSystem Spec
03 Jan 2014   #19
nommy the first

Microsoft Windows 8.1 64-bit Professional
 
 

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

----------

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8004512010, fffff880061b1f1c, ffffffffc000000d, 3}

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

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

----------

Code:
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
    Timestamp:        Fri Jan 18 14:22:15 2013 (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;
Quote   Quote: Originally Posted by Arc View Post
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   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   Tip
Please run Furmark once when your machine has just started, and once again when your machine has been active for several hours.

----------

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {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 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.

----------

Code:
2: kd> dps fffff88003186000 fffff8800318c000
fffff880`0318aa38  00000000`00000000
fffff880`0318aa40  00000000`00000021
fffff880`0318aa48  fffff880`03c37c9fUnable to load image nvmf6264.sys, 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`05a8ce13Unable to load image nvlddmkm.sys, 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.

----------

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8007b33010, fffff88006202f1c, ffffffffc000000d, 3}

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

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

----------

Code:
0: kd> !sysinfo machineid
BiosVendor = American Megatrends Inc.
BiosVersion = 0704   
BiosReleaseDate = 05/19/2009
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;
Quote:
...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
My System SpecsSystem Spec
03 Jan 2014   #20
Voisard

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

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.
My System SpecsSystem Spec
Reply

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




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSOD when trying to multi task and when playing games
Its my first time to encounter this kind of software problem and whenever i try playing online games or when i multi task i get this random BSOD. I assembled this PC around July 2014 two months ago and im familiar with troubleshooting as well. I already did some maintenance tasks, adjusted my...
BSOD Help and Support
BSOD while playing and surfing
Hi, dont know what to do, or what causes the problem. got 3 BSODīs today by the second there stand "system_service_exception" and in the third was no message. dmp files uploaded. thanks for help.
BSOD Help and Support
BSOD, comming when im doing anything. Playing and surfing
Hey Sevenforums. My computer started to crash one or two weeks after I bought my computer. Bought it brand new in March, and since then it has crashed a few times. It's happening more and more often, and now it happens several times a day. I downloaded a program called "blue-screen view" and I...
BSOD Help and Support
BSOD playing various games or just surfing.
Hi, as my title says i get BSOD that is probably related to my GPU when i'm playing games as League of Legends, Far Cry 3, TES:Skyrim, Alan Wake. My pc also freezing sometimes when i'm just surfing on internet via Chrome resulting in a BSOD. I'm really desperate and i couldn't find any help on...
BSOD Help and Support
BSOD Playing Games and Surfing the net
I'm really having a hard time determining the cause of my BSOD. I already brought it to a repair shop to determine what hardware i need to change, but they cannot detect it as well. Please help me with my problem. below is the files from minidump and perfmon My Specs are: Windows 7 32 bit....
BSOD Help and Support
BSOD while playing games or just surfing in the internet
Hey! My PC is brand new (build it up in August) but I keep getting BSOD almost every time. I've updated my graphics card drivers because I thought it would help but it didn't. I get the BSOD totally randomly. It doesn't matter if I play games or just surf in the internet. Is Windows 7 . ....
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Đ Designer Media Ltd

All times are GMT -5. The time now is 23:54.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App