Had a blue screen of death and have system issues

Let's just wait and see what happens.

NOTE: I have severe eye problems. If I do not respond to your postings, please PM another staff member for assistance.

Turn off Driver Verifier - it's designed to cause BSOD's. In this case the memory dump blames the kernel (core) of the OS (which is unlikely). So this is most likley a hardware error, but could also be a compatibility problem, a low=level driver problem, malware, or a Windows problem.

For starters, you must update the older drivers on your system (in the list below) - paying particular attention to those highlighted in RED:
OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

Code:

amdxata.sys                 Fri Mar 19 12:19:01 2010 (4BA3A3F5)
giveio.sys                  Wed Apr 03 22:33:25 1996 (316334F5)
aswNdis.sys                 Wed Jan 06 15:04:01 2010 (4B44ECB1)
SCDEmu.SYS                  Sun Nov 08 22:21:19 2009 (4AF78AAF)
nvlddmkm.sys                Wed Aug 03 05:06:24 2011 (4E390F90)
HECI.sys                    Mon Jul 09 13:40:18 2007 (46927302)
e1e6232.sys                 Fri Mar 26 04:13:32 2010 (4BAC6CAC)
GEARAspiWDM.sys             Mon May 18 08:16:53 2009 (4A1151B5)
pcouffin.sys                Tue Dec 05 09:39:53 2006 (457584B9)
AmUStor.SYS                 Tue May 26 09:32:55 2009 (4A1BEF87)
aswMonFlt.sys               Tue Sep 06 16:36:25 2011 (4E668449)
000.fcl                     Fri Sep 26 09:11:12 2008 (48DCDF70)
TuneUpUtilitiesDriver32.sys Thu Sep 17 07:54:55 2009 (4AB2238F)

http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#giveio.sys
http://www.carrona.org/dvrref.html#aswNdis.sys
http://www.carrona.org/dvrref.html#SCDEmu.SYS
http://www.carrona.org/dvrref.html#nvlddmkm.sys
http://www.carrona.org/dvrref.html#HECI.sys
http://www.carrona.org/dvrref.html#e1e6232.sys
http://www.carrona.org/dvrref.html#GEARAspiWDM.sys
http://www.carrona.org/dvrref.html#pcouffin.sys
http://www.carrona.org/dvrref.html#AmUStor.SYS
http://www.carrona.org/dvrref.html#aswMonFlt.sys
http://www.carrona.org/dvrref.html#000.fcl
http://www.carrona.org/dvrref.html#TuneUpUtilitiesDriver32.sys

I cannot open your MSINFO32 report. Please do the following:

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

BSOD BUGCHECK SUMMARY

Code:

Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\110411-38234-01.dmp]
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Debug session time: Fri Nov  4 23:39:46.406 2011 (UTC - 4:00)
System Uptime: 0 days 0:08:02.218
Probably caused by : ntkrpamp.exe ( nt!NtMapViewOfSection+0 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x1
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x1_VRF_SysCallNum_a8_nt!NtMapViewOfSection+0
Bugcheck code 00000001
Arguments 82e9c43a 00000000 0000ffff 00000000
BiosVersion = MQ96510J.86A.1687.2007.0510.0258
BiosReleaseDate = 05/10/2007
CPUID:        "Intel(R) Celeron(R) CPU        E1400  @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1998
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  

BTW - with my eye problems I can't go through the CBS log file.
As for the other errors - let's see what happens with them after we fix the BSOD error.

Okay, The HECI.sys I cannot update. Should I disable the Intel Management Engine Interface? I know when I installed the driver for it the last time, it didn't completely go through the installation, but it did install the driver. The Pcouffin.sys is tied to two programs in which I use, which is DvdFab and ConvertXtoDVD. Is Pcouffin.sys necessary to have or do you know? I uninstalled speedfan which rid me of the giveio.sys driver. I updated the Nvidia display driver, I updated PowerISO, which updated that driver. I cannot update any of the other drivers. Do you think I might have a windows problem? Is there something I can replace from my Win 7 installation disc?

You're running a new OS (Win7) on old hardware (the mobo). The device manufacturer's (for the devices on your mobo) may not support Win7. This may mean that you'll have to get a new mobo (and maybe other hardware) in order to run Win7 without problems. BUT, let's see what we can do before we go that route.

Go to the Intel Download Center ( http://downloadcenter.intel.com ) and search for the Win7 version of the Management Engine. I believe that this is the proper download, but double check me as my eyes are failing: http://downloadcenter.intel.com/Deta...ne%22&lang=eng

The pcouffin.sys dates from before Win7 came out. If you must continue using those programs you must update them to a Win7 compatible version. But, here's a suggestion:

Uninstall the 2 programs while we're troubleshooting. Once we've fixed the BSOD issues, then you can reinstall the programs if you so choose. If the system starts to BSOD again - then you'll know it's the pcouffin.sys causing it.

You may want to research updates for your BIOS also - but only read up on them to see if any may apply to your problem. Flashing the BIOS is a very dangerous operation. One small mistake or even just a key press can turn your motherboard into a doorstop.

If you get the exact same motherboard make and model you'll probably be able to keep the current Win7 installation - bu that won't necessarily solve the problem if the mobo isn't compatible with Win7. The closer you can get to that motherboard (in a Win7 compatible version) the more likely it is that it'll work properly. There's also the possibility of a repair install of Windows to repair any glitches that may occur.

Compatibility isn't just a listing on a chart - it's how the drivers are designed, and how the company decides if it will offer tech support for problems with that OS. We spend a lot of time here assisting folks with their compatibility issues - but in the end there's just no guarantee that it's gonna work.

Don't forget to check the BIOS updates for your system. Since your BIOS dates from 2007, there may be updates for it that will assist in fixing some of the comaptibility issues.