BSOD shortly after startup during first few attempts

[Hilol]

After having a BSOD problem that left no dump file, it seems my problems have returned a few days later. Luckily a dump file was created this time. The BSOD occurs shortly after startup for the first few attempts after which it will work correctly. Virus scan is clean and booting in safe mode seems to prevent it from crashing. Thanks!

On a side note, the dm log collector seems to delete the folder and leave a empty zip file after finishing. I was only able to get a part of the logs needed.
I can't attach the file using the normal method, so here's a link: https://dl.dropboxusercontent.com/s/xgi1xttvcbaswlz/SFdebugFiles.rar?dl=0

 

[Boozad]

Can you run the Log Collector again please, sometimes it may take three runs or so to catch everything.

 

[Hilol]

Can you run the Log Collector again please, sometimes it may take three runs or so to catch everything.

Strange, the dm log collector deletes everything in the folder just as it begins to compress them. It doesn't seem to happen if it can't find a minidump, though. Here's everything excluding the minidump which can be found in the original post.

 

[Boozad]

Intel Rapid Storage. Are you using a RAID setup?

fffff880`118aeea8  fffff880`04ac0000Unable to load image iaStorF.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for iaStorF.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorF.sys[/COLOR]
 iaStorF+0x6000

 

[Hilol]

Intel Rapid Storage. Are you using a RAID setup?

fffff880`118aeea8  fffff880`04ac0000Unable to load image iaStorF.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for iaStorF.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorF.sys[/COLOR]
 iaStorF+0x6000

No, but i am using a 500GB 850 EVO as my main drive and a 1TB internal HDD for miscellaneous media storage. I've had it setup like this for about 7 months.

 

[Boozad]

Uninstall Intel Rapid Storage, that should solve the issue.

 

[Hilol]

Uninstall Intel Rapid Storage, that should solve the issue.

Another BSOD, I wasn't at my computer when it happened and a new dump file was created. I'll attach a new set of logs just in case something new has happened.

 

[Boozad]

I'll have to look at these tomorrow, please send me a PM if I haven't replied in 24 hours.

 

[Boozad]

Sorry for the delay Hilol, I've been very busy the past few days. This dump is blaming your Realtek 8167 Gigabit ethernet controller driver. It's old and needs updating, check here for an updated version.

fffff880`16b76458  fffff880`0869b2b4Unable to load image Rt64win7.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys[/COLOR]
 Rt64win7+0x1f2b4

11: kd> lmvm Rt64win7
start             end                 module name
fffff880`0867c000 fffff880`08743000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        [COLOR=Red]Wed Dec 26 17:17:50 2012[/COLOR] (50DB313E)
    CheckSum:         000CDEEE
    ImageSize:        000C7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Hilol]

Sorry for the delay Hilol, I've been very busy the past few days. This dump is blaming your Realtek 8167 Gigabit ethernet controller driver. It's old and needs updating, check here for an updated version.

fffff880`16b76458  fffff880`0869b2b4Unable to load image Rt64win7.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys[/COLOR]
 Rt64win7+0x1f2b4

11: kd> lmvm Rt64win7
start             end                 module name
fffff880`0867c000 fffff880`08743000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        [COLOR=Red]Wed Dec 26 17:17:50 2012[/COLOR] (50DB313E)
    CheckSum:         000CDEEE
    ImageSize:        000C7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I think the problem has been solved. Thank you, i really wish i could do something to repay you.

 

[Boozad]

You're more than welcome, I'm glad to hear things are looking good. When you're happy the problem is sorted feel free to mark the thread as Solved, and if you experience any more issues post back straight away.

 

[Hilol]

You're more than welcome, I'm glad to hear things are looking good. When you're happy the problem is sorted feel free to mark the thread as Solved, and if you experience any more issues post back straight away.

I actually got another BSOD a few minutes after boot, I'll post back when it makes a dump file.

Edit: Error code is 0xC4, still no dump file. My google-fu is failing me when looking up the error code.

 

[Boozad]

A 0xC4 is a DRIVER_VERIFIER_DETECTED_VIOALTION STOP. Do you have Driver Verifier enabled? If so, disable it. If you don't then it's possible that the crash was caused by a driver but without a dump there's nothing I can do unfortunately.

 

[Hilol]

A 0xC4 is a DRIVER_VERIFIER_DETECTED_VIOALTION STOP. Do you have Driver Verifier enabled? If so, disable it. If you don't then it's possible that the crash was caused by a driver but without a dump there's nothing I can do unfortunately.

I got another blue screen with a different error code. I took a picture just in case it could be useful to you.
http://i.imgur.com/KOnhldx.jpg

 

[Boozad]

Can you run the Log Collector again to see if a mini dump was created.

 

[Hilol]

Can you run the Log Collector again to see if a mini dump was created.

Unfortunately, none was saved because the blue screen locks up and won't do anything for several minutes. Any blue screen that doesn't freeze usually finishes in a few seconds.

 

[Boozad]

Again this could be a driver trying to write to read-only memory, but without the dump it's impossible to say. There's a possibility it could be RAM but we can rule that out.

Download and run MemTest86+ to test your RAM. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Note

Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

 

[Hilol]

Again this could be a driver trying to write to read-only memory, but without the dump it's impossible to say. There's a possibility it could be RAM but we can rule that out.

Download and run MemTest86+ to test your RAM. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Note

Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

I ran memtest86 over 2 nights and it didn't come up with any errors both times. I'm starting to use a temporary solution of simply never turning my computer off for long periods of time since the blue screens only occur after the computer has been off for several hours. I'll just log off and restart it once in a while to prevent possible issues that could arise from leaving it on for long periods of time.

This is just temporary until i get parts to replace what could be causing it and, just to be safe, a clean reinstall of windows.