Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSODs while playing games


  • Please log in to reply

#16
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,905 posts
Good luck with the Lan driver update :thumbsup:

Some information regarding the testing of the Ram;

Many MBs will not boot unless there is Ram in slot 0/1, this slot is often the one nearest to the CPU.

A physical test of the Ram is more conclusive than testing it with software.

Memtest should be allowed to complete 4 or 5 passes and this can take up to several hours to complete.

Windows own memory testing tool.

How to physically test your Ram.

The following checks require the computer case to be opened so take the following safety precautions 1st, disconnect the power cord from the wall socket and take anti static precautions before touching anything inside, you can do this by touching a bare metal part of the case.

Have a pencil and notepad to hand.
Remove each stick of Ram and blow out the memory slots.
Insert the first stick of Ram in memory slot one, reconnect the power and in the case of a desktop computer the video to screen cable.
Power up the computer and see how it goes.
Make a note of the results.
Repeat the procedure until the first stick of Ram has been tested in each memory slot and the results written down.
Remove the first stick of Ram and put it to one side on top of a piece of paper with the number one on it for identification purposes.
Repeat the procedure with all Ram until each stick has been tested in all slots, the results written down and the sticks identified numerically.
Please note that some MBs (motherboards) will not boot unless there is Ram in slot one so please provide us with your motherboard details, brand, model name/number and any revision number, these details may be found by the CPU, between the PCI slots and/or around the edge of the motherboard, once we have the MB details we can look for the user manual.
  • 1

Advertisements


#17
szpula

szpula

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts
I attached fragment about setup of RAM sticks from manual.

A1 - is mine 1
A2 - is mine 2
B1 - is mine 3
B2 - is mine 4

So putting pair in A1/B1 or A2/B2 should work.


By physical test you mean this Windows Memory Tool?
What do you think I should do next?


BTW, since install newest driver and using only one stick, no crash/BSOD so far.

Attached Thumbnails

  • DDR.png

  • 0

#18
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,905 posts
When using two sticks of Ram they should be in slots A2 and B2 for the best performance, putting them in slots A1 and B1 will reduce performance as they are the secondary slots.

By physical test you mean this Windows Memory Tool?

No, please refer back to my reply #16 starting from the safety notes that are in red text and under the heading "How to physically test your Ram."

What do you think I should do next?

See below.

BTW, since install newest driver and using only one stick, no crash/BSOD so far.

I would continue to use the computer for a couple of days exactly as it is now, if you do not have any crashes you should carry out the physical memory test as detailed in my reply #16.
  • 0

#19
szpula

szpula

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts
I see.

But wasn't it exactly what I did while using memtest86?
I placed every stick in every hole (2 x 4 combinations) and 4 combinations more with 2 sticks inserted. Every time MB booted.
  • 0

#20
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,905 posts
Flaky Ram can crash the computer at any time and be totally random which makes it difficult to pinpoint sometimes.

As suggested use the computer as it is at present and see if it stays stable, you will then know that the new Lan driver is ok at least and go back to checking the Ram again.
  • 0

#21
szpula

szpula

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts
OK.

I will monitor PC behaviour.
But as I wrote few post before, I want to buy new RAM sticks anyway - I was thinking about 2 x 4GB.
Which one do you suggest? It use my PC for gaming, but these programs also will be used frequently: AutoCAD, Photoshop, IntelliJ IDEA, Eclipse, Visual Studio. I believe that 8GB will enough? Or should I buy 16GB?
  • 0

#22
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,905 posts
Use the Crucial system scanner tool to find the best recommended Ram for your system, no need to purchase from there, write down the details and shop around for the best deal http://www.crucial.c...ner/?click=true let us know what is suggested and we can also look for you.
  • 1

#23
szpula

szpula

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts
Hi.

I used scanner from EU site - it shows different serial numbers that scanner from US version :)

Here are my results: http://www.crucial.c...85F711031D926C3

I think that 8GB, 1600MHz, CL8 should be enough for now.
I found Crucial DDR3 8GB (2x4GB) 1600MHz Ballistix Tactical CL8 in shop near my place for the equivalence of 67EUR / 90USD (gross). Should I go for it?
  • 0

#24
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,905 posts
Hello szpula

That is a good price for the brand and CL8 spec Ram - the nearest that I got to it was the example Here
  • 0

#25
szpula

szpula

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts
First BSOD since 23rd September have just appeared.

On Sun 2013-09-29 21:16:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092913-18579-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0x813C2444, 0x2, 0x1, 0xFFFFF80002C872E0)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 2013-09-29 21:16:45 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x7B52A)
Bugcheck code: 0xA (0x813C2444, 0x2, 0x1, 0xFFFFF80002C872E0)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ntfs.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Sterownik systemu plików NT
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


MEMORY.DMP in WinDbg ('!analyze -v'):

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000813c2444, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c872e0, address which referenced memory

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80002c68000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 51fb06cd

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
00000000813c2444

CURRENT_IRQL: 0

FAULTING_IP:
nt!FsRtlPrivateLock+100
fffff800`02c872e0 008944243c41 add byte ptr [rcx+413C2444h],cl

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from fffff80002cdd129 to fffff80002cddb80

STACK_TEXT:
fffff880`0bd2b278 fffff800`02cdd129 : 00000000`0000000a 00000000`813c2444 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0bd2b280 fffff800`02cdbda0 : 00000000`00000000 00000000`00000000 00000000`000001f1 00000000`00000000 : nt!KeSynchronizeExecution+0x3d39
fffff880`0bd2b3c0 fffff800`02c872e0 : 00000000`00000000 00000000`00000000 fffff8a0`04a692e8 fffff880`0bd2b6a0 : nt!KeSynchronizeExecution+0x29b0
fffff880`0bd2b550 fffff880`016aa52a : 00000000`00000000 fffffa80`0419a8b0 00000000`00000000 00000000`00000001 : nt!FsRtlPrivateLock+0x100
fffff880`0bd2b620 fffff880`0120c4a1 : fffffa80`0419a8b0 fffffa80`045aaad0 fffff880`0bd2ba08 fffffa80`04fb7410 : Ntfs+0x7b52a
fffff880`0bd2b840 fffff880`0120f8ba : fffff880`0bd2b910 fffffa80`045aaa68 fffffa80`04fb7400 fffff880`0bd2ba00 : fltmgr+0x14a1
fffff880`0bd2b8a0 fffff880`01230dda : fffff880`0bd2ba08 00000000`00000000 fffff880`0bd2ba18 fffff880`0bd2b9f8 : fltmgr+0x48ba
fffff880`0bd2b8e0 fffff800`02f53bbb : fffffa80`0419a8b0 fffffa80`04fb7410 fffffa80`02084600 fffff800`04fb7410 : fltmgr+0x25dda
fffff880`0bd2b990 fffff800`02cdce13 : fffffa80`02c1e270 fffff8a0`000084d0 00000000`00000000 00000000`00000000 : nt!NtLockFile+0x2c7
fffff880`0bd2ba70 00000000`773220ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x3a23
00000000`049ee418 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773220ea


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!FsRtlPrivateLock+100
fffff800`02c872e0 008944243c41 add byte ptr [rcx+413C2444h],cl

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!FsRtlPrivateLock+100

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------
  • 0

Advertisements


#26
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,905 posts
Have you upgraded/updated any hardware or software.

Try running the Microsoft "Fix It"
  • 0

#27
szpula

szpula

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts
This tool didn't find any problems.

I have installed new RAMs today - Crucial DDR3 8GB (2x4GB) 1600MHz Ballistix Tactical CL8 :)
We will see how they behaves.
  • 0

#28
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,905 posts
:thumbsup:
  • 0

#29
szpula

szpula

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts
Hello.

Since I have installed new RAM, there wasn't a single BSOD :)
In the middle of October I bought new GFX: Palit GeForce GTX 760 JetStream 2GB DDR5
There weren't any problems with it too :)

A lot of thanks to you, phillpower2. You helped me a lot.
  • 0

#30
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,905 posts
Hello szpula :wave:

I am pleased that all is now well, thank you for the follow up and as ever you are most welcome :thumbsup:
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP