[sarnok]

Hi, been having some problems with Win7 blue screens for some time now. I recently refunded the HD from Western Digital for a replacement and re-installed the OS. Still getting BSODs. Below are messages from the two most recent ones. The first one, I was browsing the NVIDIA website for driver downloads when it happened. The second one, I had left the computer alone while Steam was downloading files. Other than Steam and NVIDIA drivers, my system is pretty much Win 7 vanilla right now. Would appreciate any help from anyone on this.

My systems SPECS (custom built in 2009):
GIGABYTE GA-EP45-UD3P LGA 775 Intel P45 ATX Intel Motherboard
CPU: Intel Core 2 Duo E8400 3.0 GHz 6M L2 Cache 1333MHz FSB LGA775 Dual-Core Processor
HD: Western Digital Caviar Blue WD6400AAKS 640GB 7200 RPM SATA 3.0Gb
GPU: Nvidia EVGA 896-P3-1255-AR GeForce GTX 260 Core 216 896MB 448-bit GDDR3 PCI Express
MEM: G.SKILL 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 1066 (PC2 8500) Dual Channel Kit Desktop Memory Model F2-8500CL5D-4GBPK
MEDIA: Samsung SH-S223F/BEBE Internal Half Height Supermulti SATA 22X DVD-Writable Drive



INITIAL MESSAGES RECEIVED UPON BOOT UP:


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: FFFFFA80CC621030
BCP2: 0000000000000000
BCP3: FFFFF80002894B7C
BCP4: 0000000000000005
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\070112-27409-01.dmp
C:\Users\Sarnok\AppData\Local\Temp\WER-910265-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft....88&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
--------------------------------------------------------------------------
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\070112-15724-01.dmp
C:\Users\Sarnok\AppData\Local\Temp\WER-46301-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft....88&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

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



DUMP FILES FROM THESE BSODs:

==================================================
Dump File : 070112-27409-01.dmp
Crash Time : 7/1/2012 4:58:01 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffa80`cc621030
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`02894b7c
Parameter 4 : 00000000`00000005
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070112-27409-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 291,040
==================================================

==================================================
Dump File : 070112-15724-01.dmp
Crash Time : 7/1/2012 3:55:10 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+66a7e
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+71ed0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070112-15724-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 284,656
==================================================

[Advertisements]

Please, can anyone help?

[sarnok]

Please, can anyone help?

[rshaffer61]

Hello Sarnok.... Welcome to
GeeksToGo,


I'm sorry to hear about your issue. We will try to help you resolve this as soon as possible.

• Please understand we are all volunteers and we are not here all the time.
• Sometimes it may be a extended amount of time to get back to you. If it has been
  more then 3 days please shoot me a PM and I will try to get back to you quickly
  then.
• Please do the following and supply the requested information as needed. If you
  don't understand my instructions please ask and I will try to explain them
  clearer for you.
• Do not attempt any steps unless instructed or ask before to
  make sure they will not cause any further issues.
• If you are receiving assistance in any other forum site please let us know as there may be conflicting advice given.

Before we can help you need to provide the following so I can start you in the right direction.
Laptop or Desktop?

• If a name brand system then what brand, make and model is the system?
• If custom built then what brand, make and model is the motherboard
• Total memory installed
• Total hard drive capacity and free space
• What steps have you taken so far to resolve the issue

0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
(Click to consult the online MSDN article.)
The Windows kernel detected an illegal or unknown processor instruction. A Stop 0x1E condition can be caused by invalid memory and access violations similar to those that generate Stop 0xA errors. This default Windows error handler typically intercepts these problems if error-handling routines are not present in the code itself.


0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online MSDN article.)
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card). Use the General Troubleshooting of STOP Messages checklist above.

First common denominator is a memory issue so I'm going to ask you start with the following instructions.


A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

[sarnok]

Thanks for the reply. I will follow the instructions you've laid out for testing the RAM and let you know the results.

Information on my system (a desktop) is in my original post. I've attempted replacing the HD and reinstalling Windows 7 Professional. I also dual boot with Windows XP on this machine, but my problems with BSOD predate the dual boot configuration. - Sarnok

[rshaffer61]

To clarify is the issue happening with both XP and Win7?

[sarnok]

Primarily Win7, but I believe it's with XP as well, just not as frequently.

I ran memtest over night and it found 9 errors after 2 passes.

Thx.

[rshaffer61]

I ran memtest over night and it found 9 errors after 2 passes.

This I can say is probably 90 to 100% of your issue.
Did you test all the memory together or do you know if you have more then one memory module installed on the motherboard? If more then one remove one and run the test again to see if it shows errors. Then test the other one to make sure if it is both modules or just one. Regardless i think you need ot purchase new memory and you need to make sure to get the correct type for your system. You can do this by checking with Crucial and their online memory scanner to give you the correct type and configuration you can have for your system.

Go to HERE and run the Crucial online scanner.
This will give you the exact memory configuration for your system.
You do not have to buy the memory from there, but write down the information and if you need assistance in purchasing the upgrade memory GTG can assist with suggestions also.

[sarnok]

It has two DIMMs. The overnight test was with both DIMMs. I just ran another one with just one DIMM while I was at work and confirmed it was faulty after 6 passes. Now I'll test the other DIMM.

I'll check out the memory scanner and get some new RAM. Will let you know if there are any continued problems. My parents have been having a lot of BSOD problems with a similar system that I built for them a year ago, so I'll use these steps to try and troubleshoot their system next time I visit them.

Thanks again for your time and instruction. - sarnok

[rshaffer61]

If the other ram tests good try running with just it and see if the BSOD's stop then.

[rshaffer61]

Are you still having problems with your issue?
It has been 22 days since your last response and I was wondering if the issue has been resolved?
If so can you explain how it was resolved so others may be able to fix it if they have the same issue.
If not please let us know and we can continue with helping you to resolve the issue.

[sarnok]

Are you still having problems with your issue?
It has been 22 days since your last response and I was wondering if the issue has been resolved?
If so can you explain how it was resolved so others may be able to fix it if they have the same issue.
If not please let us know and we can continue with helping you to resolve the issue.

Hey, sorry about the late reply. I ended up going out of town for a month and a half before I could troubleshoot further. When I got back, I decided to look into the issue a little more to see if my BIOS settings might have something to do with the problem. As it turned out, my motherboard (the GIGABYTE GA-EP45-UD3P) is a little finicky with RAM placement and power settings (GSKILL F2-8500CL5D-4GBPK). I originally had the DIMMs paired in slots 3 and 4. Other discussions elsewhere on the net suggested that slots 2 and 4 might be more forgiving. I shifted the DIMMs to these slots and also decreased the MCH core voltage in my BIOS from 1.1 to 0.9.

The memtest went fine after that with 0 errors after 3 passes. I've been back in Win7 on this computer now for the past 36 hours with no BSODs. So that seemed to fix the problem. This RAM is actually rated to go as high as 2.0 or 2.1 volts, but for what I do with this computer I don't think I'll need to do that, though I might try it in the future.

Thanks again for your help. Not being very savvy with hardware, you got me pointed in the right direction.

[rshaffer61]

Yeah I would not increase the voltages either. Leave them at default settings and everything should be working fine from now on.
Thanks for getting back with us and updating what has happened.

[Troy]

Also as a follow up note to this thread... I use a lot of G.Skill RAM and haven't had a failure yet (every other brand has failed on me so far at least once). I fully believe that it is possible it will happen, but not yet.

But my main point is that good RAM companies (such as G.Skill) have lifetime warranty on their memory modules. So if down the track you find the RAM is actually faulty, you wouldn't necessarily have to purchase new RAM.

Lastly I have a system very similar to yours, I am running the UD3L variant of the motherboard. Originally I had the E6750 processor and for the last year or two I have upgraded to the Q9550. This is a hefty processor, it absolutely flies. That and 8GB of G.Skill RAM (all you would need to do is add one more 4GB kit exactly the same) and a 120GB SSD drive for boot and programs, you wouldn't believe the performance difference. My computer runs like lightning and much quicker than a lot of new computers out there. So if you wanted to upgrade, you certainly have the potential.