BSOD or RESTART randomly, new memory,hard drive, and OS

hey all, okay memtest passed flying colours. verifier caused my pc to go into bsod while the windows 7 loading logo is displayed, it takes a whole few seconds longer than usual to load but then it goes into bsod. but theres a problem, it shows: stop: 0X000000C9 (0X000000000000023E, 0XFFFFF88005069904, OXFFFFF98004358DC0,OX0000000000000000)

>(SOMETHING ABOUT CREATING A DUMPFILE GOES HERE)<

initializing disk for crash dump...


AND THEN IT SITS THERE FOR A LONG TIME, NO RESPONSE, I RESTARTED, EXACTLY YHE SAME, IT JUST HANGS WHERE IT SAYS "INITIALIZING". I THEN RESTARTED AGAIN AND BOOTED TO SAFE MODE AND TURNED VERIFIER OFF AND NOW IM IN NORMAL WINDOWS BOOT AGAIN. DOES THIS HELP? THE DUMP FILE WAS NEVER CREATED THOUGH, I THINK THAT THE PC GETS STUCK BEFORE CREATING STARTS......

I'll try it about 3 more times and see if i get a new dump created

okay........... so this time i did it 8 times, 4 out of 8 was just restart without bsod, the other 4 out of 8 was bsod's, 4 different ones (2 simular ones but with different error codes).

1st one:

stop: 0X000000C9 (0X000000000000023E, 0XFFFFF88005069904, OXFFFFF98004358DC0,OX0000000000000000)

>(SOMETHING ABOUT CREATING A DUMPFILE GOES HERE)<

initializing disk for crash dump...


AND THEN IT SITS THERE FOR A LONG TIME, NO RESPONSE

2nd one:

system_service_exception

>(crap stuff about restarting in safe mode if its the first time happening goes here)<

stop: 0X0000003B (0X00000000C0000005, 0XFFFFF8800112400D, 0XFFFFF880078AFE50,0X0000000000000000)

iastor.sys- Address FFFFF8800112400D BASE AT FFFFF880010CD000, datestamp 49df8075

3rd one:

system_service_exception

>(crap stuff about restarting in safe mode if its the first time happening goes here)<

stop: 0X0000003B (0X00000000C0000005, 0XFFFFF8800126D00D, 0XFFFFF88006A11E50, 0X0000000000000000)

iastor.sys- Address FFFFF8800126D00D base at FFFFF88001216000, datestamp 49df8075

4th one:

stop: 0X000000C9 (0X000000000000023E, 0XFFFFF8800508005858904, OxFFFFF980065F8DC0,OX0000000000000000)
initializing disk for crash dump...

BUT STIL NO MINIDUMP IS WRITTEN, STILL JUST HANGS....

does "system_service_exception" or "iastor.sys" mean anything to you guys? in the past it never showd a filename or system file of any sort, just showed bsod's simular to the 1st and 4th one.....

What is the iastor.sys file?

so according to the link above the iastor.sys is only for hard drives associated with RAID???

mine is AHCI, so does that mean i can delete the file and it wont affect me? or am i jumping the gun?

the attachment shows my AHCI drive

but i cant find this file to maybe use it as an alternative:

francoisdupie said:

What is the iastor.sys file?

so according to the link above the iastor.sys is only for hard drives associated with RAID???

mine is AHCI, so does that mean i can delete the file and it wont affect me? or am i jumping the gun?

the attachment shows my AHCI drive

Related to iaStor.sys Intel Matrix Storage Manager driver - ia32. If you dont think you need it rename it to iastor.bak.

BE SURE YOU HAVE A BACKUP AND A BOOT WIN 7 DVD FIRST.

Without it you may not boot.

Hey zigzag, yeah I needed iastor.sys. System did not want to boot up and got a blue screen showing 0x7b. So after a few hours I was able to get into windows repair (safe mode did not work either) and then I cancel'd that and went into advanced, then command. I then renamed the iastor.sys file back to its origin but that didn't help. So I let windows repair run but it said that it cannot repair the windows and I should send error report to windows. So then I restarted again and used the windows restore point that was created right after I uninstalled avast. Then it booted up again normally. Is there a way of repairing this file? Why do I need it if I don't use raid?

francoisdupie said:

Hey zigzag, yeah I needed iastor.sys. System did not want to boot up and got a blue screen showing 0x7b. So after a few hours I was able to get into windows repair (safe mode did not work either) and then I cancel'd that and went into advanced, then command. I then renamed the iastor.sys file back to its origin but that didn't help. So I let windows repair run but it said that it cannot repair the windows and I should send error report to windows. So then I restarted again and used the windows restore point that was created right after I uninstalled avast. Then it booted up again normally. Is there a way of repairing this file? Why do I need it if I don't use raid?

Why it doesnt work isnt really as important as that it doesnt work. You need a new version and Intel has one.

Okay I'm on my way home then ill check if I can find the download

okay all i could find for updating is the chipset driver, i updated it from intel. but the iastore.sys file still shows the last date and time modified was in 2009....