volsnap.sys BSOD

Page 2 of 2 FirstFirst 12

  1. Posts : 16
    Windows 7
    Thread Starter
       #11

    Hi all, so far it did not have BSOD after i recover to factory defaults.

    However today i added 2 gb of ram to make it a total of 4gb on my notebook.

    I got a Memory Management BSOD.

    Should i run Memtest or sorts?

    FYI: I was not doing anything, the laptop was on idle when the BSOD happened. Thanks!!
      My Computer


  2. Posts : 16
    Windows 7
    Thread Starter
       #12

    Ran Windows Memory Diagnostic tool and found no problems.

    Thereafter there's another BSOD, IRQL_DRIVER_NOT_LESS_OR_EQUAL.

    Any kind hearted souls can help me take a look at the dump file attached in post #11, thanks!
      My Computer


  3. Posts : 1,377
    Win7x64
       #13

    RuMmYtUb said:
    Ran Windows Memory Diagnostic tool and found no problems.

    Thereafter there's another BSOD, IRQL_DRIVER_NOT_LESS_OR_EQUAL.

    Any kind hearted souls can help me take a look at the dump file attached in post #11, thanks!
    Try running memory diagnostics for a whole day if necessary. The dump from post#11 is mostly indicative of some form of memory unreliability.
      My Computer


  4. Posts : 16
    Windows 7
    Thread Starter
       #14

    IRQL_DRIVER_NOT_LESS_OR_EQUAL BSOD occured while i was running

    SFS /SCANNOW in safe mode.

    Latest dump file as attached.. can someone highlight to me where is the root of the problem? Thank you so much! I'm getting frustrated already with this new laptop
      My Computer


  5. Posts : 16
    Windows 7
    Thread Starter
       #15

    Pls help for my post #14, anyone?

    Thanks
      My Computer


  6. Posts : 1,377
    Win7x64
       #16

    RuMmYtUb said:
    Pls help for my post #14, anyone?

    Thanks
    Similar again. Memory corruption, very probably caused by physical memory unreliability.

    Memory diagnostics results very rarely do "false positives", but they frequently do "false negatives". You may wish to run the diagnostics utility for many hours, or even a full 24h period.

    It is extremely difficult to discern (from a dump) which hardware component is at fault, in situations where bad hardware is suspected.
      My Computer


  7. Posts : 16
    Windows 7
    Thread Starter
       #17

    H2SO4 said:
    RuMmYtUb said:
    Pls help for my post #14, anyone?

    Thanks
    Similar again. Memory corruption, very probably caused by physical memory unreliability.

    Memory diagnostics results very rarely do "false positives", but they frequently do "false negatives". You may wish to run the diagnostics utility for many hours, or even a full 24h period.

    It is extremely difficult to discern (from a dump) which hardware component is at fault, in situations where bad hardware is suspected.
    Thanks bro! Will run it and perhaps take out my 2gb ram and see how.
      My Computer


  8. Posts : 16
    Windows 7
    Thread Starter
       #18

    Thanks all for helping.

    My case is closed, no more BSODs so far as I have bad ram. Manufacturer changed new ram!
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:52.
Find Us