BSOD - New Install

[Bare Foot Kid]

Hello y'all,

I do not believe this! I just reinstalled and finished with MS Update last night.
Today I boot up and crash! Can anyone help me figure this out, where to find the minidump file?
I will not respond for a while as I am going to boot into Memtest86 when I finish here.
I'll probably let it run for at least 4 hours. It's a start.
This is all I have found so far.
The "temporary copy" is in the temp file and can't open the - Mini043008-01.dmp - file.
I tried to cut/paste this - Mini043008-01.dmp - into start/search and got nothing, just got the same response from "RUN".

View attachment 3663

Thank you; I'll be back!


Later Ted

 

[Bubba]

Have a nice memtest lol.

 

[sidney1st]

1: C\windows\minidump\your dump files are there.
2: To read them: How to read the small memory dump files that Windows creates for debugging
3: Happy memtest

 

[Bare Foot Kid]

Hello y'all,

Two full passes, no errors!

This is deep and I,m sleepy I'll look at it tomorrow. I did install the debugging tool.

How to read the small memory dump files that Windows creates for debugging

Maybe I'll tell this OEM OS to kiss off and get that 10K RPM Raptor and a copy of x64 Ultimate and get it over with; it's what I want to do anyway!

Hello Bubba.
Thanks sidney1st.


Later Ted

 

[Bare Foot Kid]

Hello all,

I was looking at the above, "Warning: If a virus or other security... " and decided that
a thorough Avast scan was in order.

It found this, View attachment 3677

I moved it to the chest as suggested.
Now I haven't looked into this yet but from what Avast said about this, if I understood
it correctly is that this comes through the MS servers?
If this is correct, could it have got in while I was installing SP1 and all its pals?

Well one question at a time. Thank you!

Edit : I just got this from Avast; Win32:SQLSlammer


Later Ted

 

[dmex]

Yeah sneaky buggers arnt they, theres hundreds of SQL slammer attacks floating around the Internet still...

 

[Bare Foot Kid]

Hello dmex,

Yeah it's a big PITA to me; from what I've read the exploit is a couple of years old.
Now that I have studied it more it seems that "Data Execution Prevention" DEP is
responsible for the crashes. It seems as the "worm" was trying to write to the RAM
at boot DEP would crash the system in an attempt to stop it.

Yeah sneaky buggers arnt they, theres hundreds of SQL slammer attacks floating around the Internet still...

Are we having fun yet?


Later Ted