Results 1 to 7 of 7

Thread: BSOD with WIndows Update

  1. #1
    Not *@!%in Postman Pat! Ruggerbugger's Avatar
    Join Date
    Aug 2004
    Location
    Rugby, (England for the Yanks)
    Posts
    1,659
    Thanks
    42
    Thanked
    69 times in 53 posts
    • Ruggerbugger's system
      • Motherboard:
      • Asus A7N8X-E deluxe
      • CPU:
      • XP 3200+
      • Memory:
      • 1GB Kingston PC3200 DDR2 dual channel
      • Storage:
      • 1 x 40GB OS, 1 x 320GB Data
      • Graphics card(s):
      • Sapphire 9800 Pro
      • PSU:
      • 400W Akasa (I think)
      • Case:
      • Antec Super Lanboy
      • Monitor(s):
      • Samsung LE32 LCD 720p
      • Internet:
      • VM 4Mb

    BSOD with WIndows Update

    Just been on Windows Update, where it installed the latest version of the validation tool. When I chose custom install afterwards, I got the following BSOD:

    Si3112r.sys Address F7489AFB base at F7482000

    Si3112A is the name of the Silicon Image RAID controller on my mobo. What could be the problem here?


    Click here for larger versions of photos

    Quote Originally Posted by Gonzo
    my a55 shoots great video in 1080i

  2. #2
    Ex-MSFT Paul Adams's Avatar
    Join Date
    Jul 2003
    Location
    %systemroot%
    Posts
    1,926
    Thanks
    29
    Thanked
    77 times in 59 posts
    • Paul Adams's system
      • Motherboard:
      • Asus Maximus VIII
      • CPU:
      • Intel Core i7-6700K
      • Memory:
      • 16GB
      • Storage:
      • 2x250GB SSD / 500GB SSD / 2TB HDD
      • Graphics card(s):
      • nVidia GeForce GTX1080
      • Operating System:
      • Windows 10 x64 Pro
      • Monitor(s):
      • Philips 40" 4K
      • Internet:
      • 500Mbps fiber
    All bluescreens are caused by unhandled exceptions in kernel mode.
    Almost every single bluescreen is caused by 3rd party drivers, this is the case here and you have been pointed to which driver fell over.

    It could be that the driver didn't handle losing connectivity with its disk, or maybe it didn't track memory it had allocated, or perhaps another 3rd party driver corrupted the Silicon Image driver in memory.

    What was the bugcheck code?
    Did it create a "Save Dump" event in the system event log?
    Did this happen just once, or can you reproduce the issue?
    Did it produce a kernel memory dump C:\Windows\Memory.dmp?
    ~ I have CDO. It's like OCD except the letters are in alphabetical order, as they should be. ~
    PC: Win10 x64 | Asus Maximus VIII | Core i7-6700K | 16GB DDR3 | 2x250GB SSD | 500GB SSD | 2TB SATA-300 | GeForce GTX1080
    Camera: Canon 60D | Sigma 10-20/4.0-5.6 | Canon 100/2.8 | Tamron 18-270/3.5-6.3

  3. #3
    Not *@!%in Postman Pat! Ruggerbugger's Avatar
    Join Date
    Aug 2004
    Location
    Rugby, (England for the Yanks)
    Posts
    1,659
    Thanks
    42
    Thanked
    69 times in 53 posts
    • Ruggerbugger's system
      • Motherboard:
      • Asus A7N8X-E deluxe
      • CPU:
      • XP 3200+
      • Memory:
      • 1GB Kingston PC3200 DDR2 dual channel
      • Storage:
      • 1 x 40GB OS, 1 x 320GB Data
      • Graphics card(s):
      • Sapphire 9800 Pro
      • PSU:
      • 400W Akasa (I think)
      • Case:
      • Antec Super Lanboy
      • Monitor(s):
      • Samsung LE32 LCD 720p
      • Internet:
      • VM 4Mb
    I'll check these tonight or tomorrow Paul, The issue was reproducible, but I didn't get it when I turned Automatic Updates back on. I can look for the kernel dump, but how do I check for the bugcheck code and the Save Dump event?

    This is the first time I've had this problem.


    Click here for larger versions of photos

    Quote Originally Posted by Gonzo
    my a55 shoots great video in 1080i

  4. #4
    Ex-MSFT Paul Adams's Avatar
    Join Date
    Jul 2003
    Location
    %systemroot%
    Posts
    1,926
    Thanks
    29
    Thanked
    77 times in 59 posts
    • Paul Adams's system
      • Motherboard:
      • Asus Maximus VIII
      • CPU:
      • Intel Core i7-6700K
      • Memory:
      • 16GB
      • Storage:
      • 2x250GB SSD / 500GB SSD / 2TB HDD
      • Graphics card(s):
      • nVidia GeForce GTX1080
      • Operating System:
      • Windows 10 x64 Pro
      • Monitor(s):
      • Philips 40" 4K
      • Internet:
      • 500Mbps fiber
    Right-click My Computer, click Manage.
    In the left pane, expand Event Viewer, select the System event log.
    Scroll down the list to find the error event with source "Save Dump" and double-click it.

    It will say something like this:
    "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff97fff55b79e, 0xfffffadfc901c6e0, 0xfffffadfc901c0f0). A dump was saved in: C:\WINDOWS\MEMORY.DMP."
    This would be a 0x7E bugcheck, for example.
    ~ I have CDO. It's like OCD except the letters are in alphabetical order, as they should be. ~
    PC: Win10 x64 | Asus Maximus VIII | Core i7-6700K | 16GB DDR3 | 2x250GB SSD | 500GB SSD | 2TB SATA-300 | GeForce GTX1080
    Camera: Canon 60D | Sigma 10-20/4.0-5.6 | Canon 100/2.8 | Tamron 18-270/3.5-6.3

  5. #5
    Not *@!%in Postman Pat! Ruggerbugger's Avatar
    Join Date
    Aug 2004
    Location
    Rugby, (England for the Yanks)
    Posts
    1,659
    Thanks
    42
    Thanked
    69 times in 53 posts
    • Ruggerbugger's system
      • Motherboard:
      • Asus A7N8X-E deluxe
      • CPU:
      • XP 3200+
      • Memory:
      • 1GB Kingston PC3200 DDR2 dual channel
      • Storage:
      • 1 x 40GB OS, 1 x 320GB Data
      • Graphics card(s):
      • Sapphire 9800 Pro
      • PSU:
      • 400W Akasa (I think)
      • Case:
      • Antec Super Lanboy
      • Monitor(s):
      • Samsung LE32 LCD 720p
      • Internet:
      • VM 4Mb
    I've checked, but there's no log of an event. There's no memory dump either. The issue is reproducible when I click on either the Express or Custom install buttons, but doesn't occur when the automatic updates facility is used.


    Click here for larger versions of photos

    Quote Originally Posted by Gonzo
    my a55 shoots great video in 1080i

  6. #6
    Ex-MSFT Paul Adams's Avatar
    Join Date
    Jul 2003
    Location
    %systemroot%
    Posts
    1,926
    Thanks
    29
    Thanked
    77 times in 59 posts
    • Paul Adams's system
      • Motherboard:
      • Asus Maximus VIII
      • CPU:
      • Intel Core i7-6700K
      • Memory:
      • 16GB
      • Storage:
      • 2x250GB SSD / 500GB SSD / 2TB HDD
      • Graphics card(s):
      • nVidia GeForce GTX1080
      • Operating System:
      • Windows 10 x64 Pro
      • Monitor(s):
      • Philips 40" 4K
      • Internet:
      • 500Mbps fiber
    Check your system is configured to produce memory dumps, and that the page file on C: is at least as big as your physical memory.

    Right-click My Computer, click Properties.
    Click Advanced tab, click Settings button in "Startup and Recovery" section.

    Under "System failure" ensure that the "Write an event to the system log" is ENABLED and "Automatically restart" is DISABLED.
    Under "Write debugging information", select "Kernel memory dump".
    (Dump file defaults are C:\MEMORY.DMP and to overwrite every time.)

    OK that, then click Settings in the "Performance" section.
    Click Advanced tab, click Change button.
    Veryify that the C: drive has a paging file size value against it.

    OK all the changes and you will need to reboot for them to take effect.


    Now at least a BSOD will stay on the screen for you to read the bugcheck code, even if a dump file isn't created.
    ~ I have CDO. It's like OCD except the letters are in alphabetical order, as they should be. ~
    PC: Win10 x64 | Asus Maximus VIII | Core i7-6700K | 16GB DDR3 | 2x250GB SSD | 500GB SSD | 2TB SATA-300 | GeForce GTX1080
    Camera: Canon 60D | Sigma 10-20/4.0-5.6 | Canon 100/2.8 | Tamron 18-270/3.5-6.3

  7. #7
    Registered User
    Join Date
    Apr 2006
    Posts
    1
    Thanks
    0
    Thanked
    0 times in 0 posts

    Lightbulb

    Paul, if you don't mind, I had the same exact mobo and BSoD.
    Here is what I did to resolve the issue:
    Since the latest RAID drivers available on Asus' site didn't help either, I went to Silicon Image's site and downloaded the newer drivers from there which resolved the issue for me.
    Download link: http://www.siliconimage.com/docs/SiI...D%20Driver.zip

    After downloading, unzip the contents of the zip file which should be another zip file and a word document. Extract (unzip) the contents of that other zip file (3x12_x86_rdvr-logod-10051.zip) as well.
    Then using Device Manager update drivers by pointing the driver search to the folder where you extracted the downloaded .zip file. There will be 8 files extracted but you will only need the following files for the driver update: TxtSetup.oem and Si3112r.sys but do not delete the others.

    At this point, do the following:
    START > RUN > type compmgmt.msc > OK
    expand Device Manager and double-click on SATA/RAID entry.
    click on DRIVER tab and then Update Driver button.
    point the location to wherever you extracted the 3x12_x86_rdvr-logod-10051.zip file's contents.
    After installation, reboot your PC as prompted.

    TurcoLoco

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •