BSOD several times a day every day

[NYFIREGUY]

Is Windows 7 Home Premium x64
OEM Pre-Installed On an Emachine that I just purchased.

I get a BSOD every so often its driving me nuts, I tried to turn off wifi and turnoff different components, nothing seems to solve the issue.

This is my first time Posting on a site like this, I see you guys are very knowledgeable and I hope you guys can help me.

I tried debugging the issues and reading the mini dump but im not that good at it.

Ive attached all the minidumps and performance monitor stats up. thank you very much.

 

[ttran]

Hi and Welcome to SF!!!

The results from the DMP files do not give a definitive answer. While we investigate further here are a few things that you can do.

1-Run a system file check to verify and repair you system files. You do this by typing cmd in search, then right click and run as admin. SFC /SCANNOW

2-Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
3-Event viewer
Go into event viewer (type eventvwr in search). Go to the windows log>application tab.

You want to look for critical errors (they have red in the left column ).

When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

When you find them please note the event ID, and the source codes and tell us what they are.

4-Device manager
Please go to start>search>type device manager.
Are there any "unknown devices" with yellow triangles on them?
Is you driver there , listed, and working?

If y our driver is missing, or there is a yellow triangle on it, you will need to update it.

5-Driver verifier
please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[reventon]

Hi,

A lot of BSODs but no clear cause. Run Driver Verifier as ttran mentioned above.

One potential BSOD cause that you can deal with immediately is the presence of Norton on the system. Norton is notorious for causing BSODs, and when we see it we have to recommend removal.

Norton Removal Instructions -> NIS/ N360 Removal -- jcgriff2.com

Regards,
Reventon

BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 29 13:25:22.533 2010 (GMT+12)
System Uptime: 0 days 0:25:45.296
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`02ca92b3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 29 12:59:09.263 2010 (GMT+12)
System Uptime: 1 days 5:13:50.026
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+221f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02ff1334 00000000`00000002 00000000`00000008 fffff800`02ff1334
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 23:34:07.785 2010 (GMT+12)
System Uptime: 0 days 13:57:07.533
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+221f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02fb7334 00000000`00000002 00000000`00000008 fffff800`02fb7334
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 09:36:19.720 2010 (GMT+12)
System Uptime: 0 days 2:02:42.468
Probably caused by : ntkrnlmp.exe ( nt!PspUnhandledExceptionInSystemThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02fefc60 00000000`00000002 00000000`00000008 fffff800`02fefc60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 07:32:20.742 2010 (GMT+12)
System Uptime: 0 days 1:57:31.505
Probably caused by : ntkrnlmp.exe ( nt!PspUnhandledExceptionInSystemThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02fe7c60 00000000`00000002 00000000`00000008 fffff800`02fe7c60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 05:33:53.731 2010 (GMT+12)
System Uptime: 0 days 0:42:51.494
Probably caused by : ntkrnlmp.exe ( nt!PspUnhandledExceptionInSystemThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02feac60 00000000`00000002 00000000`00000008 fffff800`02feac60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 04:46:40.195 2010 (GMT+12)
System Uptime: 0 days 2:32:55.958
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`00000000 00000000`00000002 00000000`00000000 fffff800`02ce32b3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Aug 26 03:38:51.763 2010 (GMT+12)
System Uptime: 0 days 0:35:13.527
Probably caused by : ntkrnlmp.exe ( nt!PspUnhandledExceptionInSystemThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`0303fc60 00000000`00000002 00000000`00000008 fffff800`0303fc60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Aug 26 03:02:23.794 2010 (GMT+12)
System Uptime: 0 days 0:29:24.558
Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+1d7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02c97448 fffff880`083737d8 fffff880`08373040
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Aug 25 07:17:37.639 2010 (GMT+12)
System Uptime: 0 days 1:37:01.402
Probably caused by : ntkrnlmp.exe ( nt!PspUnhandledExceptionInSystemThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`03034c60 00000000`00000002 00000000`00000008 fffff800`03034c60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Aug 25 05:39:39.626 2010 (GMT+12)
System Uptime: 0 days 0:48:33.389
Probably caused by : ntkrnlmp.exe ( nt!PspUnhandledExceptionInSystemThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02fe6c60 00000000`00000002 00000000`00000008 fffff800`02fe6c60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Aug 25 04:50:19.626 2010 (GMT+12)
System Uptime: 0 days 1:27:44.389
Probably caused by : ntkrnlmp.exe ( nt!PspUnhandledExceptionInSystemThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02ff2c60 00000000`00000002 00000000`00000008 fffff800`02ff2c60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Aug 25 03:21:44.748 2010 (GMT+12)
System Uptime: 0 days 0:28:45.496
Probably caused by : ntkrnlmp.exe ( nt!PspUnhandledExceptionInSystemThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02fe5c60 00000000`00000002 00000000`00000008 fffff800`02fe5c60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Aug 25 02:51:44.826 2010 (GMT+12)
System Uptime: 0 days 0:35:12.574
Probably caused by : ntkrnlmp.exe ( nt!PspUnhandledExceptionInSystemThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02feec60 00000000`00000002 00000000`00000008 fffff800`02feec60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Aug 24 02:49:07.118 2010 (GMT+12)
System Uptime: 0 days 19:43:33.866
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+221f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02f9c334 00000000`00000002 00000000`00000008 fffff800`02f9c334
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 23 07:04:19.794 2010 (GMT+12)
System Uptime: 0 days 0:48:37.542
Probably caused by : ntkrnlmp.exe ( nt!PspUnhandledExceptionInSystemThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02ffac60 00000000`00000002 00000000`00000008 fffff800`02ffac60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 22 23:16:49.796 2010 (GMT+12)
System Uptime: 0 days 9:57:37.544
*** WARNING: Unable to verify timestamp for EloBus.sys
*** ERROR: Module load completed but symbols could not be loaded for EloBus.sys
Probably caused by : EloBus.sys ( EloBus+1de9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02f9a334 00000000`00000002 00000000`00000008 fffff800`02f9a334
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 22 13:17:52.668 2010 (GMT+12)
System Uptime: 2 days 10:24:58.416
Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+1d7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02cd9448 fffff880`08f3c7d8 fffff880`08f3c040
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 20 02:51:40.515 2010 (GMT+12)
System Uptime: 0 days 0:28:18.278
Probably caused by : ntkrnlmp.exe ( nt!PspUnhandledExceptionInSystemThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02fe9c60 00000000`00000002 00000000`00000008 fffff800`02fe9c60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 20 02:22:06.635 2010 (GMT+12)
System Uptime: 0 days 19:54:12.383
Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+1d7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02ce8448 fffff880`091087d8 fffff880`09108040
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Aug 19 06:26:38.566 2010 (GMT+12)
System Uptime: 0 days 0:36:13.329
Probably caused by : ntkrnlmp.exe ( nt!PspUnhandledExceptionInSystemThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`03038c60 00000000`00000002 00000000`00000008 fffff800`03038c60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Aug 19 05:49:39.629 2010 (GMT+12)
System Uptime: 0 days 0:34:53.377
Probably caused by : ntkrnlmp.exe ( nt!PspUnhandledExceptionInSystemThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02feec60 00000000`00000002 00000000`00000008 fffff800`02feec60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Aug 19 05:13:58.841 2010 (GMT+12)
System Uptime: 0 days 1:40:04.589
Probably caused by : ntkrnlmp.exe ( nt!PspUnhandledExceptionInSystemThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`03028c60 00000000`00000002 00000000`00000008 fffff800`03028c60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Aug 19 03:33:04.803 2010 (GMT+12)
System Uptime: 0 days 1:13:44.567
Probably caused by : ntkrnlmp.exe ( nt!PspUnhandledExceptionInSystemThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02feec60 00000000`00000002 00000000`00000008 fffff800`02feec60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Aug 19 02:18:06.763 2010 (GMT+12)
System Uptime: 0 days 6:48:20.527
Probably caused by : ntkrnlmp.exe ( nt!PspUnhandledExceptionInSystemThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02fecc60 00000000`00000002 00000000`00000008 fffff800`02fecc60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Aug 18 19:28:35.182 2010 (GMT+12)
System Uptime: 0 days 0:01:51.946
Probably caused by : ntkrnlmp.exe ( nt!KeReleaseSemaphore+38 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000001 fffff800`02c902a8
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/font]

 

[NYFIREGUY]

I will try the above .. Thank you for your quick response. ive already removed norton that came with the system, But i will get back to you guys with my results... I was going through the computers cycle of operations and i was thinking it might have something to do with power managmnt.... i will follow your instructions and respond with my results.. thanks again for the very quick reply.

 

[NYFIREGUY]

AWESOME I restarted the computer after removing norton as per the instructions. and restarted... then got a BSOD (Memory managment) LOL . atleast it wasnt an IRQ NOT LESS OR EQUAL TOO... this happened about 60 seconds after entering into windows. ill post the mini dump.

 

[reventon]

Hi,

I looked at the previous dumps aswell and I noticed that EloBus.sys was mentioned in one of them - this is a touchscreen/tablet driver. Update from the manufacturer's site.

Nothing too informative from the recent dumps - apart from rdyboost.sys being mentioned in one. It may be worth turning Readyboost off for now.

Run Driver Verifer - http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Regards,
Reventon


BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 30 14:28:00.284 2010 (GMT+12)
System Uptime: 0 days 0:01:49.047
Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e )
BUGCHECK_STR:  0x1a_1236
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
Bugcheck code 0000001A
Arguments 00000000`00001236 fffffa80`03284450 fffffa80`03284558 00000000`0001022b
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 30 02:27:02.187 2010 (GMT+12)
System Uptime: 0 days 13:00:57.950
Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+1d7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02cec448 fffff880`009e77d8 fffff880`009e7040
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]