TechSpot

Random BSOD's

By slippyjim21
Jan 29, 2007
  1. Hiya,

    My PC is giving me grief!! I am getting lots of random BSOD's and even had a TRAP 00000006 Exception blah blah error earlier before windows had started to load. I reckon it is some hardware that is failing, probably motherboard, I have tried testing the memory with memtest and that came up OK and I have swapped the memory stick over into different slots, but it still carries on BSOD.

    The last error was with USBPORT.sys

    I have attached the last 3 minidump files, if someone can analyse them and give me a hint as to what is wrong I would be very grateful.

    Its a P4 3GHz, 1 stick of 512MB and an Asus P4VT+ motherboard

    Thanks,
    Steve

    View attachment 13107

    View attachment 13108

    View attachment 13109
     
  2. gavinseabrook

    gavinseabrook TS Rookie Posts: 528

    Sounds like a driver issue. Can you get into safemode?
     
  3. cpc2004

    cpc2004 TS Rookie Posts: 2,044

    Your attached minidumps are from last month. Can you attach the latest minidump here? The prelimary finding is hardware. Probably it is faulty ram. You must aware some faulty ram can pass memtest. If you have good ram from another PC, replace your ram. If it still crashes, the problem is not related to ram and it may be related to L2 cache memory of CPU.

    Debug report summary
    Mini112406-01.dmp BugCheck 93, {a78, 0, 0, 0}
    Probably caused by : VolSnap.sys ( VolSnap!VspWaitToRegisterWorker+ae )

    Mini122006-01.dmp BugCheck 1000000A, {1, 2, 0, 804f2609}
    Probably caused by : memory_corruption ( nt!MmFlushSection+c8 )
    STACK_TEXT:
    b9658ba4 804ec2e3 822b2390 00000001 004a3000 nt!MmFlushSection+0xc8
    b9658c2c 8059b45e 822c5db4 00000001 004a3000 nt!CcFlushCache+0x1d3 <-- Refer the cache memory
    b9658c50 8059a7b3 e1037008 00000000 00000000 nt!CmpFileFlush+0x44
    b9658cd8 8059b3ee e1037008 00000000 e1037008 nt!HvpDoWriteHive+0x41
    b9658cf0 805e3a1f e1037001 e4155d60 00000000 nt!HvSyncHive+0x88
    b9658d04 805e3ab7 e1037008 0048b7e8 b9658d64 nt!CmFlushKey+0x94
    b9658d58 804dd99f 000001b4 00fef868 7c90eb94 nt!NtFlushKey+0x88
    b9658d58 7c90eb94 000001b4 00fef868 7c90eb94 nt!KiFastCallEntry+0xfc


    Mini122906-01.dmp BugCheck 1000008E, {c0000005, bf810862, ba3fec94, 0}
    Probably caused by : win32k.sys ( win32k!RFONTOBJ::vMakeInactive+15 )
     
  4. russ

    russ TS Rookie Posts: 75

    If you have a copy of Linux live cd or could download a copy of Puppy linux live cd(50-84mb). If this Boots up and runs okay you've eliminated memory, processor and cache and probably motherboard as a problem and it likely the hard drive or a driver associated with windows. If it doesn't work then you have eliminated the hard drive and windows as a problem and could be the motherboard, Memory, processor and or cache.
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.