Win 7 Home Prem X64 BSOD

PeteJ · 19 Apr 2011

Recently I have been experiencing multiple BSOD's on my laptop. I have run WinDbg and the "probable" cause was ntoskrnl.exe.
I had re-installed windows previously and after a few days of the fresh installation the system started experiencing BSOD's especially whilst running Second Life (memory and graphically intensive).

I would very much appreciate any advice and help trying to solve this problem!

PeteJ · 26 Apr 2011

No ideas?

I'm still baffled by what is causing this!

usasma · 27 Apr 2011

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)

The hardware tests are particularly important since you've reinstalled Windows and still have problems.

Please provide this info for a more thorough evaluation: https://www.sevenforums.com/crashes-d...tructions.html

I'm suspecting that this is a hard drive problem. If the hard drive passes the diagnostics, then please do this:

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

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:


iaStor.sys      Thu Dec 17 13:41:59 2009 (4B2A7B77)
amdxata.sys     Tue May 19 13:56:59 2009 (4A12F2EB)
lullaby.sys     Wed Jun 17 22:45:32 2009 (4A39AA4C)
PxHlpa64.sys    Wed Mar 12 21:58:17 2008 (47D88A39)
aswNdis2.sys    Wed Feb 23 09:56:46 2011 (4D65202E)
aswNdis.sys     Sat Jan 09 16:22:03 2010 (4B48F37B)
atikmpag.sys    Fri Jan 22 08:07:54 2010 (4B59A32A)
dump_iaStor.sys Thu Dec 17 13:41:59 2009 (4B2A7B77)
LEqdUsb.Sys     Tue Aug 24 13:21:23 2010 (4C73FF93)
LHidEqd.Sys     Tue Aug 24 13:21:26 2010 (4C73FF96)
LHidFilt.Sys    Tue Aug 24 13:21:36 2010 (4C73FFA0)
LMouFilt.Sys    Tue Aug 24 13:21:43 2010 (4C73FFA7)
TurboB.sys      Thu Aug 06 17:17:31 2009 (4A7B486B)
ASMMAP64.sys    Thu Jul 02 05:13:26 2009 (4A4C7A36)
btwavdt.sys     Thu Jun 25 01:50:13 2009 (4A431015)
btwaudio.sys    Wed Jul 01 09:54:56 2009 (4A4B6AB0)
btwl2cap.sys    Fri Apr 03 20:28:45 2009 (49D6A9BD)
btwrchid.sys    Thu Jun 25 01:51:37 2009 (4A431069)
Sftvollh.sys    Fri Apr 23 15:20:08 2010 (4BD1F2E8)
snp2uvc.sys     Wed Aug 19 22:41:36 2009 (4A8CB7E0)
ATK64AMD.sys    Tue May 12 21:04:54 2009 (4A0A1CB6)
sncduvc.SYS     Mon Dec 29 04:14:26 2008 (495894F2)
ETD.sys         Mon Jan 18 07:37:56 2010 (4B545624)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
Impcd.sys       Mon Oct 26 16:39:41 2009 (4AE6090D)
kbfiltr.sys     Mon Jul 20 05:21:42 2009 (4A643726)
athrx.sys       Mon Oct 05 12:33:57 2009 (4ACA1FF5)
jmcr.sys        Tue Aug 18 04:23:06 2009 (4A8A64EA)
JME.sys         Thu Dec 03 21:14:21 2009 (4B18707D)
HECIx64.sys     Thu Sep 17 15:54:16 2009 (4AB293E8)
atipmdag.sys    Fri Jan 22 08:46:46 2010 (4B59AC46)
CHDRT64.sys     Fri Oct 30 13:50:02 2009 (4AEB274A)
AtiHdmi.sys     Wed Sep 30 09:54:46 2009 (4AC36326)
Sftfslh.sys     Fri Apr 23 15:20:30 2010 (4BD1F2FE)
atksgt.sys      Mon Oct 20 03:50:38 2008 (48FC384E)
lirsgt.sys      Sat Mar 06 14:53:01 2004 (404A2C1D)
Sftredirlh.sys  Fri Apr 23 15:20:39 2010 (4BD1F307)
Sftplaylh.sys   Fri Apr 23 15:20:28 2010 (4BD1F2FC)
aswFW.SYS       Wed Feb 23 09:57:42 2011 (4D652066)
aswTdi.SYS      Wed Feb 23 09:55:51 2011 (4D651FF7)
aswMonFlt.sys   Wed Feb 23 09:55:04 2011 (4D651FC8)

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Mar 12 17:51:19.246 2011 (UTC - 4:00)
System Uptime: 0 days 1:02:24.417
Probably caused by : Ntfs.sys ( Ntfs!NtfsFullDeleteLcb+45 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFullDeleteLcb+45
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0337e718 fffff880`0337df80 fffff800`02cf6538
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar  9 17:52:33.756 2011 (UTC - 4:00)
System Uptime: 0 days 0:13:38.301
BugCheck D1, {fffff880016fec7c, 2, 8, fffff880016fec7c}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+2ad0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  Steam.exe
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_Ntfs!_??_::NNGAKEGL::_string_+2ad0
Bugcheck code 000000D1
Arguments fffff880`016fec7c 00000000`00000002 00000000`00000008 fffff880`016fec7c
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar  9 17:18:21.020 2011 (UTC - 4:00)
System Uptime: 0 days 4:32:07.190
Probably caused by : memory_corruption ( nt!MiRemoveLowestPriorityStandbyPage+24b )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiRemoveLowestPriorityStandbyPage+24b
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02d3c24b 00000000`00000000 ffffffff`ffffffff
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

PeteJ · 07 May 2011

Memtest+ did 9 passes with no errors (will run again for approx 20 passes to ensure)
Seagate HDD Diagnostics found no fault with the HDD
CHKDSK found no errors

I have attached the log produced by the BSOD Dump & System File Collection app.

usasma · 07 May 2011

After we're finished troubleshooting your issues here, please visit the PC manufacturer's website and update ALL drivers.
Then visit Windows Update...Important Updates - and download/install Service Pack 1. This is important for the reliable functioning of your system.

This device is disabled:

BT-253 USB\VID_0B05&PID_1751\0025D3AF6084 This device is disabled.

Is this deliberate? If so, why?
It's most likely a BlueTooth device. If this is the case, then please uninstall the software for it, then physically remove the device from the system. If unable to remove the device, please disable it in the BIOS.

I wonder about your Avast Internet Security - we'll test that later on (please remind me if I forget).

15 more memory dumps to analyze......will post back when they're finished running....

PeteJ · 07 May 2011

I think that is the bluetooth, the tray icon reports it is disabled.
Thank you for the help, it is very much appreciated!

usasma · 07 May 2011

15 memory dumps
8 different BSOD error codes
3 different causes blamed
Most probably a hardware error - but only 3 causes being blamed makes this unusual.

Please uninstall the program that uses the driver from 2004 in this list. Also, please update the other drivers in this list:
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:


iaStor.sys      Thu Dec 17 13:41:59 2009 (4B2A7B77)
amdxata.sys     Tue May 19 13:56:59 2009 (4A12F2EB) - Windows Update will handle this file
lullaby.sys     Wed Jun 17 22:45:32 2009 (4A39AA4C)
PxHlpa64.sys    Wed Mar 12 21:58:17 2008 (47D88A39)
Impcd.sys       Mon Oct 26 16:39:41 2009 (4AE6090D)
aswNdis2.sys    Wed Feb 23 09:56:46 2011 (4D65202E)
aswNdis.sys     Sat Jan 09 16:22:03 2010 (4B48F37B)
ETD.sys         Mon Jan 18 07:37:56 2010 (4B545624)
atksgt.sys      Mon Oct 20 03:50:38 2008 (48FC384E)
dump_iaStor.sys Thu Dec 17 13:41:59 2009 (4B2A7B77) - this file will be updated when you update the iaStor.sys file
Sftvollh.sys    Fri Apr 23 15:20:08 2010 (4BD1F2E8)
TurboB.sys      Thu Aug 06 17:17:31 2009 (4A7B486B)
ASMMAP64.sys    Thu Jul 02 05:13:26 2009 (4A4C7A36)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
aswFW.SYS       Wed Feb 23 09:57:42 2011 (4D652066)
aswTdi.SYS      Wed Feb 23 09:55:51 2011 (4D651FF7)
aswRdr.SYS      Wed Feb 23 09:55:11 2011 (4D651FCF)
atikmpag.sys    Fri Jan 22 08:07:54 2010 (4B59A32A)
snp2uvc.sys     Wed Aug 19 22:41:36 2009 (4A8CB7E0)
ATK64AMD.sys    Tue May 12 21:04:54 2009 (4A0A1CB6)
JME.sys         Thu Dec 03 21:14:21 2009 (4B18707D)
athrx.sys       Mon Oct 05 12:33:57 2009 (4ACA1FF5)
AtiHdmi.sys     Wed Sep 30 09:54:46 2009 (4AC36326)
HECIx64.sys     Thu Sep 17 15:54:16 2009 (4AB293E8)
jmcr.sys        Tue Aug 18 04:23:06 2009 (4A8A64EA)
kbfiltr.sys     Mon Jul 20 05:21:42 2009 (4A643726)
atipmdag.sys    Fri Jan 22 08:46:46 2010 (4B59AC46)
LHidEqd.Sys     Tue Aug 24 13:21:26 2010 (4C73FF96)
LHidFilt.Sys    Tue Aug 24 13:21:36 2010 (4C73FFA0)
LMouFilt.Sys    Tue Aug 24 13:21:43 2010 (4C73FFA7)
CHDRT64.sys     Fri Oct 30 13:50:02 2009 (4AEB274A)
sncduvc.SYS     Mon Dec 29 04:14:26 2008 (495894F2)
LEqdUsb.Sys     Tue Aug 24 13:21:23 2010 (4C73FF93)
Sftredirlh.sys  Fri Apr 23 15:20:39 2010 (4BD1F307)
cpuz135_x64.sys Tue Nov 09 08:33:36 2010 (4CD94DB0)
lirsgt.sys      Sat Mar 06 14:53:01 2004 (404A2C1D)
npf.sys         Fri Jun 25 12:50:58 2010 (4C24DE72)
Sftfslh.sys     Fri Apr 23 15:20:30 2010 (4BD1F2FE)
Sftplaylh.sys   Fri Apr 23 15:20:28 2010 (4BD1F2FC)
aswFsBlk.SYS    Wed Feb 23 09:54:56 2011 (4D651FC0)
btwavdt.sys     Thu Jun 25 01:50:13 2009 (4A431015)
btwaudio.sys    Wed Jul 01 09:54:56 2009 (4A4B6AB0)
btwl2cap.sys    Fri Apr 03 20:28:45 2009 (49D6A9BD)
btwrchid.sys    Thu Jun 25 01:51:37 2009 (4A431069)

If that doesn't find the cause/fix the problem, then 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!

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Apr 27 17:34:37.243 2011 (UTC - 4:00)
System Uptime: 0 days 3:25:17.789
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`9e8a24fa b3b7465e`f106f6f0 fffff800`0303ffd0 00000000`00000001
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Apr 18 17:54:01.059 2011 (UTC - 4:00)
System Uptime: 0 days 1:03:59.604
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SecondLife.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff800`03040380 fffff880`05bf1b00 00000000`00000000
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Apr 13 19:19:01.061 2011 (UTC - 4:00)
System Uptime: 0 days 5:51:27.231
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`9ea69847 b3b7465e`f1236a3d fffff800`0303fe70 00000000`00000001
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Apr 10 18:26:13.950 2011 (UTC - 4:00)
System Uptime: 0 days 0:43:46.496
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
PROCESS_NAME:  SecondLife.exe
BUGCHECK_STR:  RAISED_IRQL_FAULT
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_RAISED_IRQL_FAULT_SecondLife.exe_nt!KiSystemServiceExit+245
Bugcheck code 0000004A
Arguments 00000000`74c02dd9 00000000`00000002 00000000`00000000 fffff880`09573ca0
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Apr 10 17:41:50.172 2011 (UTC - 4:00)
System Uptime: 0 days 0:34:40.717
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SecondLife.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiReplenishPageSlist+100
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02c9ab7f 00000000`00000000 ffffffff`ffffffff
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Apr  4 19:58:08.121 2011 (UTC - 4:00)
System Uptime: 0 days 1:11:18.292
Probably caused by : memory_corruption ( nt!MiGetTopLevelPfn+65 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!MiGetTopLevelPfn+65
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02d4f165 fffff880`06274ca0 00000000`00000000
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Apr  3 15:36:28.608 2011 (UTC - 4:00)
System Uptime: 0 days 0:12:05.153
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`9d24f5ce b3b7465e`efa1c7c4 fffff800`0303ff70 00000000`00000001
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Apr  3 12:34:08.226 2011 (UTC - 4:00)
System Uptime: 0 days 2:58:44.397
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  SLVoice.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`0304054a 00000000`00000000 ffffffff`ffffffff
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar 30 17:22:55.455 2011 (UTC - 4:00)
System Uptime: 0 days 4:06:00.626
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_64
Bugcheck code 00000109
Arguments a3a039d8`9e40453a b3b7465e`f0bd1730 fffff800`03040000 00000000`00000001
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar 29 18:29:17.329 2011 (UTC - 4:00)
System Uptime: 0 days 1:24:40.874
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  AvastUI.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 fffff800`030404fc
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Mar 28 17:28:03.229 2011 (UTC - 4:00)
System Uptime: 0 days 1:46:16.774
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SecondLifeDeve
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiReplenishPageSlist+100
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02cadb7f 00000000`00000000 ffffffff`ffffffff
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Mar 26 20:06:07.232 2011 (UTC - 4:00)
System Uptime: 0 days 1:19:23.777
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`995e9709 b3b7465e`ebdb690f fffff800`0303f960 00000000`00000001
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Mar 26 18:46:06.803 2011 (UTC - 4:00)
System Uptime: 0 days 3:30:16.348
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`00097ac8 00000000`00000005 a0429316`9d99e0e2
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar 23 00:02:34.829 2011 (UTC - 4:00)
System Uptime: 0 days 0:17:25.000
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bb2 )
BUGCHECK_STR:  0x1a_41201
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchProtocol
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13bb2
Bugcheck code 0000001A
Arguments 00000000`00041201 fffff680`003be760 26800001`2d556025 fffffa80`03dd38f0
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar 16 05:12:24.429 2011 (UTC - 4:00)
System Uptime: 0 days 12:30:57.600
Probably caused by : memory_corruption ( nt!MiEmptyPageAccessLog+dc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MiEmptyPageAccessLog+dc
Bugcheck code 00000050
Arguments ffffc8cb`925e581a 00000000`00000000 fffff800`02ddb81c 00000000`00000007
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar 15 16:40:38.741 2011 (UTC - 4:00)
System Uptime: 0 days 1:13:29.912
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`9cdbb583 b3b7465e`ef588779 fffff800`0303ff70 00000000`00000001
BiosVersion = K52JK.202
BiosReleaseDate = 02/09/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 430  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed: 2261
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

PeteJ · 07 May 2011

when trying to enable system restor I get the following error: There was an unexpected error in the property page: The filename, directory name, or volume label syntax is incorrect (0x8007007B)

please close the property page and try again

*Managed to enable after disabling then re-enabling

*Can't find program related to lirsgt.sys

usasma · 07 May 2011

1 - Make a system restore point
2 - go to C:\Windows\System32\drivers and rename lirsgt.sys to lirsgt.BAK
3 - if the system refuses to boot, go into Safe Mode and use System Restore to restore the system to the earlier restore point.

PeteJ · 08 May 2011

I have restored the disk image from the hidden partition. I have run windows update several times to receive all the latest updates and install SP1.
I have not reinstalled avast instead AVG free and I have not re-partitioned the hard disk drive to install linux.
I have enabled system restore and created a restore point after SP1 installed.

So far so good but as before BSODs were "random" (most seemed to occur when running second life) so if I can go a few days without a blue screen I would consider the fault most likely software.

* System Froze again while downloading portal 2 from steam, this is looking like a hardware issue and therefore I will be contacting Asus asap.