Solved BSOD at random times. Recently driver power state failure

[Arc]

I already disabled Driver Verifier. I was having terrible internet issues with it running.

Good point.

Name    [00000007] Intel(R) 82567V-2 Gigabit Network Connection
Driver    c:\windows\system32\drivers\e1y62x64.sys (10.0.6.0, 281.21 KB (287,960 bytes), [COLOR=Red]3/16/2010[/COLOR] 1:07 PM)

See how old the driver is. Try to get an update from Intel® 82567 Gigabit Ethernet Controller — Support for Intel® 82567 LM / LF / V Gigabit Network Connections.

 

[Rotzy]

Updated driver. Download speeds (via speakeasy's speed test) are now 1/10 of what they were before . Upload speeds are blazing fast.

Edit: made a few Power Management changes, specifically deselected the "Reduce link speed to save power" and the speeds are back to normal

 

[Arc]

OMG!! :shock:
Try a physical download to check it? Any small file, say Speccy?
If you dont have it, it is a must have app.

 

[Rotzy]

Since we've started messing around, my computer will no longer sleep. When I put the computer to sleep, it immediately comes back out of sleep mode. Any thoughts?

Edit: Made some power management changes to the network adapter. Seems to be sleeping again.

 

[Arc]

Change the power option setting, back them to default and see?

BTW, how is it working now?

 

[Rotzy]

I've been out of town for 5 days and I won't be home until tomorrow. We'll see how it's doing then.

 

[Rotzy]

It was doing ok, but I had a random restart today. Files attached.

 

[Arc]

As per the data you supplied, the lase BSOD occurred at 19/11/2012, 9:42 AM. So what you have got today is not a BSOD, but any other random shutdown.

Can you describe the situation when it happened?

 

[Rotzy]

It happened the same way that's been plaguing me for over a year now... I was browsing the internet reading a webpage and "poof" the computer is rebooting. No shutdown, no beeps just webpage one second and bios the next :-(. It has happened during all sorts of different tasks like web browsing, working on Word or Excel files or doing just about any other task large or small.

 

[Rotzy]

It happened the same way it's been happening for over a year now... I was browsing the internet reading a webpage and "poof", it was rebooting. No shutdown, no beeps just an internet page one second and the bios the next :-( In the past it has happened on web pages, working on Word or Excel files or doing just about every task I can think of, both large and small. I can't seem to find a pattern to any of it.

 

[Arc]

Better you perform http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html.

Follow the tutorial. Everything you need is described there, and it works good for non-oem systems, too.

 

[Rotzy]

I'm not quite ready to format the system and start over. I still haven't completed the ram test. Perhaps after that...

Another BSOD, flies attached

 

[Arc]

Yes, you need to do the RAM tests.

STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
16 errors : !nt (fffff800030ff284-fffff800030ff37c)
fffff800030ff280  24  48  39  48 *fd  75  02  f3  c3  48  8b  c8 *89  8b  00  eb $H9H.u...H......
fffff800030ff290  e7  48  8b  48 *71  eb  07  48  8b  c1  48  8b *1a  08  48  85 .H.Hq..H..H...H.
fffff800030ff2a0  c9  74  e4  eb *2d  33  c0  c3  90  90  90  90 *7e  90  90  90 .t..-3......~...
fffff800030ff2b0  65  48  8b  04 *a8  88  01  00  00  48  8b  50 *b2  48  8b  82 eH.......H.P.H..
...
fffff800030ff340  c4  28  c3  90 *74  90  90  90  90  90  90  90 *2e  83  ec  28 .(..t..........(
fffff800030ff350  48  b8  00  00 *b3  00  00  f9  ff  ff  4c  8b *78  48  3b  c8 H.........L.xH;.
fffff800030ff360  0f  83  cc  00 *66  00  48  3b  0d  a3  cc  1f *8f  76  1e  48 ....f.H;.....v.H
fffff800030ff370  b8  00  00  00 *cc  80  f6  ff  ff  48  3b  c8 *04  79  48  b8 .........H;..yH.

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

 

[Rotzy]

I know I NEED to do the ram test, but here's another BSOD...

 

[Arc]

Almost the same thing ......

STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
8 errors : !nt (fffff80003119742-fffff8000311977a)
fffff80003119740  00  00 *0d  89  b5  88  01  00  00  48 *d6  05  90  82  13  00 .........H......
fffff80003119750  48  33 *45  48  89  85  30  01  00  00 *a9  8a  f9  44  88  4d H3EH..0......D.M
fffff80003119760  00  49 *2a  f0  4c  8b  f2  48  8b  d9 *fc  ff  04  25  b4  48 .I*.L..H.....%.H
fffff80003119770  00  00 *09  bd  1f  00  10  00  44  89 *98  04  45  84  c9  0f ........D...E...

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

Let us know the result after performing memtest.

 

[Rotzy]

Ran my first memtest. It ran for 61 hours and completed 36 passes. It was error free until pass 16! Ultimately, there were 3414 errors when I finally stopped it. I assume I need to start testing individual sticks/slots now?

 

[Arc]

Right, do it, as per the instructions koolkat77 will supply now. Following that process, you will be able to discriminate between any faulty module or faulty slot.

 

[koolkat77]

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

:info: Errors are sometimes found after 8 passes.
:tip: Do this test overnight, before going to bed.

 

[Rotzy]

Mixed results from the ram test. Ultimately I was unable to identify a problem stick of ram or motherboard slot. I ran numerous tests on every stick and combination of sticks I could think of and I ran every test for at least 20 passes (some as many as 100). The only failure I encountered was in my middle two motherboard slots when using a 2GB and 1GB stick together, but that was after 24 passes. After more than a week of not using my desktop computer I have decided enough is enough. I put all of my 2GB ram sticks back in (8GB total) in a different order than they were originally. I left out the 1GB stick (it seems to be from a different manufacturer). Lets see how this goes...

 

[Rotzy]

Well, after 3 weeks with no BSODs or random restarts, I'd say we've narrowed the problem down to either a currently unused ram slot or incompatiblity with the 1GB stick of ram I removed. I think I'm going to purchase an additional 8GB and see if it runs smoothly with all motherboard slots full.