3 BSODs

Mueller1337 · 05 Apr 2011

Windows 7 is
- 64 bit Ultimate
- i had reinstalled windows
- an full OEM version

- the system is 4 month old
- the OS is 6 Days old and yes i reinstalled it.

just 3 other BSODS

Mueller1337 · 06 Apr 2011

lol am i banned from forum??? noby answers my BSODs any more

usasma · 06 Apr 2011

Since you've reinstalled Windows and still have issues - I'd have to suggest starting with this:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Scanners (read the details at the link)

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove 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:


AtiPcie.sys     Tue May 05 11:00:22 2009 (4A005486)
ElbyCDIO.sys    Thu Dec 16 17:58:13 2010 (4D0A9985)
avipbb.sys      Mon Feb 22 05:08:50 2010 (4B8257B2)
amdiox64.sys    Thu Feb 18 10:17:53 2010 (4B7D5A21)
LGBusEnum.sys   Mon Nov 23 20:36:48 2009 (4B0B38B0)
VClone.sys      Sat Jan 15 11:21:04 2011 (4D31C970)
serscan.sys     Mon Jul 13 20:35:32 2009 (4A5BD2D4)
usbfilter.sys   Tue Dec 22 03:26:22 2009 (4B3082AE)
AtihdW76.sys    Wed Nov 17 07:02:04 2010 (4CE3C43C)
avgntflt.sys    Thu Nov 11 10:59:48 2010 (4CDC12F4)
viahduaa.sys    Tue Sep 28 05:53:08 2010 (4CA1BB04)
cpuz135_x64.sys Tue Nov 09 08:33:36 2010 (4CD94DB0)
LGVirHid.sys    Mon Nov 23 20:36:48 2009 (4B0B38B0)

3 different BSOD error codes and 2 different causes blamed. This is, IMO, the beginning of a pattern that says there is a hardware problem.

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Apr  5 14:57:27.503 2011 (UTC - 4:00)
System Uptime: 0 days 1:50:24.063
Probably caused by : ntkrnlmp.exe ( nt!AlpcpQueryTokenModifiedIdMessage+82 )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x19_20_nt!AlpcpQueryTokenModifiedIdMessage+82
Bugcheck code 00000019
Arguments 00000000`00000020 fffff8a0`035a5620 fffff8a0`035a5660 00000000`05040403
BiosVersion = V10.4
BiosReleaseDate = 05/14/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Apr  5 13:06:33.324 2011 (UTC - 4:00)
System Uptime: 0 days 0:13:38.869
Probably caused by : ntkrnlmp.exe ( nt!KiPreBugcheckStackSaveArea+3f5e )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  javaw.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiPreBugcheckStackSaveArea+3f5e
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02c8199e 00000000`00000001 00000000`00000000
BiosVersion = V10.4
BiosReleaseDate = 05/14/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Apr  5 12:52:23.387 2011 (UTC - 4:00)
System Uptime: 0 days 2:43:17.558
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  java.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`00034a52 00000000`00000003 00000000`000234f1
BiosVersion = V10.4
BiosReleaseDate = 05/14/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Mueller1337 · 08 Apr 2011

hello...i tested the hdd and the ram...hd with WD Lifeguard: 0 Errors
and ram with memtest86+ and after 8 passes no error...

but there are 3 new BSODS

PLease help me

usasma · 08 Apr 2011

Please update the drivers mentioned in my previous post.

Next, try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90ºC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
- Click "Quit" to exit

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test: Torture test your CPU with Prime95

Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - ÐœÐ˜Ð NVIDIA / Ð£Ñ‚Ð¸Ð»Ð¸Ñ‚Ñ‹ / VMT
Artifact Locator - ÐœÐ˜Ð NVIDIA / Ð£Ñ‚Ð¸Ð»Ð¸Ñ‚Ñ‹ / Artifact Locator
Sorry, but I don't read the language that this website is made in.

Another interesting test that just came to my attention: Download - OCCT Website english
USE AT YOUR OWN RISK - program doesn't have a whole bunch of safety features to protect you from yourself!

Here's the list of drivers from the latest BSOD's. Compare it to the previous list so you don't waste time updating everything twice:
OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove 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:18:18 2010 (4BA3A3CA)
AtiPcie.sys     Tue May 05 11:00:22 2009 (4A005486)
avipbb.sys      Mon Feb 22 05:08:50 2010 (4B8257B2)
ElbyCDIO.sys    Thu Dec 16 17:58:13 2010 (4D0A9985)
usbfilter.sys   Tue Dec 22 03:26:22 2009 (4B3082AE)
serscan.sys     Mon Jul 13 20:35:32 2009 (4A5BD2D4)
LGBusEnum.sys   Mon Nov 23 20:36:48 2009 (4B0B38B0)
atikmdag.sys    Tue Mar 08 23:32:17 2011 (4D7702D1)
amdiox64.sys    Thu Feb 18 10:17:53 2010 (4B7D5A21)
AtihdW76.sys    Wed Nov 17 07:02:04 2010 (4CE3C43C)
avgntflt.sys    Thu Nov 11 10:59:48 2010 (4CDC12F4)
viahduaa.sys    Tue Sep 28 05:53:08 2010 (4CA1BB04)
cpuz135_x64.sys Tue Nov 09 08:33:36 2010 (4CD94DB0)
LGVirHid.sys    Mon Nov 23 20:36:48 2009 (4B0B38B0)
L1C62x64.sys    Tue Mar 22 01:32:33 2011 (4D883471)

Then, if the BSOD's don't stop, try running Driver Verifier according to these instructions:

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:

Code:

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

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Fri Apr  8 09:20:54.495 2011 (UTC - 4:00)
System Uptime: 0 days 1:34:09.040
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!MiIdentifyPfn+26f
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02b8728f fffff880`073bdc90 00000000`00000000
BiosVersion = V10.4
BiosReleaseDate = 05/14/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Apr  7 14:37:03.455 2011 (UTC - 4:00)
System Uptime: 0 days 1:51:50.000
Probably caused by : cng.sys ( cng!GatherRandomKey+22c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_cng!GatherRandomKey+22c
Bugcheck code 00000050
Arguments ffffffff`fffffbb0 00000000`00000000 fffff800`02abbc0c 00000000`00000000
BiosVersion = V10.4
BiosReleaseDate = 05/14/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Apr  7 07:49:52.635 2011 (UTC - 4:00)
System Uptime: 0 days 1:39:31.806
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+52b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+52b
Bugcheck code 00000050
Arguments fffffc80`ac00001b 00000000`00000000 fffff800`02ab8fb5 00000000`00000007
BiosVersion = V10.4
BiosReleaseDate = 05/14/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``