Hi pcpd425,
With response to your private message and I've investigated your minidumps. My finding is same as Howard. This is hardware problem and it is very hard to trouble-shoot which hardware component is faulty. Most of BSODs at this site are hardware problem unlike other forums. Most of your minidumps are crashed with bugcheck code 7F and the failing instruction is 'ret'. The crashes are not related to stack overflow and they are crashed due to hardware error. Probably it crashed due to bad ram. Two minidumps are crashed at IRQL x'1C' and this is the timer IRQL. Timer IRQL is stable routine and it crashed only if hardware errors. The culprit may be faulty ram, CPU, PSU, m/b or overheat.
Download prime95 to stress test your hardware and it executes under windows environment.
http://www.mersenne.org/freesoft.htm
Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot. Reseat video card as well.
3. Downclock the ram. Check to default setting if you video card is overclocked.
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
For example : DIMM1 and DIMM2 do not have the same timing.
DIMM1: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz) (2.0-3-3-7 @ 166 MHz)
DIMM2: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
DIMM3: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
7. Make sure that your PSU have adequate power to drive all the hardware including USB devices
8. Run chkdsk /r at command prompt
9. Run 3DMark 2005 to test your video card
10. Upgrade BIOS and make sure that the motherboard has no leaking capacitor.
11. Your nVidia Display Card driver is out of date and outdated nVidia Display card always causes bugcheck code 8E. You had better upgrade it to latest level.
If it still crashes, diagnostic which memory stick is faulty
Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
Your debug reports
Mini011806-01.dmp BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : Unknown_Image ( hal!KeReleaseQueuedSpinLock+30 )
Mini011806-02.dmp BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_EndpointTimeout+199 )
Mini011806-03.dmp BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeReleaseQueuedSpinLockFromDpcLevel+1c )
Mini011906-01.dmp BugCheck 100000D1, {30f2dadc, 1c, 0, 860ebe97}
Probably caused by : ntkrnlmp.exe ( nt!NtDelayExecution+87 -> nt!_SEH_epilog )
Mini011906-02.dmp BugCheck 1000007F, {8, f772fd70, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!_SEH_epilog+c )
Mini011906-03.dmp BugCheck 1000007F, {8, f772fd70, 0, 0}
Probably caused by : win32k.sys ( win32k!_IsChild+24 )
Mini011906-04.dmp BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeReleaseQueuedSpinLockFromDpcLevel+1c )
Mini012006-01.dmp BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_GetEndpointState+95 )
Mini012006-02.dmp BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeReleaseQueuedSpinLockFromDpcLevel+1c )
Mini012006-03.dmp BugCheck 100000D1, {800, 2, 0, 800}
Probably caused by : Unknown_Image
Mini012006-04.dmp BugCheck C2, {41, 85ad5000, 5528, 3ffbf}
Probably caused by : regspy.sys ( regspy+1663 )
Mini012106-01.dmp BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : Vax347b.sys ( Vax347b+dca2 )
Mini012106-02.dmp BugCheck 100000D3, {f38d5ec8, 1c, 0, 804d9650}
Probably caused by : swmidi.sys ( swmidi!MIDIRecorder::InitEventList+1f )
Mini012106-03.dmp BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeReleaseQueuedSpinLockFromDpcLevel+1c )
Mini012106-04.dmp BugCheck 100000D3, {f3801ec8, 1c, 0, 804d9650}
Probably caused by : swmidi.sys ( swmidi!MIDIRecorder::InitEventList+1f )