BSOD ntoskrnl.exe-7f1c0 while idling

[gregrocker]

Make sure the SSD remains set as first drive to boot, after DVD drive.

Does adding back in the HD cause it to not boot?

If so, move the data off the HD to wipe it using Diskpart Clean Command.

Do you know why your HD's were marked Active? Did they previously contain OS's and were not wiped of boot code?

Look over the steps in Clean Reinstall - Factory OEM Windows 7 which are the same for retail. How close did you come before to getting a perfect install? Did you try running with the drivers Win7 (installer and optional Updates) provided, or immediately change them out?

This could still be a hardware problem, possibly something small like a cable. But it wouldn't hurt to get a clean reinstall and wipe the HD of boot code which when plugged in causes the crashes.

 

[natteulven33dk]

Ok i Will try to do that when i get Home

 

[natteulven33dk]

The ssd is set as first boot after DVD

It did boot once with only ssd when I then started it this morning it said on boot mgr

No other hdd was plugged in I did try plugging in one hdd but still the same.

I will when I get home try to make a clean install

And no I dunno why so many was marked as active. Maybe because I set the them to not power down ? Or is that two different things ?

And I usually swap drivers quickly and use the ones supplied on the mb DVD

 

[natteulven33dk]

i have now maked a clean install following the instruction not 100% because im one of those patient people who dont need to do a "backup" of windows so i have nothing against installing all drivers a new if that is what it takes when i need a full re install i only have plugged my SSD in and my DVD currently ..

 

[gregrocker]

This is not XP. Win7 provides the drivers it wants via the installer and optional Windows Updates. You only need to provide drivers which are then missing in Device Manager. Do not change out drivers unless performance problems point to them.

This was why I suggested you reinstall, to see how it performed before changing out drivers. Did you not understand this?

 

[natteulven33dk]

no i must have misunderstood that sorry ill try again because already got BSOD again check back in when i have installed win 7 and only the LAN driver !

 

[gregrocker]

Try running for a good long while without HD plugged in, then with HD.

 

[natteulven33dk]

First BSOD after install

i got a BSOD when i was downloading updates for Windows.. :S so not even gotten to the drivers i was missing yet .. :S i have uploaded the BSOD and a perfmon file so you can see how far i was when The BSOD was showing, its bright blue color of damnation

i know there is alot not installed but taht was the time when i got the BSOD

 

[gregrocker]

Can you isolate the Update which caused the BSOD? See if it was a driver, by System Restoring to before installing Updates, choosing optional Updates first then installing only drivers singly.

Did you build this system yourself? If so then I would rebuild it checking everything with a fine tooth comb.

I notice your last screenshot shows the System Reserved partition to be empty. Look at the latest Disk Mgmt to see if that remains. If so go to Control Panel>FOlder Options>View to unhide System and Hidden Files, in Disk Mgmt rightclick SysReserved to Explore it to see if it has its boot files. You may need to temporarily assign a letter to view it.

Did you run Diskpart Clean Command on the Win7 HD before reinstall. I'd try that to overwrite any possible boot corruption.

What installer are you using? Where did you get it and how it is it burned or written?

 

[carwiz]

It's still showing an I/O error. More specifically, the requested data wasn't at the memory address specified. The particular process, in the last case, was Winint.exe which is a Windows background command processor. (Reads the commands from the .INI file.) This can be used by malware but not likely on a new build.

The problem seems to originate with filling memory. Either memory faults, page faults or disk errors.

The fact that the system started with all the partitions active and the OP not aware of the cause is suspect too. Since an attempt to Clean Install still leads to the F4 error, I'm leaning toward memory faults.

Perhaps re-seating memory modules and/or verifying module placement on the motherboard followed by a memtest should be in order. Might even start by using a single module in Slot-1 and see if the errors continue. Then swap in a different module.

One sad fact for us English speakers is that much of the vital info in the logs and sysinfo for the OP is in Danish.

 

[gregrocker]

There are very specific steps to take to test both sticks and slots: RAM - Test with Memtest86+

Double check that the RAM is spec'd precisely for the mobo.

I wonder if timing would come into play here?

 

[carwiz]

I may shoot myself in the head if turns out to be OC memory.

I say start from scratch and reset the BIOS. At least we'll have a starting point and let the BIOS set-up the memory. I'm reluctant to have the OP install utils like CPU-Z, HWinfo64, etc.

 

[carwiz]

It appears the motherboard will support DDR3-1600 in native mode. The Corsair V modules are 1.5v/1600 at 9-9-9-24 and support XMP. (Nice modules) The motherboard has a specific slot population method though. Odd that it starts in SLOT-2. Here's a snip of module/slot layout from the MB manual.

 

[natteulven33dk]

ok

The windows installer i use is a OEM version bought at the retailer together with the majority of the parts.

I have runned memtest86+ numeous times without any errors.

and my ram is slotted in dimm 2 first and then dimm 4 so they should be inserted correctly i used the manual for that

and it is my first build ever so right now im just thinking why oh why didnt i just by my computer finished that is just annoying

i have NH-D14 CPU cooler and that is hell if i need to take out rams

i when i have looked the 100MB system drive basically always have been empty that is if i can count on what space is used up.. havent checked up on it though.!

 

[natteulven33dk]

I have taken a decision (dunno if that is spelled correctly) to try something different, i took out my 5 year Old HDD from my former computer, installed it in my new, put it in one of the sloweer SATA ports installed win 7 on it, and will now try to see if this runs more stable than my SSD, so i this way may see if it is maybe either the port or the ssd itself ! .

 

[natteulven33dk]

tested just after install on a normal HDD , the ssd again with a new install and it actually made BSOD the normal HDD havent yet done a BSOD ... so my thinking is either the SSD or the Highspeed ports are the problems :S