Hi all,
Experiencing random BSOD's and other various problems. Sometimes windows explorer will keep crashing, or IE8 and Firefox will repeatedly crash or not open at all.
My ASUS M4A78T-E motherboard has all available driver updates from the ASUS website. Graphics card, GeForce 9800GT has driver update from Nvidia site.
I appreciate any help I can get. minidump files are attached.
Sorry, yes since upgrading. Had XP, installed Win7 OEM by booting from DVD, formatting drive, it did not upgrade XP from what I understand about the process.
Whole new system except for the harddrives:
ASUS M4A78T-E drivers updated from ASUS support site
NVIDIA GeForce 9800 GT driver date: 11/20/09
AMD Phenom II x2 545
DDR3 1333 RAM 2x2GB
I know its not the best, but I ran the Memory Test that comes with windows, and it said I had hardware problems. Motherboard site says it supports this RAM, so I went into the BIOS and set the RAM to be recognized as 1333 instead of being set to auto. After reboot, Windows memory test said there were no problems. That was about 2 hours ago, don't know if that really helps or not.
Hi Greg, Welcome to SF,
I believe the problem is with you Memory.Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 31-12-2009 10:02:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x3452, 0x7FEFD869000, 0xFFFFF70001083DD8, 0x72A0000000000000)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\123109-26754-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Thu 31-12-2009 10:02:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002BFA90D, 0x1, 0x8)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\123109-24663-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Thu 31-12-2009 10:02:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x49EF2, 0x0, 0x34EF2)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\123009-28158-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Thu 31-12-2009 10:02:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF6FB400040F0, 0x0, 0x0, 0xFFFFF80002BD7E77)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\123009-27518-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Thu 31-12-2009 10:02:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x888A, 0xFFFFF8A008472888, 0xFFFFF6FC80628FBB, 0xFFFFFA80001AA390)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\123009-27081-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Thu 31-12-2009 10:02:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x888A, 0xFFFFF8A003915108, 0xFFFFF6FB40000163, 0xFFFFFA80019FBD20)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\123009-26332-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Thu 31-12-2009 10:02:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\122909-28329-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Thu 31-12-2009 10:02:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x2, 0x5DC2B, 0x12FFFF, 0x1)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\122909-23946-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Thu 31-12-2009 10:02:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x2, 0x87928, 0x12FFFF, 0x1)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\122809-31855-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Thu 31-12-2009 10:02:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x8CA68, 0x2, 0x8CB67)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\122809-29780-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Thu 31-12-2009 10:02:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x7292E, 0x2, 0x10422D)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\122809-26925-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Thu 31-12-2009 10:02:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x9DBA6, 0x1, 0x9DCA6)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\122709-32729-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Thu 31-12-2009 10:02:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x3452, 0x73812000, 0xFFFFF70001082348, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\122709-28735-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Thu 31-12-2009 10:02:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF680000140B8, 0x0, 0x0, 0xFFFFF80002AA2AE2)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\122709-24429-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
1, Download Memtestx86 and run for 5 passes
2, Run the System Integrity Checker - Start sfc/ scannow right click and Run as Administrator
3, Run the Memory Diagnostics & HD Diagnostic
Hope this helps
Thank you for the advice jack. Ran memtest+86 more than 5 passes, no errors. This was after I changed the BIOS RAM settings to 1333 instead of "auto" detect. Also since that time, no random BSOD, when I should have had at least one when comparing history of them since build. I have had the problem though where IE and Firefox will crash or not open at all, along with windows explorer. A restart fixed that, but it will happen again.
I tried running sfc, nothing comes up if I type in "sfc/ scannow". But I do find sfc if I just type in "sfc". If I just click to run it, or if I right-click to run as admin, it doesn't run. It pops open on the screen and disappears right away. Maybe something to do with my settings? I am logged on as admin, but I haven't set a password if that matters.
Am getting set to run memory diagnostics and HD diagnostics. Will update.
Edit: actually I will not run the memory diagnostics you suggest in #3 since it says to run memtest+86 which I have already done.
Ok, ran HD diagnostics with program from manufacturer's site. No problems.
The only thing is that I haven't been able to run sfc
Something that may be of note:
When all this first started, my first thought was to re-install Win7, since it was a few BSOD's and mainly some funny things with programs crashing or not running. I decided to run the Win7 CD with windows running since I wanted to do a custom install and save files that were on the disk into windows.old. Everything goes fine up until the installation copies files, it will stop at x%, meaning it was random each time I tried. I will then get an error message that says the installation cannot continue because of missing files/can't find required files.
Last edited by Rayger; 02 Jan 2010 at 02:13.
Hi -
There is a space before the forward slash - not after - sfc /scannow - and it is a line command to be executed from a cmd/DOS screen -
START | type cmd.exe | RIGHT-click on cmd.exe above under "Programs" | select "Run as Administrator" | copy/paste or type the following -
Re-boot upon completion.Code:sfc /scannow
Information on the System File Checker -
SFC general info - http://support.microsoft.com/kb/936212
SFC - the CBS log -
http://support.microsoft.com/kb/928228
I ran the 14 dumps and do see the references to memory - but mostly paged memory. I found a driver of interest to me as I have seen many BSODs caused by asio.sys - the Asus PC Probe driver. Your's is from 2007 - before Windows 7's time -
Code:AsIO.sys Mon Dec 17 04:11:49 2007 (47663D55)
Did the BSODs start on Sat Dec 26 19:34:51.545 2009 (GMT-5)? None before that, regardless of OS?
That first dump shows the process running at the time of the BSOD = DAODx.exe - related to Asus mobo software. Do you recall a BSOD while updating your Asus drivers?
I would also suggest that you run the WIndows 7 Upgrade Advisor --> http://www.microsoft.com/Windows/win...e-advisor.aspx
Regards. . .
jcgriff2
.
Code:Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Thu Dec 31 00:51:22.388 2009 (GMT-5) System Uptime: 0 days 0:15:34.871 BugCheck 1A, {3452, 7fefd869000, fffff70001083dd8, 72a0000000000000} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33ab3 ) BUGCHECK_STR: 0x1a_3452 PROCESS_NAME: msdt.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Thu Dec 31 01:14:41.459 2009 (GMT-5) System Uptime: 0 days 0:03:36.942 BugCheck 1E, {ffffffffc0000005, fffff80002bfa90d, 1, 8} Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+11f ) BUGCHECK_STR: 0x1E PROCESS_NAME: WmiPrvSE.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Wed Dec 30 04:26:31.343 2009 (GMT-5) System Uptime: 0 days 0:50:49.686 BugCheck 4E, {99, 49ef2, 0, 34ef2} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) BUGCHECK_STR: 0x4E_99 PROCESS_NAME: firefox.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Wed Dec 30 04:30:13.527 2009 (GMT-5) System Uptime: 0 days 0:02:33.010 BugCheck A, {fffff6fb400040f0, 0, 0, fffff80002bd7e77} Probably caused by : memory_corruption ( nt!MiCaptureAndResetWorkingSetAccessBits+97 ) BUGCHECK_STR: 0xA PROCESS_NAME: svchost.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Wed Dec 30 04:35:51.985 2009 (GMT-5) System Uptime: 0 days 0:04:44.467 BugCheck 1A, {888a, fffff8a008472888, fffff6fc80628fbb, fffffa80001aa390} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35ed2 ) BUGCHECK_STR: 0x1a_888a PROCESS_NAME: SearchProtocol -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Wed Dec 30 05:09:25.931 2009 (GMT-5) System Uptime: 0 days 0:11:35.413 BugCheck 1A, {888a, fffff8a003915108, fffff6fb40000163, fffffa80019fbd20} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35ed2 ) BUGCHECK_STR: 0x1a_888a PROCESS_NAME: iexplore.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Tue Dec 29 04:10:55.908 2009 (GMT-5) System Uptime: 0 days 0:05:47.390 BugCheck 1A, {41287, 0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42c75 ) BUGCHECK_STR: 0x1a_41287 PROCESS_NAME: mmc.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Tue Dec 29 05:59:43.159 2009 (GMT-5) System Uptime: 0 days 1:32:24.626 BugCheck 4E, {2, 5dc2b, 12ffff, 1} Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8e ) BUGCHECK_STR: 0x4E_2 PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Mon Dec 28 07:53:39.478 2009 (GMT-5) System Uptime: 0 days 0:07:22.961 BugCheck 4E, {2, 87928, 12ffff, 1} Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8e ) BUGCHECK_STR: 0x4E_2 PROCESS_NAME: VSSVC.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Mon Dec 28 07:40:49.934 2009 (GMT-5) System Uptime: 0 days 0:03:15.416 BugCheck 4E, {99, 8ca68, 2, 8cb67} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) BUGCHECK_STR: 0x4E_99 PROCESS_NAME: svchost.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Mon Dec 28 07:36:54.163 2009 (GMT-5) System Uptime: 0 days 3:03:08.221 BugCheck 4E, {99, 7292e, 2, 10422d} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) BUGCHECK_STR: 0x4E_99 PROCESS_NAME: firefox.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sat Dec 26 20:36:26.761 2009 (GMT-5) System Uptime: 0 days 1:00:25.245 BugCheck 4E, {99, 9dba6, 1, 9dca6} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) BUGCHECK_STR: 0x4E_99 PROCESS_NAME: VDeck.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sun Dec 27 04:55:00.972 2009 (GMT-5) System Uptime: 0 days 8:06:13.455 BugCheck 1A, {3452, 73812000, fffff70001082348, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33ab3 ) BUGCHECK_STR: 0x1a_3452 PROCESS_NAME: GoogleUpdate.e -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sat Dec 26 19:34:51.545 2009 (GMT-5) System Uptime: 0 days 0:05:45.012 BugCheck A, {fffff680000140b8, 0, 0, fffff80002aa2ae2} Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1c2 ) BUGCHECK_STR: 0xA PROCESS_NAME: DAODx.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- by jcgriff2 J. C. Griffith Microsoft MVP January 2, 2010
Yes, none before that because it is a system I put together brand new, all except for the HDD's. Too many problems with the HDD's (long story, I had an OS on each and couldn't get them to boot in the new build together nor alone) I can't remember if I was able to boot this build with XP or not. Either way, the drive was formatted when I installed Win7.
No, no BSOD's on updating the BIOS or ASUS drivers. In fact after I did them I thought I was good to go.
Thanks for all of the suggestions. I ran System File Checker and it said everything was good to go. That was until I remembered to re-boot. I re-boot and about a minute later I get the BSOD and it specifically says aiso.exe. So I boot in safe mode and uninstall PC Probe. Re-boot and same thing about BSOD, but it indicates aiso.sys. So I re-boot in safe mode again and search for "aiso" and it gives me "aiso.dll" and "aiso.sys". I try to delete those but it said they were no longer there. So I guess the driver is gone with the uninstall, or would system file checker remove it? Do I need to do anything with regedit to make sure?
Thanks for the help thus far
And just to make sure, I did run Win7 compatability and everything is good.
Did you format the drive w/ KillDisk (or similar product) or did you allow Windows 7 to have the honor? If the latter, I would suggest that you low-level format the HDD w/ Killdisk and re-install Windows 7.
KillDisk --> Active@ Kill Disk. Hard Drives Eraser. Free Download.
No nitpicking here, but the Asus probe driver name is ASIO.sys - not AISO.sys
What problems did you have with the HDDs?
Regards. . .
jcgriff2
.
Of course I had Windows 7 do the honor, inexperienced that I am. I should probably do a good format and reinstall. Yes, I messed up "AISO" and "ASIO" in the post.
It wasn't physical problems with the HDD's. I had a japanese XP installed on one and english XP on the other for a dual boot. I bought all new hardware, except for the drives, I put everything together with the drives having the OS's on them and the system wouldn't boot. I'd get the win startup screen for a second, then BSOD with no time to be able to read the error. So I then switched around the drive cables thinking that would help and it didn't. I tried each of the drives alone, and of course that didn't work because of the boot.ini. I put them back in my old system and then researched how to get rid of dual boot, didn't find much, except about editing the boot.ini and just removing the OS from boot.ini that I didn't want to start. The boot.ini was only on one drive, I imagine the 1st one in the boot process in BIOS. I edited it to remove the OS that I didn't want to use, but it wouldn't start the one I wanted to use, it would start the one I removed from the boot.ini for some reason. The drive with the OS that I wanted to use wouldn't boot if installed alone.
So anyway, I put the drive that would boot into the new system and booted it with the Win7 dvd to install. After it was installed, I put the other drive in and formatted that one also.
Anyways, I have just run the system file checker again and it said no problems again. Re-booted just to be sure, and no BSOD yet.
Quote
