Sony Laptop Throwing Random BSODs

Status
Not open for further replies.

SpikedCola

Posts: 11   +0
My parents asked me to look at their laptop and Im pretty much stumped. The first things included running MemTest86+ for 12h with no errors, and a hard drive test which I dont remember the name of. The bluescreens started about a month after I did a clean install of XP, with no apparent cause (I did notice a lot of references to windows files but I dont know where to go from there). I have since analyzed every minidump looking for patterns, but that hasnt helped. Im posting the details of each dump here, so hopefully someone will be able to tell me where to look. I wont be home for about a week to try your suggestions out, but that should give me plenty of time to put together a game plan :)

Dump anaysis:

Mini050908-01.dmp.log
IRQL_NOT_LESS_OR_EQUAL (0x0000000A)
Probably caused by : rdbss.sys
---
Mini052508-01.dmp.log
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
Probably caused by : pci.sys
---
Mini052508-02.dmp.log
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
Probably caused by : pci.sys
---
Mini113008-01.dmp.log
IRQL_NOT_LESS_OR_EQUAL (a)
PROCESS_NAME: csrss.exe
Probably caused by : win32k.sys
---
Mini061508-01.dmp.log
IRQL_NOT_LESS_OR_EQUAL (a)
PROCESS_NAME: avgupd.exe
Probably caused by : memory_corruption
---
Mini092008-01.dmp.log
PAGE_FAULT_IN_NONPAGED_AREA (50)
PROCESS_NAME: msnmsgr.exe
Could not read faulting driver name
Probably caused by : win32k.sys
---
Mini101708-01.dmp.log
PAGE_FAULT_IN_NONPAGED_AREA (50)
PROCESS_NAME: firefox.exe
Could not read faulting driver name
Probably caused by : win32k.sys
---
Mini111708-01.dmp.log
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
Probably caused by : win32k.sys
---
Mini112808-01.dmp.log
IRQL_NOT_LESS_OR_EQUAL (a)
PROCESS_NAME: firefox.exe
Probably caused by : win32k.sys
---
Mini112908-01.dmp.log
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
PROCESS_NAME: explorer.exe
Probably caused by : win32k.sys
---
Opened log file 'Mini120308-01.dmp.log'
IRQL_NOT_LESS_OR_EQUAL (a)
PROCESS_NAME: helpsvc.exe
Probably caused by : memory_corruption ( nt!MiRemovePageByColor+66 )
---
Opened log file 'Mini120908-01.dmp.log'
IRQL_NOT_LESS_OR_EQUAL (a)
PROCESS_NAME: helpsvc.exe
Probably caused by : memory_corruption ( nt!MiRemovePageByColor+66 )
---
Opened log file 'Mini121108-01.dmp.log'
IRQL_NOT_LESS_OR_EQUAL (a)
PROCESS_NAME: csrss.exe
IMAGE_NAME: win32k.sys
Probably caused by : win32k.sys ( win32k!EnterCrit+14 )
---
Opened log file 'Mini121408-01.dmp.log'
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
PROCESS_NAME: Idle
IMAGE_NAME: Unknown_Image
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
---
Opened log file 'Mini121408-02.dmp.log'
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
PROCESS_NAME: wmplayer.exe
IMAGE_NAME: ntkrpamp.exe
Probably caused by : ntkrpamp.exe ( nt!NtDelayExecution+87 )



Let me know if you want the actual dump files attached. Also, if you have a script that will auto-analyze and format the logs for each dump file, I would love it if you shared - Im using the following, but it doesnt add the "probably caused by" line, and I have to hand-format each file:

MiniDumps2Txt.vbs
Code:
Set fso = CreateObject("Scripting.FileSystemObject")
Set Folder = fso.GetFolder(".")
Set Files = Folder.Files
Set WshShell = CreateObject("WScript.Shell")
For Each File In Files
  If Mid(File.Name,Len(File.Name)-3,4) = ".dmp" Then
    Set oExec = WshShell.Exec("C:\Program Files\Debugging Tools for Windows (x86)\WinDbg.exe -y ""srv*c:\Symbols*http://msdl.microsoft.com/download/symbols"" -z " + File.Name + " -c ""$$><C:\Users\J Skoba\Desktop\Parents dumps\more\UDmp2Txt.txt;q"" -Q -QS -QY -QSY")
    Do While oExec.Status = 0
      WScript.Sleep 1000
    Loop
  End If
Next

UDump2Txt.txt
Code:
.logopen /d
!analyze -v
.logclose
 
Status
Not open for further replies.
Back